On 06/23/2012 01:31 PM, Felix Miata wrote:
On 2012/06/23 12:09 (GMT+0800) George Olson composed:
...
is the YaST way, which I do this way instead, partly by altering /etc/sysconfig/bootloader, and partly manually: title openSUSE 11.4 on /dev/md2 kernel (hd1,4)/boot/vmlinuz showopts root=LABEL=AltOldLinuxRoot noresume splash=verbose vga=0x317 initrd (hd1,4)/boot/initrd
The difference (mainly showopts position before root=) allows to more easily edit all of cmdline on fly at Grub menu time to aid troubleshooting. Add the above as an additional stanza to your menu.lst - but - add it to your 12.1's menu.lst instead. Then, add this one also: title openSUSE 11.4 on md2 as sda5 kernel (hd0,4)/boot/vmlinuz showopts root=LABEL=AltOldLinuxRoot noresume splash=verbose vga=0x317 initrd (hd0,4)/boot/initrd
Try them both and see if one, or both, work, and watch the boot messages carefully if they don't for more clues than you're probably seeing with splash=silent. If neither work, try substituting root=/dev/sdb5 and root=/dev/sda5 and root=/dev/md2, on the fly in Grub's Gfxmenu as additional tries.
Thanks for the help. I changed the command line to root=/dev/sdb5 and it booted up into 11.4. However, it was really weird, because this is what the indications all showed: Mounted devices: linux-aw90:/home/george # mount devtmpfs on /dev type devtmpfs (rw,relatime,size=8064072k,nr_inodes=2016018,mode=755) tmpfs on /dev/shm type tmpfs (rw,relatime) /dev/sdb5 on / type ext4 (rw,relatime,user_xattr,acl,barrier=1,stripe=1,data=ordered) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) /dev/md1 on /home type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) gvfs-fuse-daemon on /home/george/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100) So you see, /dev/sdb5 is mounted and running. This is my root directory in 11.4. However, when I run mdadm --detail --scan, here is what I get: linux-aw90:/home/george # mdadm --detail --scan ARRAY /dev/md126 metadata=1.0 name=linux-aw90:0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 ARRAY /dev/md1 metadata=1.0 name=linux-aw90:1 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f So you see that my raid drive is listed as /dev/md126. Note above that it was not mounted. And, so I had to see what was going on in /dev/md126: linux-aw90:/home/george # mdadm --detail /dev/md126 /dev/md126: Version : 1.0 Creation Time : Mon Sep 19 13:44:31 2011 Raid Level : raid1 Array Size : 20973496 (20.00 GiB 21.48 GB) Used Dev Size : 20973496 (20.00 GiB 21.48 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Sat Jun 23 15:56:00 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : linux-aw90:0 (local to host linux-aw90) UUID : e96a14ed:bc7c8d5a:9b0c114a:9e208631 Events : 9623 Number Major Minor RaidDevice State 2 8 18 0 active sync /dev/sdb2 1 8 2 1 active sync /dev/sda2 So you see that even though I told grub to boot on /dev/sda5, the RAID controller thinks it is running on /dev/sda2 and /dev/sdb2, and it thinks that both of these are running, as you see there are 2 active devices listed. I sort of think I know where this comes from - back before I upgraded to 12.1, I was running 11.4 in a RAID 1 on /dev/sda1 and /dev/sda2. When I wanted to upgrade, I rsynced my root directory to /dev/sda5 (I only had 1 TB drive with extended partitions at the time), and then upgraded /dev/sda2 and /dev/sdb2 (RAIDED together as /dev/md126) to 12.1. Somewhere in the copy over to the single partition, it kept the configuration so that when it booted up, it still thought it was running as RAID. I just never noticed it when I booted into 11.4 from time to time, because at the time I always thought I was running only on a single partition. Now I have taken that 11.4 partition and copied it to a single degraded RAID partition, and I have not yet joined it to another partition, and the whole system is confused. It boots up on a single partition, but it thinks it is running as RAID. So the question is, where in all the different configuration files is it listed that I am running on /dev/sda2 and /dev/sdb2? I am sure there is some file on /dev/sdb2 that indicates this, and if I could go in and edit it, I might be able to make this work. -- G.O. Box #1: 12.1 | KDE 4.8.4 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB Box #2: 12.1 | KDE 4.8.4 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB Laptop: 12.1 | KDE 4.8.3 | Core2 Duo T8100 | 64 | Intel 965GM | 4GB RAM learning openSUSE and loving it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org