Raid not activated at boot

Bug #407901 reported by Jeroen Benckhuijsen on 2009-08-02
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
dmraid (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: dmraid

1) Description: Ubuntu 9.04
Release: 9.04

2) apt-cache policy dmraid
dmraid:
  Installed: 1.0.0.rc15-6ubuntu2
  Candidate: 1.0.0.rc15-6ubuntu2
  Version table:
 *** 1.0.0.rc15-6ubuntu2 0
        500 http://nl.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status
3) Expected: normal boot up sequence, with activated raid disks. fsck completing normally

4) Actual: Raid disks are not mounted at boot. fsck fails to complete due to disks not mounted. Drop to system maintenance root shell. After a "dmraid -a y ; exit" normal boot-up resumes and the disks are mounted correctly. Reproducible: every time.

Additional info: RAID controller is the NVidia NForce model on an ASUS A8N-SLI Deluxe motherboard.

Danny Wood (danwood76) wrote :

What your physical setup for the RAID?
(RAID0,1,5, etc.)

If it is a RAID5 there is a bug related to a typo of which a patch has been created.

Physical setup is RAID 1

FDisk -l output:

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00046c59

   Device Boot Start End Blocks Id System
/dev/sda1 1 30401 244196001 5 Extended
/dev/sda5 1 9961 80011669+ fd Linux raid autodetect
/dev/sda6 9962 17432 60010776 7 HPFS/NTFS
/dev/sda7 17433 30401 104173461 fd Linux raid autodetect

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00046c59

   Device Boot Start End Blocks Id System
/dev/sdc1 1 30401 244196001 5 Extended
/dev/sdc5 1 9961 80011669+ fd Linux raid autodetect
/dev/sdc6 9962 17432 60010776 7 HPFS/NTFS
/dev/sdc7 17433 30401 104173461 fd Linux raid autodetect

l4nz3r (l4nz3r) wrote :

I have the same problem with raid0, I have configured fstab for mount the /dev/mapper/isw_device and when I boot fcsk fails and I have to put dmraid -a y; exit; for resume the boot

pinzia (pinzia) wrote :

Same problem on intrepid.
I upgrade to jaunty and i have the problem yet.
it's similar of these: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/367553

https://bugs.launchpad.net/debian/+source/dmraid/+bug/315735

sorry for my bad english

alteeno (alteeno-sina) wrote :

I have the same problem from version 8.10 to 9.10 except version 8.04 working good.
I have 4 hdd for raid 1+0 on AMD 690G+SB650.

Tormod Volden (tormodvolden) wrote :

Fox-ino and alteeno, please file new bug reports, using "ubuntu-bug dmraid". It is not sure it is exactly the same problem. alteeno, are you at all using dmraid (fakeraid)?

alteeno (alteeno-sina) wrote :

Yes, I always use dmraid (fakeraid) in ubuntu from version 6.06 to 9.10 on serveral PCs.
But only 8.04 is working perfectly. The version 8.10, 9.04, 9.10 always boot into the busybox, till you typing dmraid -ay and exit.

Rez (toast2soon) wrote :

Anyone make any progress with this issue?

I have the same problem. I've just assembled a new machine from scratch based on an Asus P6TWS Pro motherboard and 9.10 will NOT recognize my Raid1 array on bootup.

I've followed the "Fakeraid howto", and have reinstalled half a dozen times so far. No way will 9.10 see the disks.

My system has 3 1TB SATA drives. One drive is my system drive, and 9.10 is loaded and will boot from that drive.

The other 2 drives form a "hardware" raid1 array via an on board Marvell controller and BIOS settings.

The drives in the raid array have never been touched as individual drives: They were installed clean and the partitioning/formatting was done on the array via gparted.

dmraid will detect the disks, but only when it is manually executed.

The first bootup after a clean install and following the "Fakeraid howto" instructions results in failure to mount and the option to press ESC to enter the maintenance shell. Amy subsequent bootup seems to completely ignore the array. There is no failure message and the system does not see the array until I manually run dmraid.

I need to get past this issue ASAP and get the array on line.

Any suggestions?

Rez (toast2soon) wrote :

Further to the above:

results of simple fdisk command:
fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000c2486

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 117106 940653913+ 83 Linux
/dev/sda2 117107 121601 36106087+ 5 Extended
/dev/sda5 117107 121601 36106056 82 Linux swap / Solaris

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdc doesn't contain a valid partition table

results of fdisk on the array:
fdisk -l /dev/mapper/ddf1_Raid1_SATA

Disk /dev/mapper/ddf1_Raid1_SATA: 1000.1 GB, 1000120999936 bytes
255 heads, 63 sectors/track, 121591 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000781f4

                      Device Boot Start End Blocks Id System
/dev/mapper/ddf1_Raid1_SATA1 1 121591 976679676 83 Linux

Chris Balcum (sherl0k) wrote :

Use kpartx to map the drive to a partition. I ran into this problem myself using ISW. In /dev/mapper there's the RAID array but no partition to mount, after running kpartx it's there.

kpartx -a /dev/mapper/isw_cidjcaibaf_Images

I added this to /etc/rc.local, along with 'dmraid -ay' and 'mount -a' with the RAID array in my /etc/fstab to ensure it mounted.

I created my RAID array with the ISW built into the BIOS of my motherboard, and created the array using gparted, for the record.

Phillip Susi (psusi) wrote :

Jeroen, can you post the output of sudo blkid?

Changed in dmraid (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for dmraid (Ubuntu) because there has been no activity for 60 days.]

Changed in dmraid (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers