| View previous topic :: View next topic |
| Author |
Message |
PegasusNZ
n00b
Joined: 30 Apr 2011
Posts: 8
|
 Posted: Sat Apr 30, 2011 11:31 am Post subject: Install from live CD raid1 quickstart guide failed |
 |
|
Hi All
I have a gentoo install on a supermicro pc with 2 systemdrives mirrored and 14x2TB raid5
all is going well when I boot off a live CD
When I try to boot off the system drive I have a few errors
Grub works fine and all the modules seem to load sorry I am a bit of a newbee
mdadm: complains about
error opening /dev/md/1
error opening /dev/md/3
error opening /dev/md/4
grub is configured to mount real_root=/dev/md3
and I end up with the horrid failed to mount /newroot
I am so close to a working system what have I missed?
_________________
I wish it would boot |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sat Apr 30, 2011 2:28 pm Post subject: |
|
|
PegasusNZ,
Welcome to Gentoo.
How do you assemble your raid volumes before you try to mount them?
The kernel auto assemble option only works with partitions type fd and raid superblock version 0.9.
This is no longer the defualt superblock version.
If you use raid superblock version 1.2, you need an initrd to to run mdadm to assemble your root filesystem before root can be mounted.
Run mdadm -E on one of the partitions you have donated to a raid set. Something like | Code: | $ sudo mdadm -E /dev/sda1
Password:
/dev/sda1:
Magic : a92b4efc
Version : 0.90.00 |
at the top of the output, shows the superblock version. In my case, 0.9.
The bad news is that changing the superbock version destroys the data on the raid set.
You must have version 0.9 on your /boot, if its raided as grub won't install on 1.x raid sets.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
PegasusNZ
n00b
Joined: 30 Apr 2011
Posts: 8
|
| Posted: Sat Apr 30, 2011 11:50 pm Post subject: |
|
|
Hi and thanks for the welcome and help
Partitions is type fd and superblock version 0.9
interestingly enough I ran mdadm -E on /dev/md3 and get
| Code: | mdadm -E /dev/md3
mdadm: No md superblock detected on /dev/md3 |
it was built with the following command:
| Code: | | mdadm --create /dev/md3 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb3 |
reformatting or rebuilding is not an issue as it is a new system and there is no data on it
_________________
I wish it would boot |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sun May 01, 2011 12:00 am Post subject: |
|
|
PegasusNZ,
The raid superblock is on the underlying partitions. Look at my example again.
Do you have Raid auto assemble set in your kernel ?
| Code: | $ grep AUTODE /usr/src/linux/.config
CONFIG_MD_AUTODETECT=y |
and are you running that kernel ?
Look at the boot messages. Do you see | Code: | [ 2.678694] md: Autodetecting RAID arrays.
...
[ 2.855866] md: ... autorun DONE. |
where ... is a lot of text showing your raid sets being detected and assembled ?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
PegasusNZ
n00b
Joined: 30 Apr 2011
Posts: 8
|
| Posted: Sun May 01, 2011 1:03 am Post subject: |
|
|
Thanks for your help
I have made a manual kernel then a genkernel I think they both have this
| Code: | livecd etc # grep AUTODE /usr/src/linux/.config
CONFIG_MD_AUTODETECT=y
|
Hmmmm why??
| Code: | md:Autodetecting RAID arrays.
md:Scanned 0 and added 0 devices
md:autorun ...
md: ... autorun DONE.
...
...
...
EXT3-fs (md3): error: unable to read superblock
|
_________________
I wish it would boot |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sun May 01, 2011 11:35 am Post subject: |
|
|
PegasusNZ,
| Code: | md:Autodetecting RAID arrays.
md:Scanned 0 and added 0 devices
md:autorun ...
md: ... autorun DONE. |
shows that your raid sets were not autodetected by the kernel.
What does show ?
It also brings us back to what does mdadm -E show, when you feed it a partition donated to a raid set.
| Code: | | mdadm -E /dev/<part_of_your_root> |
Wild guess ... do you have on your kernel command like ?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
PegasusNZ
n00b
Joined: 30 Apr 2011
Posts: 8
|
| Posted: Sun May 01, 2011 7:59 pm Post subject: |
|
|
here is the fdisk this boot had an extra drive in that was formatted in solaris
| Code: | livecd / # fdisk -l
Disk /dev/sdb: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 * 63 979964 489951 fd Linux raid autodetect
/dev/sdb2 979965 16611209 7815622+ 82 Linux swap / Solaris
/dev/sdb3 16611210 45913769 14651280 fd Linux raid autodetect
/dev/sdb4 45913770 234436544 94261387+ fd Linux raid autodetect
Disk /dev/sdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 63 979964 489951 fd Linux raid autodetect
/dev/sdc2 979965 16611209 7815622+ 82 Linux swap / Solaris
/dev/sdc3 16611210 45913769 14651280 fd Linux raid autodetect
/dev/sdc4 45913770 234436544 94261387+ fd Linux raid autodetect
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Disk /dev/md3: 15.0 GB, 15002828800 bytes
2 heads, 4 sectors/track, 3662800 cylinders, total 29302400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md3 doesn't contain a valid partition table
Disk /dev/md1: 501 MB, 501612544 bytes
2 heads, 4 sectors/track, 122464 cylinders, total 979712 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md4: 96.5 GB, 96522537984 bytes
2 heads, 4 sectors/track, 23565072 cylinders, total 188520582 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md4 doesn't contain a valid partition table
|
mdadm -E show
| Code: | mdadm -E /dev/sdb3
/dev/sdb3:
Magic : a92b4efc
Version : 0.90.00
UUID : 814dfc00:0a98d1cb:cb201669:f728008a (local to host livecd)
Creation Time : Sat Apr 30 13:54:34 2011
Raid Level : raid1
Used Dev Size : 14651200 (13.97 GiB 15.00 GB)
Array Size : 14651200 (13.97 GiB 15.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 3
Update Time : Mon May 2 08:46:28 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 93b447fb - correct
Events : 18
Number Major Minor RaidDevice State
this 0 8 19 0 active sync /dev/sdb3
0 0 8 19 0 active sync /dev/sdb3
1 1 8 35 1 active sync /dev/sdc3
|
No domdraid
Interestingly the Live CD boot gives a mdadm error no raid configured or detected
here is the lspci
| Code: | 00:00.0 Host bridge: Intel Corporation 5400 Chipset Memory Controller Hub (rev 20)
00:01.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 1 (rev 20)
00:03.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 3 (rev 20)
00:05.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 5 (rev 20)
00:07.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 7 (rev 20)
00:09.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 9 (rev 20)
00:0f.0 System peripheral: Intel Corporation 5400 Chipset QuickData Technology Device (rev 20)
00:10.0 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:10.1 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:10.2 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:10.3 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:10.4 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:11.0 Host bridge: Intel Corporation 5400 Chipset CE/SF Registers (rev 20)
00:15.0 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
00:15.1 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
00:16.0 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
00:16.1 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
04:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
04:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
05:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
06:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02)
08:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
08:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
0a:01.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
|
_________________
I wish it would boot |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sun May 01, 2011 8:31 pm Post subject: |
|
|
PegasusNZ,
That all looks good. You have an assortment of drive controllers there
| Code: | 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)
06:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2116 PCI-Express Fusion-MPT |
The liveCD will not have the kernel module for the Fusion-MPT controller. Its on its own menu, so drives on that controller will not be seen by the liveCD. You need
| Code: | │ │ SCSI device support ---> │ │
│ │ <*> Serial ATA and Parallel ATA drivers ---> │ │
│ │ [*] Multiple devices driver support (RAID and LVM) ---> │ │
│ │ < > Generic Target Core Mod (TCM) and ConfigFS Infrastructure ---> │ │
│ │ [ ] Fusion MPT device support ---> |
[*] Fusion MPT device support ---> and an option inside that menu or
<*> LSI MPT Fusion SAS 2.0 Device Driver in the SCSI low-level drivers menu. I'm not sure which.
The liveCD provides neither of those drivers - by extension, nor does genkernel as genkernel is used to build the liveCD.
and post your kernel .config file. Its too big to fit in a post.
| Code: | | wgetpaste /usr/src/linux/.config |
ans post the URL you get back.
You could also check your kernel settings.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
PegasusNZ
n00b
Joined: 30 Apr 2011
Posts: 8
|
| Posted: Sun May 01, 2011 9:38 pm Post subject: |
|
|
Lets hope this worked, had a few connection errors
| Code: |
http://paste.pocoo.org/show/381290/
|
_________________
I wish it would boot |
|
| Back to top |
|
|
PegasusNZ
n00b
Joined: 30 Apr 2011
Posts: 8
|
| Posted: Sun May 01, 2011 9:38 pm Post subject: |
|
|
oopppsss
[url]http://paste.pocoo.org/show/381290/ [/url]
_________________
I wish it would boot |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sun May 01, 2011 11:10 pm Post subject: |
|
|
PegasusNZ,
It worked. I'll look in more detail tomorrow night but I think
| Code: | | # CONFIG_SCSI_MPT2SAS is not set |
is a bad sign.
Thats <*> LSI MPT Fusion SAS 2.0 Device Driver in the SCSI low-level drivers menu.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
PegasusNZ
n00b
Joined: 30 Apr 2011
Posts: 8
|
| Posted: Mon May 02, 2011 12:35 am Post subject: |
|
|
That is strange I see what you mean I have a genkernel setup saved as my.config
I start genkernel load my.config check settings and exit
I assumed that would be the correct procedure!
comparing .config to my.config the settings are wildly different
Cheers
Callum
_________________
I wish it would boot |
|
| Back to top |
|
|
PegasusNZ
n00b
Joined: 30 Apr 2011
Posts: 8
|
| Posted: Mon May 02, 2011 3:00 am Post subject: |
|
|
My error discovered - Ah Genkernel
was not saving as I thought
_________________
I wish it would boot |
|
| Back to top |
|
|
|
Installing Gentoo
