Hi!
Recently I installed openSuSE 11.3 x64 on PC with Intel motherboard, 4GB RAM & two of 1TB WD RE3.
Of course I set RAID1 during installation
After some struggle with GRUB which pointed to wrong devices after installation I started to work.
But suddenly I found that file system is corrupted after every reboot
(It does not depend on what I use and what the way I use - reboot, shutdown -r now
or even just poweroff - everything follow to:
Starting MD Raid mdadm: /dev/md2 has been started with two drives
mdadm /dev/md3 has been started with 2 drives
mdadm /dev/md4 has been started with 2 drives
mdadm /dev/md5 has been started with 2 drives
Looks like everuthing is OK but:
Waiting for /dev/disk/by-id/md-uuid-ed3515f6:bla-bla no more events
Checking file systems…
fsck from util-linux-ng 2.17.2
fsck.ext3: no such file or directory while trying to open /dev/disk/by-id/md-uuid-ed3515f6:bla-bla
/dev/disk/by-id/md-uuid-ed3515f6:bla-bla:
The superblock could not be read or does not describe a correct ext2 filesystem.
If device is valid and it really contains ext2 filesystem
(and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
/dev/md4: clean…bla-bla
/dev/md2: clean…bla-bla
/dev/md3: clean…bla-bla
Give the root password for login:
What I do in this situation?
First I run fsck.
fsck shows - no errors - all filesystems are clean!
Lets look what mount shows:
#mount
/dev/md1 on / type ext3 (rw,acl,user_xattr)
Then I try to mount all my filesystems manually
and it does the trick!
#mount /dev/md2 /usr
#mount /dev/md3 /var
#mount /dev/md4 /tmp
#mount /dev/md5 /home
Then I see that everything fine indeed and I can run Midnight Commander (for instance)
Then I give command “reboot” and machine is rebooted and openSuSE is loaded
as usual.
But after simple reboot everything is started over!!!
Sometimes fsck shows that 2 devices have corrupted superblocks.
I cannot understand who is wrong: fsck or kernel does something unusual with filesystems at reboot?
Here my configs:
fstab:
/dev/disk/by-id/md-uuid-9dd49056:810c5264:055b3821:2b0e8729 swap swap defaults 0 0
/dev/disk/by-id/md-uuid-61f95efc:5374ff5e:26c6db3f:978989bd / ext3 acl,user_xattr 1 1
/dev/disk/by-id/md-uuid-ed3515f6:2f7738a4:f3a60f9e:57359cfd /home ext3 acl,user_xattr 1 2
/dev/disk/by-id/md-uuid-40834f25:e910c8ba:7ca5db99:8eb1832d /tmp ext3 acl,user_xattr 1 2
/dev/disk/by-id/md-uuid-b5178981:61ca5a1c:918788ea:d89c4f58 /usr ext3 acl,user_xattr 1 2
/dev/disk/by-id/md-uuid-2e46580f:1b9155bc:254ec233:548cb1aa /var ext3 acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
mtab:
/dev/md1 / ext3 rw,acl,user_xattr 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
debugfs /sys/kernel/debug debugfs rw 0 0
devtmpfs /dev devtmpfs rw,mode=0755 0 0
tmpfs /dev/shm tmpfs rw,mode=1777 0 0
devpts /dev/pts devpts rw,mode=0620,gid=5 0 0
/dev/md5 /home ext3 rw,acl,user_xattr 0 0
/dev/md4 /tmp ext3 rw,acl,user_xattr 0 0
/dev/md2 /usr ext3 rw,acl,user_xattr 0 0
/dev/md3 /var ext3 rw,acl,user_xattr 0 0
securityfs /sys/kernel/security securityfs rw 0 0
/proc /var/lib/ntp/proc none ro,nosuid,nodev,bind 0 0
It strongly seems to me something wrong with kernel because no errors after manual mounting filesystems and reboot in safe mode. Though maybe it’s wrong too.
Regards,
Mike