Sunday, December 23, 2012

fsck didn't fix the issue with disk error



After rebooting the system, it went to the single user mode. Complaining about /dev/sdb. fsck the device but it failed. remounted the root fs with rw option and removed the entry from fstab. rebooted it.

1. fsck the device in single user mode.
# fsck.ext4 /dev/sdb

Tried to fsck but got the error below.

fsck.ext4: Device or resource busy while trying to open /dev/sdb Filesystem mounted or opened

exclusively by another program?

2. The root file system is currently mounted read -only. remounted the root fs with read/write option
# mount -n -o remount,rw /

3. Edited the fstab and commented out the filesystem entry for /dev/sdb
# vi /etc/fstab
# /dev/sdb /data ext4 defaults 1 2

4. Rebooted the machine
# shutdown -r now

---------------
The super block could not e read or does not describe a correc ext2 filesystem. e2fsck -b 8193
<device>
/dev/Sam_Vol/Sam_LV
(Repair filesystem) 2 #
rsync -bazv -e ssh /home root@destination:

No comments:

Post a Comment