Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
unable to install grub on secondary raid1 boot.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5369

PostPosted: Tue Jul 31, 2012 6:22 pm    Post subject: unable to install grub on secondary raid1 boot. Reply with quote

Hello,

I've upgraded my hds and decided to do some changes in my layout, on of them was to put boot and / on raid 1.
I've followed this tutorial: http://en.gentoo-wiki.com:8088/wiki/RAID/Software
installing on sda worked but on sdb I get this:
Code:
grub> device (hd0) /dev/sdb

grub> root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/e2fs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... failed (this is not fatal)
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
 Running "install /boot/grub/stage1 (hd0) /boot/grub/stage2 p /boot/grub/menu.lst "...
 failed

Error 16: Inconsistent filesystem structure

how can I fix this?
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
ali3nx
l33t
l33t


Joined: 21 Sep 2003
Posts: 612
Location: Winnipeg, Canada

PostPosted: Tue Jul 31, 2012 6:39 pm    Post subject: Reply with quote

Just curious but are both hard drives identical and are you sure they both have identical partition layouts? I'm not 100% certain this might be the cause of it but the error you have there seems to indicate that might be a possibility.

I've used that guide myself for reference over the years and one step i try never to miss is partition layout duplication with sfdisk so the partiton table boundaries are identical.

Code:
sfdisk -d /dev/sda | sfdisk /dev/sdb

_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5369

PostPosted: Tue Jul 31, 2012 6:43 pm    Post subject: Reply with quote

ali3nx wrote:
Just curious but are both hard drives identical and are you sure they both have identical partition layouts? I'm not 100% certain this might be the cause of it but the error you have there seems to indicate that might be a possibility.


I'm using 4 drives, sd[ab] are identical, sd[cd] are the newer version of sd[ab].

here is the entire layout:
Code:
NCC-5001-D dagg # parted -l
Model: ATA SAMSUNG HD103SJ (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  211MB   210MB   ext3               boot
 3      211MB   3224MB  3014MB  reiserfs           raid
 2      3224MB  1000GB  997GB                      raid


Model: ATA SAMSUNG HD103SJ (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  211MB   210MB   ext3               boot
 3      211MB   3224MB  3014MB  reiserfs           raid
 2      3224MB  1000GB  997GB                      raid


Model: ATA ST1000DM005 HD10 (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  211MB   210MB   ext3               boot
 3      211MB   3224MB  3014MB  reiserfs           raid
 2      3224MB  1000GB  997GB                      raid


Model: ATA ST1000DM005 HD10 (scsi)
Disk /dev/sdd: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  211MB   210MB   ext3               boot
 3      211MB   3224MB  3014MB  reiserfs           raid
 2      3224MB  1000GB  997GB                      raid


Model: ATA WDC WD3200AAKS-0 (scsi)
Disk /dev/sde: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  320GB  320GB


Model: WDC WD50 00AAKS-00A7B2 (scsi)
Disk /dev/sdf: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  500GB  500GB  primary  ext3


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/extra-share: 118GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number  Start  End    Size   File system  Flags
 1      0.00B  118GB  118GB  fat32


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/extra-swap: 16.8GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number  Start  End     Size    File system     Flags
 1      0.00B  16.8GB  16.8GB  linux-swap(v1)


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/extra-dev_and_utils: 185GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number  Start  End    Size   File system  Flags
 1      0.00B  185GB  185GB  reiserfs


Model: Linux Software RAID Array (md)
Disk /dev/md0: 210MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number  Start  End    Size   File system  Flags
 1      0.00B  210MB  210MB  ext3


Model: Linux Software RAID Array (md)
Disk /dev/md1: 2991GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  21.5GB  21.5GB  reiserfs
 2      21.5GB  22.6GB  1074MB  ext2
 3      22.6GB  44.0GB  21.5GB  reiserfs
 4      44.0GB  70.9GB  26.8GB  reiserfs
 5      70.9GB  125GB   53.7GB  reiserfs
 6      125GB   1224GB  1100GB  reiserfs
 7      1224GB  2991GB  1767GB  xfs


Model: Linux Software RAID Array (md)
Disk /dev/md2: 3014MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number  Start  End     Size    File system  Flags
 1      0.00B  3014MB  3014MB  reiserfs

_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein


Last edited by DaggyStyle on Tue Jul 31, 2012 6:58 pm; edited 1 time in total
Back to top
View user's profile Send private message
ali3nx
l33t
l33t


Joined: 21 Sep 2003
Posts: 612
Location: Winnipeg, Canada

PostPosted: Tue Jul 31, 2012 6:57 pm    Post subject: Reply with quote

IIRC the last time i setup mdadm raid I just used the standard commands to install a grub mbr bootloader on each physical drive in case the raid ever failed. since it's raid 1 /boot it's mirrored anyway.

Code:
root (hd0,0)
setup (hd0)

root (hd1,0)
setup (hd1)

ect


It's been a few years since i've been willing to attempt using mdadm because of several bad experiences with buggy hardware so i've been more willing to just rely on LSI megaraid SAS hardware raid controllers. Some sata controllers just do not play well with mdadm whatsoever. The last asus server motherboard I used mdadm with (certainly not faulting mdadm for this) had a love for desyncing twice a week. Hopefully that's not the case here.
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!


Last edited by ali3nx on Tue Jul 31, 2012 7:43 pm; edited 2 times in total
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5369

PostPosted: Tue Jul 31, 2012 7:10 pm    Post subject: Reply with quote

ali3nx wrote:
IIRC the last time i setup mdadm raid I just used the standard commands to install a grub mbr bootloader on each physical drive in case the raid ever failed. since it's raid 1 /boot it's mirrored anyway.

Code:
root (hd0,0)
setup (hd0)

root (hd1,0)
setup (hd1)

ect


It's been a few years since i've been willing to attempt using mdadm because of several bad experiences with buggy hardware so i've been more willing to just rely on LSI megaraid SAS hardware raid controllers. Some sata controllers just do not play well with mdadm whatsoever. The last asus server motherboard I used mdadm with (certainly not faulting mdadm for this) had a love for desyncing twice a week. Hopefully that's not the case here.

well, before I had raid1 and 0 on this board without any problems, but they were not boot.
but, if I run grub, install n sda and them sdb it passes on sda but fails on sdb. the if I restart grub again and try it vice versa (sdb first, then sda it works on sdb but not sda).

afaik, linux sw is quite stable, I don't have the money to get a hw raid and the one on my board sw and I was told it is crap.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
ali3nx
l33t
l33t


Joined: 21 Sep 2003
Posts: 612
Location: Winnipeg, Canada

PostPosted: Tue Jul 31, 2012 7:17 pm    Post subject: Reply with quote

Which chipset and sata controller do you have? Maybe you could paste up some lspci details? I still have that server running I had so many problems with. It may be a longshot but let's compare notes.

I may have disabled the onboard raid controller on this server in the bios long ago because it was causing all kinds of grief. I've been using an adaptec hardware controller for several years which earned it 365 day uptime :)

It dates back to the era when sata/pata dual mode controllers were first being introduced. The Intel ICH7 chipset had a terrible pata controller that was nothing but a nuisance.

Code:
asgard ~ # lspci
00:00.0 Host bridge: Intel Corporation 3200/3210 Chipset DRAM Controller (rev 01)
00:01.0 PCI bridge: Intel Corporation 3200/3210 Chipset Host-Primary PCI Express Bridge (rev 01)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 01)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 01)
00:1c.4 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 5 (rev 01)
00:1c.5 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 6 (rev 01)
00:1d.0 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
00:1d.7 USB controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA Controller [AHCI mode] (rev 01)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
01:03.0 VGA compatible controller: XGI Technology Inc. (eXtreme Graphics Innovation) Z7/Z9 (XG20 core)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
06:00.0 PCI bridge: Intel Corporation 80333 Segment-A PCI Express-to-PCI Express Bridge
06:00.2 PCI bridge: Intel Corporation 80333 Segment-B PCI Express-to-PCI Express Bridge
08:0e.0 RAID bus controller: Adaptec AAC-RAID


If your onboard raid is truly "crap" there may be other problems with the controller that could contribute to further grief with mdadm.
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5369

PostPosted: Tue Jul 31, 2012 7:26 pm    Post subject: Reply with quote

here:
Code:
dagg@NCC-5001-D ~ $ /usr/sbin/lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5430 Series]
01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Cedar HDMI Audio [Radeon HD 5400/6300 Series]
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
04:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 10)
06:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630 [Radeon HD 3600 Series]
06:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI RV635 HDMI Audio [Radeon HD 3600 Series]

when I've decided to go raid, I've consulted with the IT guy in our company, he said that the o\b raid are sw which are worst than the one in the kernel and I'd rather go with the kernel one as it is more maintained.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
ali3nx
l33t
l33t


Joined: 21 Sep 2003
Posts: 612
Location: Winnipeg, Canada

PostPosted: Tue Jul 31, 2012 7:40 pm    Post subject: Reply with quote

That's definitely not an ICH7. Nice server btw 8)

The only other thing i can think of is that two of the hard drives you have actually do have larger sector counts. Assuming you used sfdisk in your mdadm raid setup process if the first drive you used to setup the sfdisk partition mirror has a larger sector count than the other drives you mirrored to you may have a partition table that's out of bounds.

You can check how many sectors are available in each drive with fdisk -l.

mdadm may be well maintained and work well but it has high requirements for getting all your ducks in a row for it to work extremely well. Often the one thing you miss will be the item that comes back to kick you in the ass.

In my experience two of the larger risks of using mdadm is hard drives with different firmware or dissimilar hard drives.
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!


Last edited by ali3nx on Tue Jul 31, 2012 7:54 pm; edited 1 time in total
Back to top
View user's profile Send private message
ali3nx
l33t
l33t


Joined: 21 Sep 2003
Posts: 612
Location: Winnipeg, Canada

PostPosted: Tue Jul 31, 2012 7:42 pm    Post subject: Reply with quote

DaggyStyle wrote:
when I've decided to go raid, I've consulted with the IT guy in our company, he said that the o\b raid are sw which are worst than the one in the kernel and I'd rather go with the kernel one as it is more maintained.


For $400 to $600 you could pickup an LSI 9260-8i on ebay possibly with the Battery backup unit. Highly recommend it if you continue to have problems with mdadm. I'm running 20TB on two of them in my home environment and they've been absolutely flawless.
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5369

PostPosted: Tue Jul 31, 2012 8:33 pm    Post subject: Reply with quote

ali3nx wrote:
That's definitely not an ICH7. Nice server btw 8)

The only other thing i can think of is that two of the hard drives you have actually do have larger sector counts. Assuming you used sfdisk in your mdadm raid setup process if the first drive you used to setup the sfdisk partition mirror has a larger sector count than the other drives you mirrored to you may have a partition table that's out of bounds.

You can check how many sectors are available in each drive with fdisk -l.

mdadm may be well maintained and work well but it has high requirements for getting all your ducks in a row for it to work extremely well. Often the one thing you miss will be the item that comes back to kick you in the ass.

In my experience two of the larger risks of using mdadm is hard drives with different firmware or dissimilar hard drives.


as I had problems getting the system up, it was impossible to copy the partition mirror without loosing my raid 5.
fdisk won't work as the partition table is gpt, can you run qfile sfdisk and post the package it belongs there as I wasn't able to find it.

as mentioned before the two first drives are identical, the two last are identical but each two might be a bit different as the first two are samsung f3 and the last two are seagate - samsung f3.

my server is a simple i7-2600 desktop, I just make sure I buy good hardware.

ali3nx wrote:
DaggyStyle wrote:
when I've decided to go raid, I've consulted with the IT guy in our company, he said that the o\b raid are sw which are worst than the one in the kernel and I'd rather go with the kernel one as it is more maintained.


For $400 to $600 you could pickup an LSI 9260-8i on ebay possibly with the Battery backup unit. Highly recommend it if you continue to have problems with mdadm. I'm running 20TB on two of them in my home environment and they've been absolutely flawless.

for that price I can get a new server where I live.

my needs are not that big, I have 4.32Tb which spread over two raid1, one raid 5 and lvm setup.
I'm not sure that my issue is with mdadm, it is more like grub or the partitions.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
ali3nx
l33t
l33t


Joined: 21 Sep 2003
Posts: 612
Location: Winnipeg, Canada

PostPosted: Tue Jul 31, 2012 8:58 pm    Post subject: Reply with quote

DaggyStyle wrote:

as I had problems getting the system up, it was impossible to copy the partition mirror without loosing my raid 5.
fdisk won't work as the partition table is gpt, can you run qfile sfdisk and post the package it belongs there as I wasn't able to find it.


Any time i've ever tried to setup an mdadm raid partition layout it's been using drives that have been completely zeroed out with dd if=/dev/zero of=/dev/sdX

Did you remove any existing partitions on the drives and make new ones to mirror? If you did do that it may be causing you some grief.

If you can make a stage4 tarball backup of your os install and backup your data and recreate your entire partition layout that may solve your issues.

I am aware of the issues with GPT not being supported by fdisk but parted doesn't display the full sector count in the physical drive details which could be valuable information for your endeavors of creating a mdadm partition layout that's not out of bounds or at all dissimilar.

Code:
illusion ~ # fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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: 0x59e5813a

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63      224909      112423+  83  Linux
/dev/sda2          224910     4433939     2104515   82  Linux swap / Solaris
/dev/sda3         4433940   625137344   310351702+  83  Linux



DaggyStyle wrote:

my needs are not that big, I have 4.32Tb which spread over two raid1, one raid 5 and lvm setup.
I'm not sure that my issue is with mdadm, it is more like grub or the partitions.


Hopefully you do get it working and yes that's most likely the situation. identical partition tables are another direct prerequisite for mdadm to work reliably.
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5369

PostPosted: Tue Jul 31, 2012 9:20 pm    Post subject: Reply with quote

ali3nx wrote:
DaggyStyle wrote:

as I had problems getting the system up, it was impossible to copy the partition mirror without loosing my raid 5.
fdisk won't work as the partition table is gpt, can you run qfile sfdisk and post the package it belongs there as I wasn't able to find it.


Any time i've ever tried to setup an mdadm raid partition layout it's been using drives that have been completely zeroed out with dd if=/dev/zero of=/dev/sdX

Did you remove any existing partitions on the drives and make new ones to mirror? If you did do that it may be causing you some grief.

If you can make a stage4 tarball backup of your os install and backup your data and recreate your entire partition layout that may solve your issues.

I am aware of the issues with GPT not being supported by fdisk but parted doesn't display the full sector count in the physical drive details which could be valuable information for your endeavors of creating a mdadm partition layout that's not out of bounds or at all dissimilar.

Code:
illusion ~ # fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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: 0x59e5813a

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63      224909      112423+  83  Linux
/dev/sda2          224910     4433939     2104515   82  Linux swap / Solaris
/dev/sda3         4433940   625137344   310351702+  83  Linux



DaggyStyle wrote:

my needs are not that big, I have 4.32Tb which spread over two raid1, one raid 5 and lvm setup.
I'm not sure that my issue is with mdadm, it is more like grub or the partitions.


Hopefully you do get it working and yes that's most likely the situation. identical partition tables are another direct prerequisite for mdadm to work reliably.


here:
Code:
NCC-5001-D dagg # fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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  1953525167   976762583+  ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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               1  1953525167   976762583+  ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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               1  1953525167   976762583+  ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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/sdd1               1  1953525167   976762583+  ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sde: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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/sde1               1   625142447   312571223+  ee  GPT

Disk /dev/md0: 209 MB, 209649664 bytes
2 heads, 4 sectors/track, 51184 cylinders, total 409472 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 /dev/md2: 3013 MB, 3013541888 bytes
2 heads, 4 sectors/track, 735728 cylinders, total 5885824 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


WARNING: GPT (GUID Partition Table) detected on '/dev/md1'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/md1: 2990.9 GB, 2990935375872 bytes
255 heads, 63 sectors/track, 363627 cylinders, total 5841670656 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 393216 bytes
Disk identifier: 0x00000000

    Device Boot      Start         End      Blocks   Id  System
/dev/md1p1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/mapper/extra-swap: 16.8 GB, 16814964736 bytes
255 heads, 63 sectors/track, 2044 cylinders, total 32841728 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 /dev/mapper/extra-share: 118.1 GB, 118111600640 bytes
255 heads, 63 sectors/track, 14359 cylinders, total 230686720 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

Disk /dev/mapper/extra-dev_and_utils: 185.1 GB, 185140772864 bytes
255 heads, 63 sectors/track, 22508 cylinders, total 361603072 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

well I guess I can take out one drive, partition it as whole, copy the system's content to it (I'm still below the 1TB of data overall), blank the other 3 drives, create the right partition table on one of them, copy it to the other two, create the arrays with one drive missing, set everything up, copy back the data, blank the remaining one, create the partition table on it (save the previous on file), add it back to the arrays, rsync and reboot.
my for this I need sfdisk and time. both I don't have now...

also the above is las resort, I'd rather try to fix it than tear the thing down and rebuild it.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5369

PostPosted: Wed Aug 01, 2012 4:52 pm    Post subject: Reply with quote

here is the output of sgdisk -p on each device:
Code:

Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9F2B5F40-ED12-4636-B7AD-787FD6D9C2AA
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3437 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          411647   200.0 MiB   EF00 
   2         6297600      1953523711   928.5 GiB   FD00 
   3          411648         6297599   2.8 GiB     FD00 

Disk /dev/sdb: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 39281290-3742-4CE8-AA51-DE5B785516BF
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3437 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          411647   200.0 MiB   EF00 
   2         6297600      1953523711   928.5 GiB   FD00 
   3          411648         6297599   2.8 GiB     FD00 

Disk /dev/sdc: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 5CA75A53-67C6-4AF4-9E54-08381DF35228
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3437 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          411647   200.0 MiB   EF00 
   2         6297600      1953523711   928.5 GiB   FD00 
   3          411648         6297599   2.8 GiB     FD00 

Disk /dev/sdd: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): BECCEF54-6FFF-4339-9DBE-8B89A499A73C
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3437 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          411647   200.0 MiB   EF00 
   2         6297600      1953523711   928.5 GiB   FD00 
   3          411648         6297599   2.8 GiB     FD00 

Disk /dev/sde: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 956AD053-ACBD-4434-930B-920130E1428B
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625142414
Partitions will be aligned on 2048-sector boundaries
Total free space is 2669 sectors (1.3 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048       625141759   298.1 GiB   0700

unless I'm missing something, the partitions are the same.
what are the odds that this is because I've created the partitions on each one by hand?
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
ali3nx
l33t
l33t


Joined: 21 Sep 2003
Posts: 612
Location: Winnipeg, Canada

PostPosted: Wed Aug 01, 2012 7:07 pm    Post subject: Reply with quote

It does appear that you've done all the prerequisite setup correctly and you dont have any mismatched partition boundaries that we can see at least. I did find some further reference for you that may help. Definitely not time wasted with a software raid setup like this.

https://forums.gentoo.org/viewtopic-t-866323-start-0.html

Quote:
16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal
error caused by the sanity checks of the filesystem structure on
disk not matching what it expects. This is usually caused by a
corrupt filesystem or bugs in the code handling it in GRUB.


I have to admit that having an inconsistent software raid before you've even finished setting it up wouldn't make me feel warm and fuzzy about it if that were mine 8O
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5369

PostPosted: Wed Aug 01, 2012 7:28 pm    Post subject: Reply with quote

ali3nx wrote:
It does appear that you've done all the prerequisite setup correctly and you dont have any mismatched partition boundaries that we can see at least. I did find some further reference for you that may help. Definitely not time wasted with a software raid setup like this.

https://forums.gentoo.org/viewtopic-t-866323-start-0.html

Quote:
16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal
error caused by the sanity checks of the filesystem structure on
disk not matching what it expects. This is usually caused by a
corrupt filesystem or bugs in the code handling it in GRUB.


I have to admit that having an inconsistent software raid before you've even finished setting it up wouldn't make me feel warm and fuzzy about it if that were mine 8O


thats only /boot, /root and the rest are working ok
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum