/home mounts as readonly!

[Zeadar]

My /home partition is mounted as readonly! Leaving my system malfunctioning. Writing this from a livecd. saved sabayon's dmesg on an external drive ofcourse.

dmesg: http://pastebin.sabayon.org/pastie/12223

At about the end of the file, the kernel complain about an error with sda. But I've never had any issues with me harddrive before so I'm completely clueless what to do about it.

Have a nice day!

Code: Select all

[  139.980231] sd 0:0:0:0: [sda] CDB:
[  139.980233] cdb[0]=0x2a: 2a 00 1f 93 bc d8 00 00 d0 00
[  139.980243] end_request: I/O error, dev sda, sector 529775832
[  139.980308] ata1: EH complete
[  140.048681] Aborting journal on device dm-1-8.
[  140.048743] EXT4-fs error (device dm-1) in ext4_reserve_inode_write:4476: Journal has aborted
[  140.050022] journal commit I/O error
[  140.307845] EXT4-fs error (device dm-1) in ext4_dirty_inode:4603: Journal has aborted
[  140.307838] EXT4-fs error (device dm-1): ext4_journal_start_sb:370:
[  140.307853] EXT4-fs error (device dm-1): ext4_journal_start_sb:370:
[  140.307857] Detected aborted journal

[  140.307863] EXT4-fs (dm-1): Remounting filesystem read-only
[  140.307867] Detected aborted journal

The last bit of dmesg. Don't know if all of it relevant.

EDIT: On the third boot sabayon mounted the root partition intead of /home. This made me more confused than before.

[Matte88]

Code: Select all

[  139.980243] end_request: I/O error, dev sda, sector 529775832
[  139.980308] ata1: EH complete
[  140.048681] Aborting journal on device dm-1-8.
[  140.048743] EXT4-fs error (device dm-1) in ext4_reserve_inode_write:4476: Journal has aborted
[  140.050022] journal commit I/O error
[  140.307845] EXT4-fs error (device dm-1) in ext4_dirty_inode:4603: Journal has aborted
[  140.307838] EXT4-fs error (device dm-1): ext4_journal_start_sb:370:
[  140.307853] EXT4-fs error (device dm-1): ext4_journal_start_sb:370:
[  140.307857] Detected aborted journal

[  140.307863] EXT4-fs (dm-1): Remounting filesystem read-only
[  140.307867] Detected aborted journal

I think you sda's going to become a paperweight...

[sabayonino]

oooh ... check your partitonfrom live-mode (sabayon or gparted-live).

some sectors seem broken

[Ryuno-Ki]

By the way, does Sabayon provides some kind of S.M.A.R.T. testing?

[colock]

sure. smartctl is the command you're looking for.

[Zeadar]

Alright! I've searched and learned about a bit about how to fix the filesystem and such. e.g mounted my lvm portations, made a badblocks file each of /dev/lg_disarray/<disks> and fcsk.ext4 -l badblocks /dev/vg_disarray/<disks>.

/dev/vg_disarray/lv_home had 12 errors!

Code: Select all

e2fsck 1.42.5 (29-Jul-2012)
Bad block 190272420 out of range; ignored.
Bad block 190272421 out of range; ignored.
Bad block 190272422 out of range; ignored.
Bad block 190272423 out of range; ignored.
Bad block 213691796 out of range; ignored.
Bad block 213691797 out of range; ignored.
Bad block 213691798 out of range; ignored.
Bad block 213691799 out of range; ignored.
Bad block 246138440 out of range; ignored.
Bad block 246138441 out of range; ignored.
Bad block 246138442 out of range; ignored.
Bad block 246138443 out of range; ignored.
/dev/vg_disarray/lv_home: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/vg_disarray/lv_home: ***** FILE SYSTEM WAS MODIFIED *****
/dev/vg_disarray/lv_home: 193279/26574848 files (1.0% non-contiguous), 35411578/106299392 blocks


All other partitions are fine.

I'd think the sabayon is usable by now but now it mounts /root as readonly and failing to load kde! (even kdm).

Sitting helpless at a root prompt at boot which I can't do anything wth since it's mounted as readonly, have tried umount and mount command to bring it back but it doesn't work. I only get a message that the device is busy when I try to mount /root after <umount /dev/vg_disarray/lv_root>.