https://bugzilla.novell.com/show_bug.cgi?id=350573
Summary: 10.3 Promise pdc2036 Raid Install Crashes after
Partitioning and Software Install
Product: openSUSE 10.3
Version: Final
Platform: i686
OS/Version: openSUSE 10.3
Status: NEW
Severity: Major
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: drankinatty@suddenlinkmail.com
QAContact: jsrain@novell.com
Found By: Customer
Promise fast trak 376 (pdc20376) raid 1 crashes install after yast gets through
partitioning and software install. The rebooted system fails to recognize the
raid although the install up to that point went fine. I have included as much
information as I can including the screen messages displayed 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); Promise fast trak 376
pdc20376) controller.
Partitions (sda existed sdb,sdc created by yast on install:
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 selecting 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 and rescue on the DVD, but
at least booting from the dvd gets back to the basic screen that allows you to
boot an existing installation. Here you can NOT select /dev/mapper/. 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:
The problem seems to be a failure of the second part of the install to
honor the raid designations seen by the initial install. To me it seems that
the system should mount /boot, /, and /home as /dev/mapper/bfefdifda_part1,
/dev/mapper/bfefdifda_part2, and /dev/mapper/bfefdifda_part3, respectively.
However, the system fails to recognize /dev/mapper/bfefdifda_part1 or
/dev/mapper/bfefdifda_part3 on reboot. Why???
Booting from the install medium and "crashing" back to being able to
boot an existing installation or system, I then go into maintenance 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
All correct, but no RAID seen or options to recognize a raid are given.
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, (or Merge and propose) 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. You
can manually set and then mount them with mount -a, but that will never allow
you to mount the raid by setting /dev/mapper/bfefdifda_part1 as /boot,
/dev/mapper/bfefdifda_part2 as /, or /dev/mapper/bfefdifda_part3 as /home. It's
FUBAR.
The config files involved are:
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 am in a holy mess here and I need help! After the first part of the
install went well, it looked like the all was well. But, after the software
install, and the first required reboot, all hell broke loose. What designations
should be in the menu.lst, device.map or in the /dev system for that matter to
make this work?
Again, just let me know what else you want to look at and I'll be glad
to send. But since this is a backup system for the office, I need to get it
running again ASAP. Direct emails of any tips or tricks are also welcomed.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
