Subject: scsi errors -- help deciphering messages
From: John Schmidt (jas@netbrick.com)
Date: Mon Feb 04 2002 - 14:48:21 MST
Hi,
I have been having some lockups due to scsi errors. I have two drives with /
on /dev/sdb5 and /home on /dev/sdc5. I am not sure which of the drives is
flaking out on me. I am guessing it is /dev/sdc5 based on the id 2 shown in
/var/log/messages. I have output from var/log/messages (with my /etc/fstab
shown above):
/etc/fstab:
/dev/sdb5 / ext2 defaults 1 1
/dev/sdb4 swap swap defaults 0 0
/dev/sdc5 /home ext2 defaults 1 2
/dev/fd0 /mnt/floppy auto noauto,user 0 0
/dev/cdrom /mnt/cdrom auto noauto,ro,user 0 0
none /proc proc defaults 0 0
none /proc/bus/usb usbdevfs defaults 0 0
none /dev/pts devpts gid=5,mode=620 0
0
Feb 4 13:30:45 retriever kernel: SCSI disk error : host 0 channel 0 id 2 lun
0
return code = 2
Feb 4 13:30:45 retriever kernel: scsidisk I/O error: dev 08:25, sector
16517326Feb 4 13:30:45 retriever kernel: scsidisk I/O error: dev 08:25,
sector 16517326Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev
08:25, sector 1196104
Feb 4 13:30:46 retriever kernel: EXT2-fs error (device sd(8,37)):
ext2_write_inode: unable to read inode block - inode=149506, block=598052
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector 557136
Feb 4 13:30:46 retriever kernel: EXT2-fs error (device sd(8,37)):
ext2_write_inode: unable to read inode block - inode=69670, block=278568
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector
1769568
Feb 4 13:30:46 retriever kernel: EXT2-fs error (device sd(8,37)):
ext2_write_inode: unable to read inode block - inode=221282, block=884784
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector
1671252
Feb 4 13:30:46 retriever kernel: EXT2-fs error (device sd(8,37)):
ext2_write_inode: unable to read inode block - inode=208947, block=835626
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector
11223122Feb 4 13:30:46 retriever kernel: EXT2-fs error (device sd(8,37)):
ext2_write_inode: unable to read inode block - inode=1402923, block=5611561
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector
15499342Feb 4 13:30:46 retriever kernel: EXT2-fs error (device sd(8,37)):
ext2_write_inode: unable to read inode block - inode=1937440, block=7749671
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector
12730440Feb 4 13:30:46 retriever kernel: EXT2-fs error (device sd(8,37)):
ext2_write_inode: unable to read inode block - inode=1591300, block=6365220
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector
1998926
Feb 4 13:30:46 retriever kernel: EXT2-fs error (device sd(8,37)):
ext2_write_inode: unable to read inode block - inode=249888, block=999463
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector 2
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector 66
Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25, sector
16515140Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev 08:25,
sector 16515148Feb 4 13:30:46 retriever kernel: scsidisk I/O error: dev
08:25, sector 16515154Feb 4 13:30:46 retriever kernel: scsidisk I/O error:
dev 08:25, sector 16516086Feb 4 13:30:46 retriever kernel: scsidisk I/O
error: dev 08:25, sector 16516350
Given the above, is it safe to assume that my drive is going south?
John Schmidt
jas@netbrick.com
This archive was generated by hypermail 2a24 : Mon Feb 04 2002 - 15:03:48 MST