fsck command changed ext3 raid to ext3 that doesn't mount?

Okay I’m not quite sure what happened…
But as my filesystem got corrupted I had to run the fsck command to fix things, now as it asked me like 5 milion questions and it took like 6 hours I’ve no idea what it exactly has been doing.

I do remember something about the journaling getting ruined and I think it asked if I wanted to change my ext3 filesystem to ext2 to fix it, which I answered yes to.

I can finally boot again and it seems to have fixed at least my main harddrive (sda), sdb/sdc/sdd which are my disks configured in a software raid 5 seems to have been downgraded to ext2.

The problem is that my raid array doesn’t seem to be mounted (guess that’s what the asterisk stands for).

Posted my bootlog on pastebin, don’t know if it’s of any use.

Some screenshots of YaST partioner, again no idea how useful it is.
http://thumbnails4.imagebam.com/2338/97ad0e23376656.gif](http://www.imagebam.com/image/97ad0e23376656) http://thumbnails13.imagebam.com/2338/3b4a0923376660.gif](http://www.imagebam.com/image/3b4a0923376660) http://thumbnails10.imagebam.com/2338/524bcc23376667.gif](http://www.imagebam.com/image/524bcc23376667)

Raid monitor info:

Personalities : [raid6] [raid5] [raid4] 
md1 : active raid5 sdd1[0] sdb1[3] sdc1[1]
      1953519616 blocks super 1.0 level 5, 128k chunk, algorithm 0 [3/3] [UUU]
      bitmap: 0/466 pages [0KB], 1024KB chunk

unused devices: <none>

Finally fstab…

/dev/disk/by-id/ata-WDC_WD6400AAKS-75A7B0_WD-WMASY1366430-part3 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-WDC_WD6400AAKS-75A7B0_WD-WMASY1366430-part1 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/ata-WDC_WD6400AAKS-75A7B0_WD-WMASY1366430-part2 /home                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
/dev/md1             /home/Bakhuis/Shared/Anime/Archive ext3       defaults              1 2

All disks pass SMART test by the way.

(How) Can I remount my raid array so I got access to my files again?

ignore sde, it’s an old disk I hooked up to back up some things I don’t want to lose
OpenSUSE 11.1 x86_64 / KDE 4.1

tried mount -a and it told me.

mount: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error.
In some cases useful info is found in syslog try dmsg | tail or so.

So I did the dmsg | tail, which didn’t make any sense to me, googled bad superblock and found Linux: Recover Corrupted Partition From A Bad Superblock.
Followed the steps described there, which went smooth… did a mount -a again.

Same message as before.

So I thought… to hell with it and changed the fstab entry to ext2 instead of ext3, mount -a, and it’s working.

Time to google the differences between ext2 and 3 I guess, as everything seems to work fine. Thought I’d lose the information like the last time a file was accessed… but that’s still working.

ext3 is just ext2 + a journal. You can add a journal to ext2 to make it ext3.

Think I’m going to leave it as is… the advantage of a journaling system from what I can tell is that it should eliminate the need to run fsck after the system doesn’t shutdown properly.

Well… I had to run this pretty much every reboot lately, so that’s not gonna cost me anything.