Hi Folks, (forgive the top-post, I think it appropriate in this case) I figured out an acceptable solution for the wandering disk designations. The "expert" partition manager in the installation process has an option that I haven't used before that allows mounting of partitions by label or uuid. I've used labels in the past for this kind of server, but only after it was up and running. The partition manager allows configuration during install time. The system disk device still changed from sde to sda, but it didn't matter. I created boot, swap, root and home partition labels, the system automatically mounted the other raid arrays by uuid. I'm happy and up again. Thanks for the suggestions. Regards, Lew Wolfgang Lew Wolfgang wrote:
Lew Wolfgang wrote:
I'm having a problem installing 10.3 x86_64 on a box with many raid disk controllers and disks. It has two disks mounted in the back that are supposed to be the system disks, configured as a raid1 mirror. Alas, this disk shows up after all the other disks, in this particular case as /dev/sde instead of /dev/sda.
A full install goes well until the first boot. The boot fails saying it can't find /dev/sde3 (the root partition). It eventually drops into a limited sh shell running out of ram.
This box worked ok when the system disk appeared as /dev/sdc. I wonder if there is some bug about booting from disks too far removed from /dev/sda?
Hi Folks,
I've got some more to report on my first-boot failure on a fresh 10.3 install.
Someone, (sorry, I couldn't find your email) suggested booting with "acpi=off irqpool". This had no effect.
Then, I tried Ian Marller's suggestion of editing /etc/sysconfig/kernel from a rescue boot. The mkinitrd invocation failed (yes, I chrooted). Adding 3w_xxxx and such to the kernel boot line also had no effect.
Soooo, recall that this is the first boot during the install procedure on the 10.3 DVD, right after all the packages have been loaded. There isn't too much I could have done up to this point to have fouled things up, so this really smells like a bug.
I've got three three 8-port 3-ware controllers (24-SATA disks total) and one 2-port 3-ware controller for the system disk. The current configuration has five raid units, and are reported as sda through sde in the install expert partition screen. The 2-disk system raid appears as sde to the partitioner, and is configured with sde1 (boot) sde2 (swap) sde3 (/) and sde4 (/export/home). There doesn't seem to be any way for me to configure things so that the 2-disk raid shows up as sda, where it should be.
Now, here's some further info: After the failed boot it's possible to escape to a very limited shell. At this point the boot failed because it couldn't find sde3, the system root partition. From this limited shell I looked at /dev/sd* and found that sda1-4 exists, but only one partition on sde1. So it looks like my system partition is now showing up as sda!!! WTFO? /etc/fstab had the system partitions on sde, so I booted the rescue system again and edited fstab, changing sde to sda. Alas, this also didn't work.
Not being a grub expert, I'm now at a loss. Any suggestions?
Thanks, Lew Wolfgang
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org