[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#354765: marked as done (Remounting /dev/hd*1 as ro during installation and aborts)



Your message dated Wed, 1 Mar 2006 06:42:23 +0100
with message-id <20060301054223.GH5056@djedefre.onera>
and subject line Bug#354765: Remounting /dev/hd*1 as ro during installation and aborts
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports
Severity: Critical

INSTALL REPORT

Debian-installer-version:ftp://carroll.aset.psu.edu/pub/linux/distributions/debian-cd/3.1_r0a/i386
Fourteen CD set downloaded over several days, starting on or about 11/10/2005.



uname -a:

Linux debian 2.6.8-2-686 #1 Thu May 19 17:53:30 JST 2005 i686 GNU/Linux
  1. Date: February 26, 2006

Method: Booted from installation CD.

Machine: CUSTOM BUILT
Processor: ATHLON XP 2200+
Memory: 256MB
Root Device: IDE /dev/hda1

Root Size/partition table:

Disk /dev/hda: 41.1 GB, 41174138880 bytes
255 heads, 63 sectors/track, 5005 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End         Blocks    Id  System
/dev/hda1   *            1          851      6835626   83  Linux
/dev/hda2             852        5005    33367005     5  Extended
/dev/hda5             852          944        746991   82  Linux swap / Solaris
/dev/hda6             945        5005    32619951   83  Linux

Disk /dev/hdb: 10.2 GB, 10242892800 bytes
255 heads, 63 sectors/track, 1245 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start           End         Blocks      Id  System
/dev/hdb1   *              1           682     5478133+  83  Linux
/dev/hdb2               683         1245     4522297+    5  Extended
/dev/hdb5               683           819     1100421     82  Linux swap / Solaris
/dev/hdb6               820         1245     3421813+  83  Linux

Operating systems: Mandrivalinux 1.10 on /dev/hdb
Debian 2.6.8-2-386 on /dev/hda



Output of lspci and lspci -n:

lspci:

0000:00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0269
0000:00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1269
0000:00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2269
0000:00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3269
0000:00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4269
0000:00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7269
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South]
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

lspci -n:

0000:00:00.0 0600: 1106:0269
0000:00:00.1 0600: 1106:1269
0000:00:00.2 0600: 1106:2269
0000:00:00.3 0600: 1106:3269
0000:00:00.4 0600: 1106:4269
0000:00:00.7 0600: 1106:7269
0000:00:01.0 0604: 1106:b198
0000:00:0f.0 0104: 1106:3149 (rev 80)
0000:00:0f.1 0101: 1106:0571 (rev 06)
0000:00:10.0 0c03: 1106:3038 (rev 81)
0000:00:10.1 0c03: 1106:3038 (rev 81)
0000:00:10.2 0c03: 1106:3038 (rev 81)
0000:00:10.3 0c03: 1106:3038 (rev 81)
0000:00:10.4 0c03: 1106:3104 (rev 86)
0000:00:11.0 0601: 1106:3227
0000:00:11.5 0401: 1106:3059 (rev 60)
0000:00:12.0 0200: 1106:3065 (rev 78)
0000:01:00.0 0300: 1002:5159


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]

Comments/Problems:

    This was reinstallation of Debian onto a newer and larger disk. I had it originally installed on the second (slave) IDE disk, toward the end of last December. It worked fine for a while, but than it started having problems with the disk. Rather frequently, during boot, it would report lost interrupt on /dev/hdb and abort. Less frequently, when the system was up and running, it would show message "lost interrupt (hdb)" and a second or two later "reconected". Several times it even knocked the disk off of BIOS' list of hardware. Warm restart would'n bring it back onto the list; I had to cold restart. Once, the BIOS even reported that there was imminent disk failure and to back up the data. Each time the system reported a problem with the disk, I ran disk manufacturer's diagnostic and each time the diagnostics found nothing wrong with either disk. Yet another problem that occasionally happened both with Mandriva and Debian is that on shutdown message "EXT3-fs error: "Read only file system, journal aborted"" comes up and prints indefinitely. So, before reporting the problem, I decided to switch places of Mandriva and Debian to see whether it's a hardware problem. Mandriva installed OK, onto the same disk where Debian was, and is still there and working.

    With Debian the installation procedure was erratic: the base system would install about once out of every four tries. Each time I started from the beginning I would see something different. Whenever it failed, however, it was for the same reason. The reported problem on console #3 was that it couldn't remove /var/lib/dpkg/status or something similar because the the file system was read-only.  When base system did install so that I could reboot and log in, the rest of the installation invariably failed, for the same reason - read only file system. And it would always happen at the same point: it would download updates from /security.debian.org, unpack and run package configuration, and then, just as it brought back the menu, the message "EXT3-fs error: read only file system" would break through the menu and scrool of the screen. I tried reinstalling back on the slave disk, but it made no difference, the same thing was happening over and over again. So I went back and forth between slave and master disks, trying different things like "mount -n -o remount rw \", ran aptitude trying to fix broken packages, until it partially installed, on master disk, after I don't know how many tries.. Hardly a day later, when I tried to boot, the disk was unreadable again and boot ended with the message "Kernel panic: tried to kill init". I tried booting again - the same message came up. I tried to mount /dev/hda1 from withing Mandriva, to salvage install logs; it didn't work; mount reported bad magic number. I then ran "e2fsck -b 32768 /dev/hda", and that recovered journal, then shut down Mandriva and succeeded in bringing Debian up, logging in and out and shutting down. So, Debian is on, but rather precariously, X doesn't work properly and a number of packages are broken. I decided to leave it at that, rather than trying any further fixes, lest everyting gets trashed again.

    This was the best I could do. Hope you can help.

Install logs and other status info is available in /var/log/debian-installer/.

-- 
                                                Sincerely,


                                                Ivica Culjak


--- End Message ---
--- Begin Message ---
>         disk, toward the end of last December. It worked fine for a
>         while, but than it started having problems with the disk. Rather


All this sounds like a dying disk problem which has nothing to do with
the installe ritself.





--- End Message ---

Reply to: