Okay, the situation is… I got 3 disks (sda/sdb/sdd) with a single ‘raid’ partition that were a raid array in my server.
Now I’ve hooked the disks up to my desktop and created a RAID out of them again (no formatting).
The Filesystem is ext2 and I tried adding it by adding the following line to my fstab file
/dev/md0 /home/Pascal/Shared ext2 defaults 1 2
and then running mount -a as root, which resulted in the following error:
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
I’m just not the command-line type, and I was able to go into YaST and open the Partitioner tool and add a RAID1 and a RAID5 array, and even an encrypted partiton. It created fstab and cryptotab entries for me. Have you thought of trying that?
Axeia adjusted his/her AFDB on Saturday 16 May 2009 19:06 to write:
>
> Okay, the situation is… I got 3 disks (sda/sdb/sdd) with a single
> ‘raid’ partition that were a raid array in my server.
> Now I’ve hooked the disks up to my desktop and created a RAID out of
> them again (no formatting).
>
> The Filesystem is ext2 and I tried adding it by adding the following
> line to my fstab file
>
> Code:
> --------------------
> /dev/md0 /home/Pascal/Shared ext2 defaults 1 2
> --------------------
>
> and then running mount -a as root, which resulted in the following
> error:
>
> Code:
> --------------------
> mount: wrong fs type, bad option, bad superblock on /dev/md0,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
> --------------------
I ahve seen this before when I had a raid setup, I think I just tried and
mounted it else where try putting it in :
/mnt/back-up
or somewhere like that but not in your /home folder
First thing I attempted despise the commandline as the next time I run into this problem I wont remember the commands, remembering what you clicked in which order is way easier.
# e2fsck -f /dev/md0
e2fsck 1.41.4 (27-Jan-2009)
e2fsck: Filesystem revision too high while trying to open /dev/md0
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an 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>
Did you preserve the order when you built the RAID again?
I’m asking this because if the specified order was incorrect, it would have incorrectly reconstructed - and this can corrupt the whole data.
Unplugged them and hooked them up to another PC so the chances of them ending up in the exact same order are lower than that of the opposite.
That’s quite a challenge on its own tbh. Guess I can kiss my data goodbye then? If it is than I’m going to reconsider doing the same thing again and might just get another disk and go for a dual raid 1.
Site does warn about not ommitting the N parameter
Caution –
Be sure to use the newfs -N in the next step. If you omit the -N option, you will create a new, empty file system.
So it should show it just fine… but it’s not installed and YaST / webpin come up blank when searching for it… so not quite sure how I would get it installed
Yeah same, can only find BSD/Solaris posts about it.
So if I don’t find a solution in the next 2 weeks then I’ll just wipe the disks clean and find out how much my ISP considers fair under their ‘fair use policy’
Well I’ll have to restore my files some way, and since my disks seem like a lost cause it will be over the internet… and hauling in over a terabyte is probably not something my ISP will appreciate