You are not logged in.
Pages: 1
I reinstalled arch using a script i made and everything was working fine until kde 4 froze for some reason that I cant remember, ctrl+alt+backspace didnt do anything and alt+sysrq+RUISUB didnt seem to do anything either (is it even enabled in the arch kernel?) so my last resort was to do a hard reboot. When I tried to boot back into it I was greeted with the expected "your filesystem is dirty enter maintenance mode to fix it" so i ran jfs_fsck /dev/sda6 -a and it ran and said that the filesystem was clean, i also checked my /var partition which is also JFS and that came back clean also. I rebooted and the same thing happened, so i tried to go into my kde 3 installation and for some reason that was screwed up too even though its reiserfs and not jfs. the grub kernel line was pointing to /dev/sda6 even though its on /dev/sda7, even when I changed that it still give me the dirty filesystem error.
I cant seem to figure out why it wont boot even when the FS is marked as being clean. heres the output of the check i got when running it from a kubuntu live cd:
ubuntu@ubuntu:~$ sudo fsck.jfs -v /dev/sda6
fsck.jfs version 1.1.11, 05-Jun-2006
processing started: 3/13/2009 2.18.35
Using default parameter: -p
The current device is: /dev/sda6
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes: 4096
Filesystem size in blocks: 2441872
**Phase 0 - Replay Journal Log
LOGREDO: Log already redone!
logredo returned rc = 0
Filesystem is clean.
All observed inconsistencies have been repaired.
Filesystem has been marked clean.
**** Filesystem was modified. ****
processing terminated: 3/13/2009 2:18:35 with return code: 0 exit code: 0.
ubuntu@ubuntu:~$ sudo fsck.jfs -v /dev/sdc3
fsck.jfs version 1.1.11, 05-Jun-2006
processing started: 3/13/2009 2.29.22
Using default parameter: -p
The current device is: /dev/sdc3
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes: 4096
Filesystem size in blocks: 1317330
**Phase 0 - Replay Journal Log
LOGREDO: Log already redone!
logredo returned rc = 0
Filesystem is clean.
All observed inconsistencies have been repaired.
Filesystem has been marked clean.
**** Filesystem was modified. ****
processing terminated: 3/13/2009 2:29:23 with return code: 0 exit code: 0.
ubuntu@ubuntu:~$ sudo fsck.reiserfs --fix-fixable /dev/sda7
###########
reiserfsck --fix-fixable started at Fri Mar 13 02:31:14 2009
###########
Replaying journal..
Reiserfs journal '/dev/sda7' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 41014
Internal nodes 278
Directories 11105
Other files 157035
Data block pointers 771287 (17 of them are zero)
Safe links 0
###########
reiserfsck finished at Fri Mar 13 02:31:29 2009
###########
Offline
I think this is related to the JFS quirk where the filesystem needs to be remounted read-only again first?
Try doing the fsck, mounting it read-only before rebooting, and then reboot. If it fails at the reboot part, try doing the above and then try mounting it read-write without rebooting yet.
What's your fstab in Arch? I *think* the Arch installer by default makes JFS root mount read-only, did you make your own fstab?
Last edited by Ranguvar (2009-03-13 02:46:27)
Offline
Pages: 1