RAID Problems on boot Kernel: 2.4.32-sparc-r2

endemic · n00b Joined: 06 Oct 2003 Posts: 23 Location: Dayton, OH

After upgrading my Ultra 60 I am unable to mount my RAID1 array to / on boot. Here is what happens during boot:

overkll · Posted: Sat Apr 22, 2006 4:57 pm Post subject:

Looking at your boot log, fsck.ext3 is being called, but the error message is for an ext2 partition.

Do you have an ext3 or ext2 partition on the md devices?

I don't have a sparc, but I did see a similar error message when I was converting my raid devices from reiserfs to ext3. If I remember correctly, mke2fs was the issue. I thought I was making ext3 files system with the command

endemic · n00b Joined: 06 Oct 2003 Posts: 23 Location: Dayton, OH

The md device is most certainly ext3. This is the first kernel I've experienced this issue with.

Here is the output of tune2fs -l /dev/md0:

overkll · Posted: Sun Apr 23, 2006 2:30 pm Post subject:

endemic · n00b Joined: 06 Oct 2003 Posts: 23 Location: Dayton, OH

Yeah, I've tried so many different things thinking I was doing something stupid with fstab... The old kernel image mounts it fine with fstab the way it is. I'll change it anyways just to be correct.

I'm wondering if it could be a bug with this version of sparc sources?

starrbuck · Posted: Wed Apr 26, 2006 9:19 pm Post subject:

This issue just started for me, however, my 2.4.32-sparc-r2 is working fine while my 2.4.32-sparc-r4 is broken as described here.

I got around the issue for now by disabling the bootup file system check for root:

overkll · Posted: Thu Apr 27, 2006 6:34 pm Post subject:

Have y'all check bugs.gentoo.org for this bug? If there isn't one, maybe y'all should report this do the devs.

starrbuck · Posted: Thu Apr 27, 2006 6:57 pm Post subject:

This bug appears to describe the issue but it hasn't been touched since last month.

The SPARC devs read this forum, so between the bug and this message thread, I'm confident they are at least aware of it.
_________________
Gentoo Linux is groovy, baby! Yeah!

NetrixTardis · n00b Joined: 21 Sep 2004 Posts: 12 Location: Selma, TX

my findings are as followed:

the changes with tune2fs recommended by overkll didn't change anything. the changes to the fstab for the / (root) to 0 0 "fixed" the issue. however, if you force a fsck upon reboot, back to the same error. so, for the temp fix, just edit your /etc/fstab, and change the check/dump to "0 0" for the time being to get your box working with 2.4.32-r4. just don't attempt to force a fsck. in this case, reboot to the old kernel (you do keep a backup kernel to boot from don't you? <G>) so that it may run with the fsck, then boot back into -r4.

hopefully, some sparc devs are looking at this...

NetrixTardis

ps. tested and working on a Sun Ultra1-170E.

markpr · n00b Joined: 07 Nov 2004 Posts: 26

That's great info. I had the same problems tried several rebuilds and came up with the same worakround (no fsck). This just wasn't good enough for me so I scrapped my plans for some servers and went back to Solaris and SVM. I'm now going to go with your suggestion and after building with r4 I'll build an r2 kernel just-in-case. I had abandoned raid on gentoo-sparc unti this problem was better understand.. but this is good enough for now.

starrbuck · Posted: Sat Apr 29, 2006 9:36 pm Post subject:

Excellent advice, NetrixTardis. I always keep the previous kernel around for issues like this. Hopefully by the next kernal release the issue will be repaired, but if not I can keep the r2 kernel around for its properly-working fsck.
_________________
Gentoo Linux is groovy, baby! Yeah!

gaidh · n00b Joined: 23 Jun 2006 Posts: 4

Just to add a little confirmation, I've got the same problem on an Enterprise 220R (2xT1 UltraSparc II, 2GB mem, 2x 37GB U160s on a SYM53C875).

I tried setting up root raid1 (which I've done may times on other archs) during system install, and it all went smooth until rebooting. At that time I received exactly what is described in the first post on this thread: fsck.ext3 errors relating to a corrupt superblock. `tune2fs -l /dev/md0` would also give the corrupt superblock error. However, if I boot under the liveCD (2006.0) and assemble the device there, fsck and tune2fs would work perfectly. It seems most likely to be a problem with the way md assembles the array at boot time, which is different from the way it is done after the system has booted.

I tried both 2.4.32-gentoo-r2 and r4, both give the same problem. Unfortunately I don't have a source tree or an image from an earlier kernel, as this is a fresh install. Can someone provide a source tree for sparc-sources-2.4.23 or a similar version (which seems to work)? If I can confirm that this kernel works (as described in the first post) I'll do some hunting for where it went wrong (unless someone is already doing this, which I don't see any indication of).

Weeve · Retired Dev Joined: 30 Oct 2002 Posts: 641

For folks having problems, what do your silo.conf files look like?

P3SM · Posted: Thu Jun 29, 2006 11:07 am Post subject:

Just my 2c but I had a similar problem with my Raid 1 that was working fine until reboot, giving corrupt superblocks. I solved it by rewriting the superblocks and resizing the array. Never showed up again

Not sure if this is the same thing though :?:

_________________
Smaug: Sun Netra T1 105, UltraSPARC-IIi 440MHz, 512MB, 2*36GB 10kRPM; 2 Sun Netra D130: 6*36GB 10kRPM, swraid 0
Haku: Dual P3 Xeon 500MHz, 512MB; Sun Multipack: 12*18GB 10kRPM, hwraid 5
Falkor: Sun SparcStation LX, 128 MB, 2.1GB