I hardly can't believe it. This night (after I was formatting the last
one of my QIC80 backup tapes <g>), my Linux system (kernel 2.1.128)
died just out of the blue.
The death resulted in a very bad filesystem corruption (superblock has
gone and a few directory entries). Fortunately, I had the chance to plug
in the drive into another Linux machine and was able to repair
most of the filesystem and - more important - to save all my private data.
I got the following messages, when I tried to boot linux in my machine:
(On sda1 is an old DOS version with loadlin, which I use to load linux)
Partition check:
sda: sda1 sda2 sda3
(Here, a strange noise appeared)
aha1542.c: Trying device reset for target 0
Sent BUS RESET fo scsi host 0
scsidisk I/O error: dev 08:03,sector 2
EXT2-fs: unable to read superblock
scsidisk I/O error: dev 08:03, sector 0
FAT bread failed
kernel panic: VFS: unable to mount root from 08:03
Well, on the other machine, I was able to run e2fsck with the superblock
at pos. 8193 (how can I *boot* linux and specify, that the superblock is
at 8193?). There were some twenty errors, but almost all data could
be restored.
In the syslog of the other machine (who uses a AHA2940), I got a lot of
entries like the following:
Nov 17 07:58:34 proddev-linux2 kernel: scsi0: MEDIUM ERROR on channel 0, id 1, lun 0, CDB: 0x08 0b 8b e0 40 00
Nov 17 07:58:34 proddev-linux2 kernel: Current error sd08:13: sns = f0 3
Nov 17 07:58:34 proddev-linux2 kernel: ASC=11 ASCQ= 0
Nov 17 07:58:34 proddev-linux2 kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x0b 0
x8b 0xf8 0x18 0x00 0x00 0x00 0x00 0x11 0x00 0x00 0x80
Nov 17 07:58:34 proddev-linux2 kernel: scsidisk I/O error: dev 08:13, sector 81998, absolute sector 756728
Nov 17 08:03:28 proddev-linux2 kernel: scsi0: MEDIUM ERROR on channel 0, id 1, lun 0, CDB: 0x08 0b 8b f8 02 00
Nov 17 08:03:28 proddev-linux2 kernel: Current error sd08:13: sns = f0 3
Nov 17 08:03:28 proddev-linux2 kernel: ASC=11 ASCQ= 0
Nov 17 08:03:28 proddev-linux2 kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x0b 0
x8b 0xf8 0x18 0x00 0x00 0x00 0x00 0x11 0x00 0x00 0x80
Nov 17 08:03:28 proddev-linux2 kernel: scsidisk I/O error: dev 08:13, sector 81998, absolute sector 756728
Nov 17 08:10:25 proddev-linux2 kernel: scsi0: MEDIUM ERROR on channel 0, id 1, lun 0, CDB: 0x08 0b 8b f8 02 00
Nov 17 08:10:25 proddev-linux2 kernel: Current error sd08:13: sns = f0 3
Nov 17 08:10:25 proddev-linux2 kernel: ASC=11 ASCQ= 0
Nov 17 08:10:25 proddev-linux2 kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x0b 0
x8b 0xf8 0x18 0x00 0x00 0x00 0x00 0x11 0x00 0x00 0x80
Nov 17 08:10:25 proddev-linux2 kernel: scsidisk I/O error: dev 08:13, sector 81998, absolute sector 756728
Nov 17 08:10:25 proddev-linux2 kernel: EXT2-fs error (device 08:13): ext2_read_inode: unable to read inode block - inode=10406, block=40999
My question now - who (except me for missing backups :-) is to blame
here?
- My aha1542 (quite unlikely. It never made *any* problems in the past)
- my DCAS 43440 (it's just 10 months old...)
- Kernel 2.1.128 (2.1 kernels worked absolutely fine for me since more
than half a year. Never the slightest problem)
- something else, not mentioned here?
Ciao and thank you very much
Christoph
-- ** http://ourworld.compuserve.com/homepages/ChLorenz/ ** ChLorenz@csi.com ** ** No Spam ! ** No Adverts ! ** No Junk-Mails ! ** No unwanted Mails ! **
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/