[opensuse] new hardware, system won't boot up in 2nd partion with RAID1 setup
Hi all, I just upgraded my hardware and I have RAID 1 set up and working on the first 2 partitions after swap of both my hard drives.It boots ok into the first RAID partition, /dev/md0, with openSUSE12.1. However, I am now unable to get my backup partition started on /dev/md2, where I have openSUSE 11.4 installed. When I try and boot into /dev/md2, my system gets past grub, but then as it is booting up, udev sets up device /dev/md126 on 2 drives (I don't know which RAID this is or where it gets the number 126), and then it cannot find the root drive. (It does not do that when I boot into /dev/md0, where I have openSUSE 12.1 installed.) When I select the 3rd option I set up on grub, to boot into openSUSE 11.4 on my degraded RAID, this is what shows up on the boot sequence: doing fast boot Creating device nodes with udev mdadm: /dev/md126 has been started with 2 drives. Trying manual resume from /dev/disk/by-label/swap2 Invoking userspace resume from /dev/disk/by-label/swap2 resume: libgcrypt version 1.4.6 Trying manual resume from /dev/disk/by-label/swap2 Invoking in-kernel resume from /dev/disk/by-label/swap2 Waiting for device /dev/disk/by-label/AltOldLinuxRoot to appear: .^[................................ Could not find /dev/disk/by-label/AltOldLinuxRoot. Want me to fall back to /dev/disk/by-label/root? (Y/n) So it never finds the RAID partition to boot into it, even though grub found it no problem (I had to set up the degraded RAID specifying metadata 1.0, because when I tried it with the default 1.2, the superblock is stored 4k from the start, so grub couldn't find the boot directory). Ok, here is some background. My partitions are set up as follows: Disk /dev/sda: 1000.2 GB, 1000204886016 bytes Device Boot Blocks Id System LABEL /dev/sda1 2095104 82 Linux swap / Solaris swap2 /dev/sda2 * 20973568 fd Linux raid autodetect linux-aw90:0 /dev/sda3 465306624 fd Linux raid autodetect linux-aw90:1 /dev/sda4 488385536 f W95 Ext'd (LBA) /dev/sda5 20971520 83 Linux root2 /dev/sda6 20971520 83 Linux /dev/sda7 446429184 83 Linux xtradata Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes Device Boot Blocks Id System LABEL /dev/sdb1 2095104 82 Linux swap / Solaris swap1 /dev/sdb2 20973568 fd Linux raid autodetect linux-aw90:0 /dev/sdb3 465306624 fd Linux raid autodetect linux-aw90:1 /dev/sdb4 488385536 5 Extended /dev/sdb5 20971520 fd Linux raid autodetect linux-aw90:2 /dev/sdb6 20971520 83 Linux roottemp /dev/sdb7 446429184 83 Linux newkde These are my RAID1 partitions Device Device RAID device LABEL /dev/sda2 /dev/sdb2 /dev/md0 root /dev/sda3 /dev/sdb3 /dev/md1 home /dev/sdb5 missing /dev/md2 AltOldLinuxRoot I have no problem being able to boot into /dev/md0, as this is my normal OS. What I am trying to do is also be able to boot into /dev/md2 while it is still a degraded RAID. Grub reads my menu.lst file just fine. This is the 3rd option I have setup in menu.lst, and I have copied just that section here: ###George's option on /dev/md2### title extended partition openSUSE 11.4 on /dev/md2 kernel (hd1,4)/boot/vmlinuz-2.6.37.6-0.9-desktop root=/dev/disk/by-label/AltOldLinuxRoot resume=/dev/disk/by-label/swap2 splash=silent quiet showopts vga=0x317 initrd (hd1,4)/boot/initrd-2.6.37.6-0.9-desktop Here is what my /etc/mdadm.conf looks like on the openSUSE 11.4 partition DEVICE containers partitions ARRAY /dev/md0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 name=linux-aw90:0 ARRAY /dev/md1 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f name=linux-aw90:1 ARRAY /dev/md2 UUID=9e211746:31896532:b4f86782:184e93f7 name=linux-aw90:2 So, any help getting my system to boot in my 11.4 degraded RAID partition? -- 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
On 2012/06/23 12:09 (GMT+0800) George Olson composed: ...
Trying manual resume from /dev/disk/by-label/swap2 ... So, any help getting my system to boot in my 11.4 degraded RAID partition?
I'm not pretending to know the answer to your problem, just providing suggestions to try. YaST makes life more difficult than it need be. Yours: title extended partition openSUSE 11.4 on /dev/md2 kernel (hd1,4)/boot/vmlinuz-2.6.37.6-0.9-desktop root=/dev/disk/by-label/AltOldLinuxRoot resume=/dev/disk/by-label/swap2 splash=silent quiet showopts vga=0x317 initrd (hd1,4)/boot/initrd-2.6.37.6-0.9-desktop 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. If nothing works, or maybe before you try the rest, try to get md2 rebuilt while running from md0. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 06/23/2012 06:57 PM, George Olson wrote:
On 06/23/2012 01:31 PM, Felix Miata wrote:
On 2012/06/23 12:09 (GMT+0800) George Olson composed:
...
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.
By doing a grep search, I found the following: linux-aw90:/boot/grub # grep -r "md126" /mnt/md/etc/ grep: /mnt/md/etc/alternatives/xulrunner: No such file or directory /mnt/md/etc/lvm/.cache: "/dev/md126", So in the lvm cache it stores /dev/md126. But am I even using lvm? I mean, I don't have dynamically sized partitions anywhere. Does RAID use lvm to keep track of what its partitions? The /mnt/md/etc/lvm.cache file starts with the line, # This file is automatically maintained by lvm. Still researching... -- 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
On 06/24/2012 09:15 AM, George Olson wrote:
On 06/23/2012 06:57 PM, George Olson wrote:
On 06/23/2012 01:31 PM, Felix Miata wrote:
On 2012/06/23 12:09 (GMT+0800) George Olson composed:
...
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.
By doing a grep search, I found the following:
linux-aw90:/boot/grub # grep -r "md126" /mnt/md/etc/ grep: /mnt/md/etc/alternatives/xulrunner: No such file or directory /mnt/md/etc/lvm/.cache: "/dev/md126",
So in the lvm cache it stores /dev/md126.
But am I even using lvm? I mean, I don't have dynamically sized partitions anywhere. Does RAID use lvm to keep track of what its partitions?
The /mnt/md/etc/lvm.cache file starts with the line, # This file is automatically maintained by lvm.
Still researching...
When I do a google search on RAID, all the hits are about how to set up RAID, or about how RAID keeps track of data. That information is not helpful for this problem. What I need to know is, how does a running system determine and keep track of what exactly is being used as RAID? If someone can point me to that, then perhaps I can figure out why my 11.4 is thinking that my RAIDed root directory is running actively on /dev/sda2 and /dev/sdb2 while in reality it is actively running on the single partition /dev/sdb5. Then I can perhaps work with the settings to get it running correctly. -- 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
On 06/24/2012 09:15 AM, George Olson wrote:
On 06/23/2012 06:57 PM, George Olson wrote:
On 06/23/2012 01:31 PM, Felix Miata wrote:
On 2012/06/23 12:09 (GMT+0800) George Olson composed:
...
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.
By doing a grep search, I found the following:
linux-aw90:/boot/grub # grep -r "md126" /mnt/md/etc/ grep: /mnt/md/etc/alternatives/xulrunner: No such file or directory /mnt/md/etc/lvm/.cache: "/dev/md126",
So in the lvm cache it stores /dev/md126.
But am I even using lvm? I mean, I don't have dynamically sized partitions anywhere. Does RAID use lvm to keep track of what its partitions?
The /mnt/md/etc/lvm.cache file starts with the line, # This file is automatically maintained by lvm.
Still researching...
When I do a google search on RAID, all the hits are about how to set up RAID, or about how RAID keeps track of data. That information is not helpful for this problem. What I need to know is, how does a running system determine and keep track of what exactly is being used as RAID? If someone can point me to that, then perhaps I can figure out why my 11.4 is incorrectly thinking that my RAIDed root directory is running actively on /dev/sda2 and /dev/sdb2 while in reality it is actively running on the single partition /dev/sdb5. Then I can perhaps work with the settings to get it running correctly. -- 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
On 2012/06/24 09:24 (GMT+0800) George Olson composed:
When I do a google search on RAID, all the hits are about how to set up RAID, or about how RAID keeps track of data. That information is not helpful for this problem. What I need to know is, how does a running system determine and keep track of what exactly is being used as RAID? If someone can point me to that, then perhaps I can figure out why my 11.4 is incorrectly thinking that my RAIDed root directory is running actively on /dev/sda2 and /dev/sdb2 while in reality it is actively running on the single partition /dev/sdb5. Then I can perhaps work with the settings to get it running correctly.
[Assuming MD RAID autodetect] I don't know how the autodetect mechanism works. But neither have I noticed you share either 12.1's or 11.4's /etc/mdadm.conf, or a comparison of the two. Maybe that's what you've missed? Maybe a boot using UUID for root= cmdline syntax would get you farther along? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/24/2012 09:40 AM, Felix Miata wrote:
On 2012/06/24 09:24 (GMT+0800) George Olson composed:
[Assuming MD RAID autodetect]
I don't know how the autodetect mechanism works. But neither have I noticed you share either 12.1's or 11.4's /etc/mdadm.conf, or a comparison of the two. Maybe that's what you've missed? Maybe a boot using UUID for root= cmdline syntax would get you farther along?
Ah yes, thanks for the reminder. Forgot to put that on the email. Here is 12.1's /etc/mdadm.conf: ARRAY /dev/md/0 metadata=1.0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 name=linux-aw90:0 ARRAY /dev/md/1 metadata=1.0 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f name=linux-aw90:1 ARRAY /dev/md/2 metadata=1.0 UUID=9e211746:31896532:b4f86782:184e93f7 name=linux-aw90:2 This is close to the mdadm --detail --scan running on 12.1: linux-aw90:/mnt/md/etc # mdadm --detail --scan ARRAY /dev/md0 metadata=1.0 name=linux-aw90:0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 ARRAY /dev/md/1 metadata=1.0 name=linux-aw90:1 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f ARRAY /dev/md/2 metadata=1.0 name=linux-aw90:2 UUID=9e211746:31896532:b4f86782:184e93f7 When I created the first RAID, yast created the mdadm.conf file, so when adding /dev/md2 I just made sure it followed the same format. I have read that you can simply run mdadm --detail --scan directly into the mdadm config file so they match exactly. And here is 11.4's /etc/mdadm.conf: DEVICE containers partitions ARRAY /dev/md0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 name=linux-aw90:0 ARRAY /dev/md1 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f name=linux-aw90:1 ARRAY /dev/md2 UUID=9e211746:31896532:b4f86782:184e93f7 name=linux-aw90:2 I have just tried rebooting like I did before into /dev/sdb5 and also with the UUID for root in the menu.lst syntax, and neither one will boot up now. I did not make any changes to the disk and it booted up before, so maybe something is corrupted on the partition. Do you think that is possible? -- 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
On 06/24/2012 05:10 PM, George Olson wrote:
On 06/24/2012 09:40 AM, Felix Miata wrote:
On 2012/06/24 09:24 (GMT+0800) George Olson composed:
[Assuming MD RAID autodetect]
I don't know how the autodetect mechanism works. But neither have I noticed you share either 12.1's or 11.4's /etc/mdadm.conf, or a comparison of the two. Maybe that's what you've missed? Maybe a boot using UUID for root= cmdline syntax would get you farther along?
Ah yes, thanks for the reminder. Forgot to put that on the email. Here is 12.1's /etc/mdadm.conf:
ARRAY /dev/md/0 metadata=1.0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 name=linux-aw90:0 ARRAY /dev/md/1 metadata=1.0 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f name=linux-aw90:1 ARRAY /dev/md/2 metadata=1.0 UUID=9e211746:31896532:b4f86782:184e93f7 name=linux-aw90:2
This is close to the mdadm --detail --scan running on 12.1: linux-aw90:/mnt/md/etc # mdadm --detail --scan ARRAY /dev/md0 metadata=1.0 name=linux-aw90:0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 ARRAY /dev/md/1 metadata=1.0 name=linux-aw90:1 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f ARRAY /dev/md/2 metadata=1.0 name=linux-aw90:2 UUID=9e211746:31896532:b4f86782:184e93f7
When I created the first RAID, yast created the mdadm.conf file, so when adding /dev/md2 I just made sure it followed the same format. I have read that you can simply run mdadm --detail --scan directly into the mdadm config file so they match exactly.
And here is 11.4's /etc/mdadm.conf: DEVICE containers partitions ARRAY /dev/md0 UUID=e96a14ed:bc7c8d5a:9b0c114a:9e208631 name=linux-aw90:0 ARRAY /dev/md1 UUID=cdfe9dc0:73d6f7cb:7dda2c20:e3758f4f name=linux-aw90:1 ARRAY /dev/md2 UUID=9e211746:31896532:b4f86782:184e93f7 name=linux-aw90:2
I have just tried rebooting like I did before into /dev/sdb5 and also with the UUID for root in the menu.lst syntax, and neither one will boot up now. I did not make any changes to the disk and it booted up before, so maybe something is corrupted on the partition. Do you think that is possible?
Wait, I did change one thing, but I made the change in 12.1, not in 11.4. I put a line in /etc/fstab in 12.1 to automatically mount the partition when I boot up into 12.1. But that should not make any difference, right? Here is the line I added to /etc/fstab: /dev/disk/by-label/AltOldLinuxRoot /mnt/md ext4 acl,user_xattr 1 2 -- 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
participants (2)
-
Felix Miata -
George Olson