mdadm raid1 on one disk problem with boot

Bug #1371985 reported by Kanogin Alexandr
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Installed Ubuntu 14.04 LTS 32bit server from CD.

Install OS on software RAID1 with one hdd disk (degraided raid1).
The system should boot from one disk.
However, the system does not boot in this configuration.

After reboot system this messages are last and boot stopped:
[ 6.531314] md: raid6 personality registered for level 6
[ 6.531382] md: raid5 personality registered for level 5
[ 6.531427] md: raid4 personality registered for level 4
[ 6.535395] md: raid10 personality registered for level 10
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
mount: mounting /dev/disk/by-uuid/d35b085e-1361-4d78-afd0-60dcdc0a2b81 on /root failed: Device or resource busy
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
[ 6.195744] usb 2-1: New USB device found, idVendor=0e0f, idProduct=0003
[ 6.195789] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6.195835] usb 2-1: Product: VMware Virtual USB Mouse
[ 6.195880] usb 2-1: Manufacturer: VMware
[ 6.306922] usb 2-2: new full-speed USB device number 3 using uhci_hcd
[ 6.435625] usb 2-2: New USB device found, idVendor=0e0f, idProduct=0002
[ 6.435671] usb 2-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 6.435716] usb 2-2: Product: VMware Virtual USB Hub
[ 6.436427] hub 2-2:1.0: USB hub found
[ 6.436633] hub 2-2:1.0: 7 ports detected
mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
[ 6.440124] hidraw: raw HID events driver (C) Jiri Kosina
[ 6.443783] usbcore: registered new interface driver usbhid
[ 6.443829] usbhid: USB HID core driver

BusyBox v1.21.1 (Ubuntu 1:1.21.-=1ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

If through boot press "scroll lock" or "Ctrl-S" around the message:
[ 6.195744] usb 2-1: New USB device found, idVendor=0e0f, idProduct=0003
[ 6.195789] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6.195835] usb 2-1: Product: VMware Virtual USB Mouse
[ 6.195880] usb 2-1: Manufacturer: VMware

Then loading passes to login:
Ubuntu 14.04.1 LTS ubuntu tty1
ubuntu login:

But, if change /etc/mdadm/mdadm.conf (/dev/md/0 to /dev/md0 and /dev/md/1 to /dev/md1)

from:
ARRAY /dev/md/0 metadata=1.2 UUID=8f0090f4:8058b740:de4ea3e4:d197046c name=ubuntu:0
ARRAY /dev/md/1 metadata=1.2 UUID=039ff78d:03ed555f:2b050a37:996683f2 name=ubuntu:1

to:
ARRAY /dev/md0 metadata=1.2 UUID=8f0090f4:8058b740:de4ea3e4:d197046c name=ubuntu:0
ARRAY /dev/md1 metadata=1.2 UUID=039ff78d:03ed555f:2b050a37:996683f2 name=ubuntu:1

and run:
update-initramfs -u -k all
then boot loading passes to login:
Ubuntu 14.04.1 LTS ubuntu tty1
ubuntu login:

And after return lines
ARRAY /dev/md/0 metadata=1.2 UUID=8f0090f4:8058b740:de4ea3e4:d197046c name=ubuntu:0
ARRAY /dev/md/1 metadata=1.2 UUID=039ff78d:03ed555f:2b050a37:996683f2 name=ubuntu:1
to config file /etc/mdadm/mdadm.conf, then boot process stop at "(initramfs)".
---
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: i386
CurrentDmesg: [ 21.192659] init: plymouth-upstart-bridge main process (268) killed by TERM signal
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-09-20 (0 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MDadmExamine.dev.sda:
 /dev/sda:
    MBR Magic : aa55
 Partition[0] : 39061504 sectors at 2048 (type fd)
 Partition[1] : 2877440 sectors at 39063552 (type fd)
MachineType: VMware, Inc. VMware Virtual Platform
Package: mdadm 3.2.5-5ubuntu4.1
PackageArchitecture: i386
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=d35b085e-1361-4d78-afd0-60dcdc0a2b81 ro nomdmonddf nomdmonisw
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Tags: trusty
Uname: Linux 3.13.0-35-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

Revision history for this message
Kanogin Alexandr (kanogin) wrote : BootDmesg.txt

apport information

description: updated
tags: added: apport-collected trusty
description: updated
Revision history for this message
Kanogin Alexandr (kanogin) wrote : Dependencies.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : Lspci.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : MDadmExamine.dev.sda1.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : MDadmExamine.dev.sda2.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : ProcEnviron.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : ProcMDstat.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : ProcModules.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : ProcMounts.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : ProcPartitions.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : UdevDb.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : UdevLog.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : initrd.files.txt

apport information

Revision history for this message
Kanogin Alexandr (kanogin) wrote : mdadm.conf.txt

apport information

description: updated
Revision history for this message
soulmate (vveresko) wrote :

The same problem, the one disk in my raid 1 has broken and now it can't boot with the same message :(

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mdadm (Ubuntu):
status: New → Confirmed
Revision history for this message
Stan (swoz) wrote :

I have the same issue with Ubuntu 14.04.1 LTS 64bit.

Following hack solves the issue:
 echo "sleep 60" > /etc/initramfs-tools/scripts/init-premount/delay_for_raid_array_to_build_before_mounting
 chmod a+x /etc/initramfs-tools/scripts/init-premount/delay_for_raid_array_to_build_before_mounting
 update-initramfs -u
(found at http://ubuntuforums.org/showthread.php?t=2241430)

Now it boots, but I'm worried that this is not the proper solution.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.