Kamaraju S Kusumanchi <raju.mailingli...@gmail.com> writes: > lee wrote: > >> Kamaraju S Kusumanchi <raju.mailingli...@gmail.com> writes: >> >>> When I ran >>> >>> $sudo e2fsck -c -c -f -v /dev/sdb7 >>> >>> I am getting a lot of errors such as >>> >>> Error reading block 18022401 (Attempt to read block from filesystem >>> resulted >>> in short read) while reading inode and block bitmaps. Ignore error<y>? >>> yes Force rewrite<y>? yes >>> 3) Is the drive going bad and need to be replaced? >> >> Corresponding entries in /var/log/syslog about the inability to read >> sectors from this device would indicate that there is a hardware >> problem. Provided that all connections and the power supply are ok, I >> would say the device is broken when there are such errors in syslog. >> >> In case there aren't errors in syslog, I would look somewhere else >> first. > > Yes, there are I/O errors in syslog such as > > Aug 30 08:27:20 kusumanchi kernel: [118453.218041] Buffer I/O error on > device sdb7, logical block 5384272
That seems to indicate that the disk is broken. At first I thought these messages look different from what I've seen, but googling shows quite some agreement that messages like this tell you that the disk is damaged. >> Are you really still using ext2fs? > > The partitions are ext3. Is there a better command to check ext3 partitions > other than ext2fs? See man fsck ... running "fsck -t ext2" probably ends up doing the same thing as calling the fs-type specific checking tool directly, though. -- Debian testing amd64 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d320s2sw....@yun.yagibdah.de
