Repair hd

Under construction
----------------------------

"Bad block messages" usually happens when drives will not mount or boot completely.
Checkout error for sure

dmesg | tail
[ 4324.292510] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 4324.292521] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 4327.713599] EXT4-fs (sdb1): ext4_check_descriptors: Checksum for group 1536 failed (18982!=0)
[ 4327.713612] EXT4-fs (sdb1): group descriptors corrupted!
[ 4331.946594] EXT4-fs (sdb1): ext4_check_descriptors: Checksum for group 1536 failed (18982!=0)
[ 4331.946607] EXT4-fs (sdb1): group descriptors corrupted!
[ 4342.836612] EXT4-fs (sdb1): ext4_check_descriptors: Checksum for group 1536 failed (18982!=0)
[ 4342.836625] EXT4-fs (sdb1): group descriptors corrupted!
[ 4600.601626] EXT4-fs (sdb1): ext4_check_descriptors: Checksum for group 1536 failed (18982!=0)
[ 4600.601637] EXT4-fs (sdb1): group descriptors corrupted!

Get back up blocks (if any) so problem can be resolved.  sudo mke2fs -n /dev/xxx

$ sudo mke2fs -n /dev/sdb1

mke2fs 1.42 (29-Nov-2011)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
15007744 inodes, 60001024 blocks
3000051 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
1832 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Run the fix. Takes an eon. Battery backup required. sudo e2fsck -b block_number /dev/xxx

$ sudo e2fsck -b 23887872 /dev/sdb1

---
---
Group descriptor 1825 checksum is invalid.  FIXED.
Group descriptor 1826 checksum is invalid.  FIXED.
Group descriptor 1827 checksum is invalid.  FIXED.
Group descriptor 1828 checksum is invalid.  FIXED.
Group descriptor 1829 checksum is invalid.  FIXED.
Group descriptor 1830 checksum is invalid.  FIXED.
Group descriptor 1831 checksum is invalid.  FIXED.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 10882413 has zero dtime.  Fix<y>? yes

Comments

Popular posts from this blog

Guiless?

Web.com and Network Solutions, the Walmart of the internet.

MSOffice vs Libreoffice