[opensuse] GRUB Help - Howto boot 10.3 RAID 1 hardware SATA controller ?
Listmates, I can't get grub to boot a fresh 10.3 install from my promise SATA raid controller with two new 320G drives in RAID 1. I thought I knew GRUB, but RAID is completely new to me. I really, really need HELP! I have included as much information as I can including the screen messages display during boot below. If I can send anything else, please just let me know. Hardware: MSI K7N2 Delta-ILSR motherboard (RAID O or 1 is supported on ATA133+SATA H/D or 2 SATA H/D); AthlonXP2800+; 1G ram; 1 Maxtor 80G ATA drive (sda); 2 Seagate 320G drives in raid 1 (sdb, sdc) Partitions: sda: sda1 56G NTFS, sda5 1G linux swap, sda6 NTFS sdb: sdb1 79M ext3 /boot, sdb2 20G ext3 /, sdb3 270G /home sdc: sdc1 79M ext3 /boot, sdc2 20G ext3 /, sdc3 270G /home sdb and sdc were blank unformatted disks prior to install. Yast Install Partitioner saw sdb and sdc and created sdb and sdc 1-3 when yast selected the following partition scheme during install: 79M ext3 /dev/mapper/bfefdifda_part1 20G ext3 /dev/mapper/bfefdifda_part2 270G ext3 /dev/mapper/bfefdifda_part3 Yast correctly saw the raid during install and the install worked perfectly through partitioning and software installation. The first required reboot is where everything fell apart. Upon reboot the following error is received Booting from local disk... GRUB Loading stage 1.5. GRUB loading, please wait... Error 17 The system then freezes. Booting from the install DVD crashes out of the graphic install due to the hosed repair install on the DVD, but at least gets back to the basic screen that allows you to boot an existing installation. Here you can NOT select /dev/mapper/<part1,2 or 3>. Yast sees sdb1, sdb2, sdb3, sdc1, sdc2, sdc3. The system will boot if you select either sdb2 or sdc2, but the boot fails after it tries to mount /boot and /home. You are then left with the "press enter to login" that gets you to the repair mode prompt. The screen messages shown are: mount mtab /dev/mapper/bfefdifda_part2 already mounted on / activating device mapper waiting for /dev/mapper/bfefdifda_part1: No such file or directory fsck.ext3: No such file of directory while trying to open /dev/mapper/bfefdifda_part1 /dev/mapper/bfefdifda_part1: The superblock could not be read of 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> error on stat() /dev/mapper/bfefdifda_part1: no such file or directory error on stat() /dev/mapper/bfefdifda_part3: no such file or directory fsck.ext3: No such file of directory while trying to open /dev/mapper/bfefdifda_part3 /dev/mapper/bfefdifda_part3: The superblock could not be read of 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> error on stat() /dev/mapper/bfefdifda_part3: no such file or directory fsck.ext3 /dev/mapper/bfefdifda_part3 failed (status 0x8). Run Manually! /dev/disc/by-id/scsi-SATA_ST3320620AS_6QIS96D-Part1 has gone 49710 days without being checked, check forced. (..the check stuff here) /dev/disc/by-id/scsi-SATA_ST3320620AS_6QIS96D-Part3 has gone 49710 days without being checked, check forced. (..the check stuff here) blogd: No message logging because /var is not accessible fsck failed for at least 1 filesystem (not /) Press enter for login: I then go into repair mode and run yast2. The partitioner lists the following: Partition Type Mount /dev/sda IC35L080AVVA07-0 /dev/sda1 HPFS/NTFS /windows/C /dev/sda2 Extended /dev/sda5 Linux Swap swap /dev/sda6 HPFS/NTFS /windows/D /dev/sdb ST3320620AS /dev/sdb1 Linux Native /dev/sdb2 Linux Native /dev/sdb3 Linux Native /dev/sdc ST3320620AS /dev/sdc1 Linux Native /dev/sdc2 Linux Native / /dev/sdc3 Linux Native I can set the Mount Point for /boot (sdb1 or sdc1) and /home (sdb3 or sdc3) but there is no way to tell the system that it is in raid here. You obviously can't set both sdb1 and sdc1 as /boot. You can select "Linux RAID" as the fs type, but I have no clue what this would do and it give a very stern warning about setting it here. Running the yast bootloader module yields a "blank" bootloader scheme. I can go to "other" and select Propose a new scheme, but that results in it trying to boot from an image on /sdc2 but there is no way to get it to boot from a /boot partition because none are mounted at the time. I am in a holy mess here and I need help! I'll continue to google for a solution, but if anyone knows how to fix this mess please post any help you can. Thanks! -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin pecked at the keyboard and wrote:
Listmates,
I can't get grub to boot a fresh 10.3 install from my promise SATA raid controller with two new 320G drives in RAID 1. I thought I knew GRUB, but RAID is completely new to me. I really, really need HELP! I have included as much information as I can including the screen messages display during boot below. If I can send anything else, please just let me know.
Hardware: MSI K7N2 Delta-ILSR motherboard (RAID O or 1 is supported on ATA133+SATA H/D or 2 SATA H/D); AthlonXP2800+; 1G ram; 1 Maxtor 80G ATA drive (sda); 2 Seagate 320G drives in raid 1 (sdb, sdc)
Partitions:
sda: sda1 56G NTFS, sda5 1G linux swap, sda6 NTFS sdb: sdb1 79M ext3 /boot, sdb2 20G ext3 /, sdb3 270G /home sdc: sdc1 79M ext3 /boot, sdc2 20G ext3 /, sdc3 270G /home
sdb and sdc were blank unformatted disks prior to install. Yast Install Partitioner saw sdb and sdc and created sdb and sdc 1-3 when yast selected the following partition scheme during install:
79M ext3 /dev/mapper/bfefdifda_part1 20G ext3 /dev/mapper/bfefdifda_part2 270G ext3 /dev/mapper/bfefdifda_part3
Yast correctly saw the raid during install and the install worked perfectly through partitioning and software installation. The first required reboot is where everything fell apart. Upon reboot the following error is received
Booting from local disk... GRUB Loading stage 1.5.
GRUB loading, please wait... Error 17
The system then freezes. Booting from the install DVD crashes out of the graphic install due to the hosed repair install on the DVD, but at least gets back to the basic screen that allows you to boot an existing installation. Here you can NOT select /dev/mapper/<part1,2 or 3>. Yast sees sdb1, sdb2, sdb3, sdc1, sdc2, sdc3. The system will boot if you select either sdb2 or sdc2, but the boot fails after it tries to mount /boot and /home. You are then left with the "press enter to login" that gets you to the repair mode prompt. The screen messages shown are:
mount mtab /dev/mapper/bfefdifda_part2 already mounted on / activating device mapper waiting for /dev/mapper/bfefdifda_part1: No such file or directory
fsck.ext3: No such file of directory while trying to open /dev/mapper/bfefdifda_part1 /dev/mapper/bfefdifda_part1: The superblock could not be read of 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>
error on stat() /dev/mapper/bfefdifda_part1: no such file or directory error on stat() /dev/mapper/bfefdifda_part3: no such file or directory
fsck.ext3: No such file of directory while trying to open /dev/mapper/bfefdifda_part3 /dev/mapper/bfefdifda_part3: The superblock could not be read of 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>
error on stat() /dev/mapper/bfefdifda_part3: no such file or directory fsck.ext3 /dev/mapper/bfefdifda_part3 failed (status 0x8). Run Manually! /dev/disc/by-id/scsi-SATA_ST3320620AS_6QIS96D-Part1 has gone 49710 days without being checked, check forced. (..the check stuff here) /dev/disc/by-id/scsi-SATA_ST3320620AS_6QIS96D-Part3 has gone 49710 days without being checked, check forced. (..the check stuff here)
blogd: No message logging because /var is not accessible fsck failed for at least 1 filesystem (not /) Press enter for login:
I then go into repair mode and run yast2. The partitioner lists the following:
Partition Type Mount /dev/sda IC35L080AVVA07-0 /dev/sda1 HPFS/NTFS /windows/C /dev/sda2 Extended /dev/sda5 Linux Swap swap /dev/sda6 HPFS/NTFS /windows/D /dev/sdb ST3320620AS /dev/sdb1 Linux Native /dev/sdb2 Linux Native /dev/sdb3 Linux Native /dev/sdc ST3320620AS /dev/sdc1 Linux Native /dev/sdc2 Linux Native / /dev/sdc3 Linux Native
I can set the Mount Point for /boot (sdb1 or sdc1) and /home (sdb3 or sdc3) but there is no way to tell the system that it is in raid here. You obviously can't set both sdb1 and sdc1 as /boot. You can select "Linux RAID" as the fs type, but I have no clue what this would do and it give a very stern warning about setting it here.
Running the yast bootloader module yields a "blank" bootloader scheme. I can go to "other" and select Propose a new scheme, but that results in it trying to boot from an image on /sdc2 but there is no way to get it to boot from a /boot partition because none are mounted at the time.
I am in a holy mess here and I need help! I'll continue to google for a solution, but if anyone knows how to fix this mess please post any help you can. Thanks!
Please post the contents of /boot/grub/device.map and /boot/grub/menu.lst -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ken Schneider wrote:
Please post the contents of /boot/grub/device.map and /boot/grub/menu.lst
God I hope you can help with this mess. Here are the files! (thank God I could get the network up even though install has never gotten to the point of setting the root password or users) device.map (fd0) /dev/fd0 (hd0) /dev/sda (hd2) /dev/sdc (hd1) /dev/sdb menu.lst # Modified by YaST2. Last modification on Sun Dec 23 13:57:41 UTC 2007 default 1 timeout 8 gfxmenu (hd1,0)/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 root (hd1,0) kernel /vmlinuz-2.6.22.5-31-default root=/dev/sdb2 resume=/dev/sda5 splash=silent showopts initrd /initrd-2.6.22.5-31-default ###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.3 (/dev/sdc1)### title openSUSE 10.3 (/dev/sdc1) root (hd2,0) configfile /boot/grub/menu.lst ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd1,0) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd1,0) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 root (hd1,0) kernel /vmlinuz-2.6.22.5-31-default root=/dev/sdb2 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /initrd-2.6.22.5-31-default ###Don't change this comment - YaST2 identifier: Original name: Kernel-2.6.22.5-31-default### title Kernel-2.6.22.5-31-default root (hd1,0) kernel /vmlinuz-2.6.22.5-31-default root=/dev/sdb2 resume=/dev/sda5 splash=silent showopts initrd /initrd-2.6.22.5-31-default /etc/grub.conf setup --stage2=/boot/grub/stage2 (hd0) (hd1,0) quit -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin pecked at the keyboard and wrote:
Ken Schneider wrote:
Please post the contents of /boot/grub/device.map and /boot/grub/menu.lst
God I hope you can help with this mess. Here are the files! (thank God I could get the network up even though install has never gotten to the point of setting the root password or users)
device.map
(fd0) /dev/fd0 (hd0) /dev/sda (hd2) /dev/sdc (hd1) /dev/sdb
menu.lst
# Modified by YaST2. Last modification on Sun Dec 23 13:57:41 UTC 2007 default 1 timeout 8 gfxmenu (hd1,0)/message
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 root (hd1,0) kernel /vmlinuz-2.6.22.5-31-default root=/dev/sdb2 resume=/dev/sda5 splash=silent showopts initrd /initrd-2.6.22.5-31-default
###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.3 (/dev/sdc1)### title openSUSE 10.3 (/dev/sdc1) root (hd2,0) configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd1,0) chainloader (hd0,0)+1
###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd1,0) chainloader (fd0)+1
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 root (hd1,0) kernel /vmlinuz-2.6.22.5-31-default root=/dev/sdb2 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /initrd-2.6.22.5-31-default
###Don't change this comment - YaST2 identifier: Original name: Kernel-2.6.22.5-31-default### title Kernel-2.6.22.5-31-default root (hd1,0) kernel /vmlinuz-2.6.22.5-31-default root=/dev/sdb2 resume=/dev/sda5 splash=silent showopts initrd /initrd-2.6.22.5-31-default
/etc/grub.conf
setup --stage2=/boot/grub/stage2 (hd0) (hd1,0) quit
I can't help further, just wanted to check for the obvious. For a repair cd for 10.3 check here: ftp://beta.suse.com/private/10.3-repair-mini it may help your situation. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ken Schneider wrote:
David C. Rankin pecked at the keyboard and wrote:
quit
I can't help further, just wanted to check for the obvious. For a repair cd for 10.3 check here: ftp://beta.suse.com/private/10.3-repair-mini it may help your situation.
Where is the repair mini ISO? I can't find it at the link you provide or at opensuse? Any other hiding places? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon December 24 2007 09:32, David C. Rankin wrote:
Where is the repair mini ISO? I can't find it at the link you provide or at opensuse?
He pointed to the directory that has the 3 versions of the mini ISO. Here is the link directly to the i386 version: ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-i386.iso And here is its MD5SUM: 6d1ee833396ba5234ca4fe490a6f7b56 openSUSE-10.3-Repair-mini-i386.iso -- Carlos FL Who is General Failure, and why is he reading my disk? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007/12/24 16:01 (GMT-0700) Carlos F Lange apparently typed:
On Mon December 24 2007 09:32, David C. Rankin wrote:
Where is the repair mini ISO? I can't find it at the link you provide or at opensuse?
He pointed to the directory that has the 3 versions of the mini ISO. Here is the link directly to the i386 version: ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-i386.iso
And here is its MD5SUM: 6d1ee833396ba5234ca4fe490a6f7b56 openSUSE-10.3-Repair-mini-i386.iso
Maybe he couldn't find it because ftp://beta.suse.com/private/ shows empty. To fetch things like that I commonly use the ftp component of mc. I had do cd 10.3-repair-mini to see the isos and MD5SUMS file. Then when I tried to copy them, mc couldn't open them. -- Jesus Christ, the reason for the season. Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata pecked at the keyboard and wrote:
On 2007/12/24 16:01 (GMT-0700) Carlos F Lange apparently typed:
On Mon December 24 2007 09:32, David C. Rankin wrote:
Where is the repair mini ISO? I can't find it at the link you provide or at opensuse?
He pointed to the directory that has the 3 versions of the mini ISO. Here is the link directly to the i386 version: ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-i386.iso
And here is its MD5SUM: 6d1ee833396ba5234ca4fe490a6f7b56 openSUSE-10.3-Repair-mini-i386.iso
Maybe he couldn't find it because ftp://beta.suse.com/private/ shows empty. To fetch things like that I commonly use the ftp component of mc. I had do cd 10.3-repair-mini to see the isos and MD5SUMS file. Then when I tried to copy them, mc couldn't open them.
I provided ftp://beta.suse.com/private/10.3-repair-mini so that David could choose the version he needed. Why he would need a link to a specific one I don't know. Or he didn't cut and paste the info correct. It seemed simple enough to just click on the link I provided. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
man, 24.12.2007 kl. 17.28 -0500, skrev Ken Schneider:
I provided ftp://beta.suse.com/private/10.3-repair-mini so that David could choose the version he needed. Why he would need a link to a specific one I don't know. Or he didn't cut and paste the info correct. It seemed simple enough to just click on the link I provided.
It shows empty in firefox, but opening the link in nautilus (and probably any "proper" ftp-client shows the images. Pretty sure this is the source of the confusion. Bjørn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bjørn Lie wrote:
man, 24.12.2007 kl. 17.28 -0500, skrev Ken Schneider:
I provided ftp://beta.suse.com/private/10.3-repair-mini so that David could choose the version he needed. Why he would need a link to a specific one I don't know. Or he didn't cut and paste the info correct. It seemed simple enough to just click on the link I provided.
It shows empty in firefox, but opening the link in nautilus (and probably any "proper" ftp-client shows the images. Pretty sure this is the source of the confusion.
Bjørn
I finally found it in gftp. You _cannot_ look in the ../private directory and see anything. You must go directly to the ../private/10.3-repair-mini to see it. For people used to navigating down a directory path, it is invisible. For others if you need it, just get it with wget: i386: wget -b ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-i386.iso ppc: wget -b ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-ppc.iso x86_64: wget -b ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-x86_64.iso Now we will see if it can fix the raid problem (fingers crossed) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin pecked at the keyboard and wrote:
Bjørn Lie wrote:
man, 24.12.2007 kl. 17.28 -0500, skrev Ken Schneider:
I provided ftp://beta.suse.com/private/10.3-repair-mini so that David could choose the version he needed. Why he would need a link to a specific one I don't know. Or he didn't cut and paste the info correct. It seemed simple enough to just click on the link I provided.
It shows empty in firefox, but opening the link in nautilus (and probably any "proper" ftp-client shows the images. Pretty sure this is the source of the confusion.
Bjørn
I finally found it in gftp. You _cannot_ look in the ../private directory and see anything.
Which is why I provided a link directly to the directory with the contents. You must go directly to the
../private/10.3-repair-mini to see it.
Which is exactly what I provided in the first place because "../private" shows as empty.
For people used to navigating down a directory path, it is invisible. For others if you need it, just get it with wget:
i386:
wget -b ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-i386.iso
ppc:
wget -b ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-ppc.iso
x86_64:
wget -b ftp://beta.suse.com/private/10.3-repair-mini/openSUSE-10.3-Repair-mini-x86_64.iso
Now we will see if it can fix the raid problem (fingers crossed)
-- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Now we will see if it can fix the raid problem (fingers crossed)
No dice, raid problem remain. Repair iso doesn't deal with raid issues. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin pecked at the keyboard and wrote:
David C. Rankin wrote:
Now we will see if it can fix the raid problem (fingers crossed)
No dice, raid problem remain. Repair iso doesn't deal with raid issues.
bummer! Sorry to hear that. I suppose the only option left is a re-install. Do that but don't format any filesystems when installing. Sometimes that will get through some problems. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Bjørn Lie -
Carlos F Lange -
David C. Rankin -
Felix Miata -
Ken Schneider