system startup hangs

system startup hangs

[Richard B. Pyne]

Please forgive me if I ask stupid questions, I am fairly new to linux 
raid and most of the documentation I can find is severely outdated 
and/or written for someone who already understands linux raid.

I have successfully built a set raid 6 array with 4 drives and have 
copied my system partitions onto the raid drives. I then reboot with 
root=/dev/md0.

Everything looks like it is working right up through:

md/raid:md0 raid level 6 active with 4 out of 4 devices, algorithm 2
md0: detected capacity change from 0 to 1000131788
md: autorun DONE.
md0: unknown partition table
EXT3-fs (md0): error: couldn't mount because of unsupported optional 
features
EXT2-fs (md0): error: couldn't mount because of unsupported optional 
features
EXT4-fs (md0): mounted filesystem with ordered data mode.  Opts: (null)
VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
freeing unused kernel memory: 472k freed


at which point it just hangs. No more disk access, no more messages.


The system has 5 WD Caviar Black 500GB drives. I did the linux install 
on the first drive and built the other 4 drives into the raid system, 
planning to move everything (except the /boot partition) on to the raid 
array and then repartition everything except the /boot partition on the 
first drive and add it to the raid.

I currently have md0 for / md1 for /home md2 for /usr md3 for /var and 
md4 on which I plan on running lvm to allocate to other system needs.

Any advice, insights and/or direction will be greatly appreciated.

Re: system startup hangs

[NeilBrown]

[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]

On Wed, 07 Dec 2011 15:38:05 -0700 "Richard B. Pyne" <rpyne@kinfolk.org>
wrote:

> Please forgive me if I ask stupid questions, I am fairly new to linux 
> raid and most of the documentation I can find is severely outdated 
> and/or written for someone who already understands linux raid.
> 
> I have successfully built a set raid 6 array with 4 drives and have 
> copied my system partitions onto the raid drives. I then reboot with 
> root=/dev/md0.
> 
> Everything looks like it is working right up through:
> 
> md/raid:md0 raid level 6 active with 4 out of 4 devices, algorithm 2
> md0: detected capacity change from 0 to 1000131788
> md: autorun DONE.
> md0: unknown partition table
> EXT3-fs (md0): error: couldn't mount because of unsupported optional 
> features
> EXT2-fs (md0): error: couldn't mount because of unsupported optional 
> features
> EXT4-fs (md0): mounted filesystem with ordered data mode.  Opts: (null)
> VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
> freeing unused kernel memory: 472k freed

It looks like the array got setup fine, the filesystem on it was mounted, and
then .... nothing.

I think at this point it should be running /sbin/init.

It doesn't seem like a RAID problem exactly.  Maybe something when wrong when
you copying the system partition into the RAID, but that is just a guess.

At this point we probably need to know at least what distro you are using.
There is probably some way to turn on tracing in the initrd and the boot
sequence, but it is different for different distros.

NeilBrown



> 
> 
> at which point it just hangs. No more disk access, no more messages.
> 
> 
> The system has 5 WD Caviar Black 500GB drives. I did the linux install 
> on the first drive and built the other 4 drives into the raid system, 
> planning to move everything (except the /boot partition) on to the raid 
> array and then repartition everything except the /boot partition on the 
> first drive and add it to the raid.
> 
> I currently have md0 for / md1 for /home md2 for /usr md3 for /var and 
> md4 on which I plan on running lvm to allocate to other system needs.
> 
> Any advice, insights and/or direction will be greatly appreciated.
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

Re: system startup hangs

[Mathias Burén]

On 7 December 2011 22:38, Richard B. Pyne <rpyne@kinfolk.org> wrote:
> Please forgive me if I ask stupid questions, I am fairly new to linux raid
> and most of the documentation I can find is severely outdated and/or written
> for someone who already understands linux raid.
>
> I have successfully built a set raid 6 array with 4 drives and have copied
> my system partitions onto the raid drives. I then reboot with root=/dev/md0.
>
> Everything looks like it is working right up through:
>
> md/raid:md0 raid level 6 active with 4 out of 4 devices, algorithm 2
> md0: detected capacity change from 0 to 1000131788
> md: autorun DONE.
> md0: unknown partition table
> EXT3-fs (md0): error: couldn't mount because of unsupported optional
> features
> EXT2-fs (md0): error: couldn't mount because of unsupported optional
> features
> EXT4-fs (md0): mounted filesystem with ordered data mode.  Opts: (null)
> VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
> freeing unused kernel memory: 472k freed
>
>
> at which point it just hangs. No more disk access, no more messages.
>
>
> The system has 5 WD Caviar Black 500GB drives. I did the linux install on
> the first drive and built the other 4 drives into the raid system, planning
> to move everything (except the /boot partition) on to the raid array and
> then repartition everything except the /boot partition on the first drive
> and add it to the raid.
>
> I currently have md0 for / md1 for /home md2 for /usr md3 for /var and md4
> on which I plan on running lvm to allocate to other system needs.
>
> Any advice, insights and/or direction will be greatly appreciated.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

So you created 1 RAID6 volume. That is now "1 RAID drive", i.e. md0.

Did you create partitions on md0? Or did you make it a physical volume
(PV) with LVM?
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: system startup hangs

[Richard B. Pyne]

On 12/7/2011 4:01 PM, Mathias Burén wrote:
> On 7 December 2011 22:38, Richard B. Pyne<rpyne@kinfolk.org>  wrote:
>> Please forgive me if I ask stupid questions, I am fairly new to linux raid
>> and most of the documentation I can find is severely outdated and/or written
>> for someone who already understands linux raid.
>>
>> I have successfully built a set raid 6 array with 4 drives and have copied
>> my system partitions onto the raid drives. I then reboot with root=/dev/md0.
>>
>> Everything looks like it is working right up through:
>>
>> md/raid:md0 raid level 6 active with 4 out of 4 devices, algorithm 2
>> md0: detected capacity change from 0 to 1000131788
>> md: autorun DONE.
>> md0: unknown partition table
>> EXT3-fs (md0): error: couldn't mount because of unsupported optional
>> features
>> EXT2-fs (md0): error: couldn't mount because of unsupported optional
>> features
>> EXT4-fs (md0): mounted filesystem with ordered data mode.  Opts: (null)
>> VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
>> freeing unused kernel memory: 472k freed
>>
>>
>> at which point it just hangs. No more disk access, no more messages.
>>
>>
>> The system has 5 WD Caviar Black 500GB drives. I did the linux install on
>> the first drive and built the other 4 drives into the raid system, planning
>> to move everything (except the /boot partition) on to the raid array and
>> then repartition everything except the /boot partition on the first drive
>> and add it to the raid.
>>
>> I currently have md0 for / md1 for /home md2 for /usr md3 for /var and md4
>> on which I plan on running lvm to allocate to other system needs.
>>
>> Any advice, insights and/or direction will be greatly appreciated.
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> So you created 1 RAID6 volume. That is now "1 RAID drive", i.e. md0.
>
> Did you create partitions on md0? Or did you make it a physical volume
> (PV) with LVM?

I guess I should have been a bit more clear. Each drive is partitioned 
with 7 partitions. 1,2,3,5,6,7&8. partition 1 is just a small partition 
to match the original boot drive /boot partition. Partition 2 is swap 
space. partition 3 has been made into md0 and formatted with an ext4 for 
/, same for partitions 5 as md1 for /home, partition 6 as md2 for /usr 
and partition 7 as md3 for /var. Once I have everything up and working, 
then I will put lvm on md4 made from partition 8 and use it for other 
server needs.


--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: system startup hangs

[Richard B. Pyne]

On 12/7/2011 4:00 PM, NeilBrown wrote:
> On Wed, 07 Dec 2011 15:38:05 -0700 "Richard B. Pyne"<rpyne@kinfolk.org>
> wrote:
>
>> Please forgive me if I ask stupid questions, I am fairly new to linux
>> raid and most of the documentation I can find is severely outdated
>> and/or written for someone who already understands linux raid.
>>
>> I have successfully built a set raid 6 array with 4 drives and have
>> copied my system partitions onto the raid drives. I then reboot with
>> root=/dev/md0.
>>
>> Everything looks like it is working right up through:
>>
>> md/raid:md0 raid level 6 active with 4 out of 4 devices, algorithm 2
>> md0: detected capacity change from 0 to 1000131788
>> md: autorun DONE.
>> md0: unknown partition table
>> EXT3-fs (md0): error: couldn't mount because of unsupported optional
>> features
>> EXT2-fs (md0): error: couldn't mount because of unsupported optional
>> features
>> EXT4-fs (md0): mounted filesystem with ordered data mode.  Opts: (null)
>> VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
>> freeing unused kernel memory: 472k freed
> It looks like the array got setup fine, the filesystem on it was mounted, and
> then .... nothing.
>
> I think at this point it should be running /sbin/init.
>
> It doesn't seem like a RAID problem exactly.  Maybe something when wrong when
> you copying the system partition into the RAID, but that is just a guess.
>
> At this point we probably need to know at least what distro you are using.
> There is probably some way to turn on tracing in the initrd and the boot
> sequence, but it is different for different distros.
>
> NeilBrown
>
I am using lunar linux. ( http://lunar-linux.org ). The kernel is 3.1.4 
x86_64 confiugred with raid autodetect and the raid sets were built with 
-e 0.90.

--Richard

Re: system startup hangs

[Robin Hill]

[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]

On Wed Dec 07, 2011 at 03:38:05PM -0700, Richard B. Pyne wrote:

> Please forgive me if I ask stupid questions, I am fairly new to linux 
> raid and most of the documentation I can find is severely outdated 
> and/or written for someone who already understands linux raid.
> 
> I have successfully built a set raid 6 array with 4 drives and have 
> copied my system partitions onto the raid drives. I then reboot with 
> root=/dev/md0.
> 
> Everything looks like it is working right up through:
> 
> md/raid:md0 raid level 6 active with 4 out of 4 devices, algorithm 2
> md0: detected capacity change from 0 to 1000131788
> md: autorun DONE.
> md0: unknown partition table
> EXT3-fs (md0): error: couldn't mount because of unsupported optional 
> features
> EXT2-fs (md0): error: couldn't mount because of unsupported optional 
> features
> EXT4-fs (md0): mounted filesystem with ordered data mode.  Opts: (null)
> VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
> freeing unused kernel memory: 472k freed
> 
> 
> at which point it just hangs. No more disk access, no more messages.
> 
> 
> The system has 5 WD Caviar Black 500GB drives. I did the linux install 
> on the first drive and built the other 4 drives into the raid system, 
> planning to move everything (except the /boot partition) on to the raid 
> array and then repartition everything except the /boot partition on the 
> first drive and add it to the raid.
> 
> I currently have md0 for / md1 for /home md2 for /usr md3 for /var and 
> md4 on which I plan on running lvm to allocate to other system needs.
> 
> Any advice, insights and/or direction will be greatly appreciated.
> 
> 
I've been bitten by this one myself recently. I suspect you've failed to
copy over the required underlying /dev entries. You need at least
/dev/console and /dev/null on the rootfs - at this stage the tmpfs
hasn't been mounted on /dev and udev hasn't created all the dev nodes.

Cheers,
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: system startup hangs

[Richard B. Pyne]

On 12/8/2011 5:21 AM, Robin Hill wrote:
> On Wed Dec 07, 2011 at 03:38:05PM -0700, Richard B. Pyne wrote:
>> EXT4-fs (md0): mounted filesystem with ordered data mode.  Opts: (null)
>> VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
>> freeing unused kernel memory: 472k freed
>>
>> at which point it just hangs. No more disk access, no more messages.
>>
>> I currently have md0 for / md1 for /home md2 for /usr md3 for /var and
>> md4 on which I plan on running lvm to allocate to other system needs.
>>
>> Any advice, insights and/or direction will be greatly appreciated.
>>
> I've been bitten by this one myself recently. I suspect you've failed to
> copy over the required underlying /dev entries. You need at least
> /dev/console and /dev/null on the rootfs - at this stage the tmpfs
> hasn't been mounted on /dev and udev hasn't created all the dev nodes.
>
> Cheers,
>      Robin
That was the problem, Thank you very much!

Now lilo is telling me that I must have my boot on a RAID1 device even 
though I have it on a non-raid drive and partition.

--Richard