UBUNTU: modprobe hang on boot, ocz Revo Drive, raid0

markp1989 · Jun 29, 2011

just got my OCZ revo drive in the post today.

fyi: the 50gb revo drive is 2x25gb SSDs + a fake raid controller on a PCIE card.
http://www.play.com/PC/PCs/4-/18616...tml?_$ja=tsid:11518|cat:18616749|prd:18616749

I set up 100mb partition at the start of the first "drive" for /boot , and used the rest of the drive in raid 0.

here is the boot chart, most of the boot time is modprobe, hanging for 10 seconds.
https://dl.dropbox.com/s/e14gr1fu2pvnlv2/MarksPC-natty-20110629-3.png

due to the 10second wait, boot time is actualy longer with the new drive than it was with my old SATA II SSD.

is there anyway I can stop modprobe hanging like that?

Thanks, Mark

Adragontattoo · Jun 29, 2011

which version of mdadm? Ubuntu was running a much older version

markp1989 · Jun 30, 2011

looks like it has version 3.1.4

output from mdadm -V:
mdadm - v3.1.4 - 31st August 2010

according to wiki thats the current version.

since i made the post yesterday, I did a new install. I put the boot partition on the start 320gb hard drive, and used the complete SSD in raid0 for root, but modprobe still hangs, so the bootchart looks the same.

edit: just noticed something strange in the disk manager.

it shows the array as "not partitioned" but it also shows that it has a ext4 partition on it :S

edit again, removed screen shot was way to big. here is a link instead http://dl.dropbox.com/u/4137122/Screenshot.png

edit1:
any mentions of raid and md0 in dmesg, may give people more of an idea of whats going on in my system.

Code:

mark@MarksPC:~$ dmesg | grep raid 
[    3.027691] md: raid0 personality registered for level 0
[    3.030791] md: raid1 personality registered for level 1
[    3.192801] raid6: int64x1   2929 MB/s
[    3.362361] raid6: int64x2   3848 MB/s
[    3.531910] raid6: int64x4   2632 MB/s
[    3.701477] raid6: int64x8   2636 MB/s
[    3.871039] raid6: sse2x1    8413 MB/s
[    4.040628] raid6: sse2x2    9908 MB/s
[    4.210208] raid6: sse2x4   11017 MB/s
[    4.210209] raid6: using algorithm sse2x4 (11017 MB/s)
[   11.735341] md: raid6 personality registered for level 6
[   11.735342] md: raid5 personality registered for level 5
[   11.735343] md: raid4 personality registered for level 4
[   11.740463] md: raid10 personality registered for level 10
[   11.759298] md/raid0:md0: looking at sdc1
[   11.759302] md/raid0:md0:   comparing sdc1(48852992) with sdc1(48852992)
[   11.759307] md/raid0:md0:   END
[   11.759309] md/raid0:md0:   ==> UNIQUE
[   11.759311] md/raid0:md0: 1 zones
[   11.759314] md/raid0:md0: looking at sdb1
[   11.759317] md/raid0:md0:   comparing sdb1(48852992) with sdc1(48852992)
[   11.759321] md/raid0:md0:   EQUAL
[   11.759324] md/raid0:md0: FINAL 1 zones
[   11.759328] md/raid0:md0: done.
[   11.759331] md/raid0:md0: md_size is 97705984 sectors.
mark@MarksPC:~$

Code:

mark@MarksPC:~$ dmesg | grep md0
[   11.759298] md/raid0:md0: looking at sdc1
[   11.759302] md/raid0:md0:   comparing sdc1(48852992) with sdc1(48852992)
[   11.759307] md/raid0:md0:   END
[   11.759309] md/raid0:md0:   ==> UNIQUE
[   11.759311] md/raid0:md0: 1 zones
[   11.759314] md/raid0:md0: looking at sdb1
[   11.759317] md/raid0:md0:   comparing sdb1(48852992) with sdc1(48852992)
[   11.759321] md/raid0:md0:   EQUAL
[   11.759324] md/raid0:md0: FINAL 1 zones
[   11.759328] md/raid0:md0: done.
[   11.759331] md/raid0:md0: md_size is 97705984 sectors.
[   11.759333] ******* md0 configuration *********
[   11.759355] md0: detected capacity change from 0 to 50025463808
[   11.760848]  md0: unknown partition table
[   11.797582] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[   12.915845] EXT4-fs (md0): re-mounted. Opts: errors=remount-ro
[   13.637898] EXT4-fs (md0): re-mounted. Opts: errors=remount-ro,commit=0
[   15.210517] EXT4-fs (md0): re-mounted. Opts: errors=remount-ro,commit=0
mark@MarksPC:~$

here is the matching bootchart for the dmesg above http://dl.dropbox.com/u/4137122/MarksPC-natty-20110630-1.png

Adragontattoo · Jun 30, 2011

1st code SS shows it is making sure the two drives are in sync before boot

Id suggest wiping the array out, removing the superblocks and fully recreating the array from square 1. Make sure it is fully synchronized before doing ANY data moves if possible.

I had to recreate and resync the 13tb array twice when I started beating on it ahead of it being complet...

markp1989 · Jul 1, 2011

Thanks for replying to my thread

Im away from my desktop right now, I will try to start again and report back some time later today.

UBUNTU: modprobe hang on boot, ocz Revo Drive, raid0

markp1989

Member

Adragontattoo

Trailer Chasing Senior

markp1989

Member

Adragontattoo

Trailer Chasing Senior

markp1989

Member

Similar threads