Ubuntu

install fails missing obsolete /dev/MAKEDEV

Reported by Enry W on 2009-04-29
186
This bug affects 30 people
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Undecided
Unassigned
Jaunty
Undecided
Unassigned
Lucid
High
Unassigned
Maverick
High
Unassigned

Bug Description

Binary package hint: mdadm

I don't use arrays of disks, but Synaptic wants mdadm to be installed anyway when installing mondo recovery suite.
System: Ubuntu 9.04 installed on a USB stick.

From Install log:

Setting up mdadm (2.6.7.1-1ubuntu8)
Generating array device nodes...

/var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV not found
failed

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script killed by signal (Interrupt)
MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda.
MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda1.
MDadmExamine.dev.sda2: Error: command ['/sbin/mdadm', '-E', '/dev/sda2'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda2.
MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb.
MDadmExamine.dev.sdb1: Error: command ['/sbin/mdadm', '-E', '/dev/sdb1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb1.
MDadmExamine.dev.sdb2: Error: command ['/sbin/mdadm', '-E', '/dev/sdb2'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb2.
MDadmExamine.dev.sdb3: Error: command ['/sbin/mdadm', '-E', '/dev/sdb3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb3.
MachineType: Dell Inc. Latitude D430
Package: mdadm 2.6.7.1-1ubuntu8
ProcCmdLine: root=UUID=8f0f3fe0-ee11-4851-be50-8dd9a6dc77b1 ro splash
ProcMDstat:
 Personalities :
 unused devices: <none>
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: mdadm
Title: package mdadm 2.6.7.1-1ubuntu8 failed to install/upgrade: subprocess post-installation script killed by signal (Interrupt)

Enry W (puw2012) wrote :
Jonas Pedersen (jonasped) wrote :

I can confirm this error. If no one is faster than me I will produce a debdiff to solve the issue. It will however not be before next ween as I am moving this weekend.

Changed in mdadm (Ubuntu):
status: New → Confirmed
Jonas Pedersen (jonasped) wrote :

I have uploaded an updated mdadm package to my PPA. Can you please try it out? It is located at https://launchpad.net/~jonasped/+archive/ppa. Package is currently being build by the build farm, so it is hopefully available within the next hour.

Attached is a debdiff.

Download full text (3.3 KiB)

I removed the old mdadm with synaptic and installed the new mdadm_2.6.7.1-1ubuntu9~ppa1~jaunty1_lpia.deb
         (232.1 KiB) with gdebi.
It installed like a charm.
Thank you for the prompt fix.

> Date: Sun, 3 May 2009 20:24:35 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 368986] Re: package mdadm 2.6.7.1-1ubuntu8 failed to install, with error /dev/MAKEDEV not found
>
> I have uploaded an updated mdadm package to my PPA. Can you please try
> it out? It is located at https://launchpad.net/~jonasped/+archive/ppa.
> Package is currently being build by the build farm, so it is hopefully
> available within the next hour.
>
> Attached is a debdiff.
>
> ** Attachment added: "mdadm_2.6.7.1-ubuntu8_to_2.6.7.1-ubuntu9.debdiff"
> http://launchpadlibrarian.net/26290105/mdadm_2.6.7.1-ubuntu8_to_2.6.7.1-ubuntu9.debdiff
>
> --
> package mdadm 2.6.7.1-1ubuntu8 failed to install, with error /dev/MAKEDEV not found
> https://bugs.launchpad.net/bugs/368986
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “mdadm” source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: mdadm
>
> I don't use arrays of disks, but Synaptic wants mdadm to be installed anyway when installing mondo recovery suite.
> System: Ubuntu 9.04 installed on a USB stick.
>
> >From Install log:
>
> Setting up mdadm (2.6.7.1-1ubuntu8)
> Generating array device nodes...
>
> /var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV not found
> failed
>
> ProblemType: Package
> Architecture: i386
> DistroRelease: Ubuntu 9.04
> ErrorMessage: subprocess post-installation script killed by signal (Interrupt)
> MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda.
> MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda1.
> MDadmExamine.dev.sda2: Error: command ['/sbin/mdadm', '-E', '/dev/sda2'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda2.
> MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb.
> MDadmExamine.dev.sdb1: Error: command ['/sbin/mdadm', '-E', '/dev/sdb1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb1.
> MDadmExamine.dev.sdb2: Error: command ['/sbin/mdadm', '-E', '/dev/sdb2'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb2.
> MDadmExamine.dev.sdb3: Error: command ['/sbin/mdadm', '-E', '/dev/sdb3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb3.
> MachineType: Dell Inc. Latitude D430
> Package: mdadm 2.6.7.1-1ubuntu8
> ProcCmdLine: root=UUID=8f0f3fe0-ee11-4851-be50-8dd9a6dc77b1 ro splash
> ProcMDstat:
> Personalities :
> unused devices: <none>
> ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
> SourcePackage: mdadm
> Title: package mdadm 2.6.7.1-1ubuntu8 failed to install/upgrade: subprocess post-installation script killed by signal (Interrupt)

_________________________________________________________________
I...

Read more...

Enry, thanks for tseting.

SRU team: Not sure if this can be a candidate for a SRU. If not just un-subscribe your self again.

Martin Pitt (pitti) wrote :

We have and require udev, so MAKEDEV shouldn't be required at all? Can it just be dropped?

Just chiming in to say I am having the same issue in Karmic Koala.

rowez (info-rowez) wrote :

I can confirm this error for Karmic with 2.6.7.1-1ubuntu13 when Mark for Installation (also after Mark for Complete Removal).

rowez (info-rowez) wrote :

When doing sudo MAKEDEV md in /dev (look to patch) it echo's :
.udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation.

The creation of the md* devices in /dev at the time of package installation does not seem to be too critical. I was able to create a 4x1TB RAID5 with mdadm under 9.10 with no issues, it seems like mdadm will automatically create the md0 device if it does not exist when creating a new raid.

Before creating the array I also tested the solution from the patch above, and came across the same error message that rowez reported.

ceg (ceg) on 2010-03-29
summary: - package mdadm 2.6.7.1-1ubuntu8 failed to install, with error
- /dev/MAKEDEV not found
+ mdadm 2.6.7.1-1ubuntu8 fails to install (missing obsolete /dev/MAKEDEV)
ceg (ceg) on 2010-03-29
summary: - mdadm 2.6.7.1-1ubuntu8 fails to install (missing obsolete /dev/MAKEDEV)
+ install fails missing obsolete /dev/MAKEDEV
John Dong (jdong) wrote :

I can't accept the nominations (need core-dev permissions), but as a comment, this bug is SRU-worthy due to the potential for upgrade script breakage. IMO the update script should not fail on MAKEDEV, as it's not terribly fatal that the devices couldn't be made at install time.

tags: added: iso-testing
ceg (ceg) on 2010-04-09
tags: added: dist-upgrade
ceg (ceg) wrote :

Fixed in Jools' packages linked in Bug #495370

Rick Benet (rgbenet) wrote :

I am writing this from Karmic as it is functional and evidently problem free. I had a good installation of Hardy and decided to upgrade to Lucid from that system on the same HD. All seemingly went well until, at one point, it said there had been some problem and that some programs might not operate properly. I continued on without any further problems until it came to do the start-up. It came to one particular point and stopped. I hand typed in what was on the terminal at that point and have included it in the attachment. I do hope you can help. Thanks

Daniel Richard G. (skunk) wrote :

Rick, please attach your report as a plain ASCII text file. There is no need for a word-processor-format document, and people here don't appreciate the extra effort needed to view it.

(That said, it's perfectly acceptable to submit a photograph of the screen with the error messages, rather than transcribe them all by hand.)

nsrderooy (nsrderooy) wrote :

#first install mdadm

sudo apt-get install mdadm

#here's a patch, install it by;

patch -p1 -i mdadm.postinst.patch /var/lib/dpkg/info/mdadm.postinst

#then run;

sudo dpkg-reconfigure mdadm

#enjoy

It's almost unbelievable that mdadm (and so software RAID) does not work on Ubuntu (and since so much time!). Please note that the patch it's a one-liner... Also please note that software RAID it's one way (the only one?) to get better performance from disks on the cloud (e.g. RAID0/striping helps parallelizing I/O requests with AWS EBS) and Ubuntu is investing so much in cloud computing.

BTW thanks nsrderooy for the patch, I applied it successfully but RAID continued to not work (maybe a kernel/initrd problem?).

nsrderooy (nsrderooy) wrote :

I can't believe it either, this bug is over a year old... and no one picks it up, I'm not a software dev, but if you post your problem I'll take a look to see if I can spot the problem.

Changed in mdadm (Ubuntu Jaunty):
status: New → Confirmed

I'm sorry but I've no time now to deal with this bug again, but it's easy to reproduce: launch an EC2 instance with Ubuntu 10.04 64bit EBS (AMI ami-3abf954e in EU as you can find here http://uec-images.ubuntu.com/releases/lucid/release/ ), attach a couple of EBS disks to it just to test, then try to create a new RAID0 in /dev/md0 and you'll get an error (even /proc/mdstat doesn't not exist if I remember correctly). Applying your patch let the installation of mdadm finish but doesn't solve the problems with RAID.

Clint Byrum (clint-fewbar) wrote :

I just ran into this bug while testing maverick isos:

clint@ubuntu:~$ sudo dpkg-reconfigure mdadm
[sudo] password for clint:
 * Stopping MD monitoring service mdadm --monitor
   ...done.
Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV: not found
failed.
 Removing any system startup links for /etc/init.d/mdadm-raid ...
update-initramfs: Generating /boot/initrd.img-2.6.35-22-server
update-rc.d: warning: mdadm start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (S)
update-rc.d: warning: mdadm stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 6)
 * Starting MD monitoring service mdadm --monitor
   ...done.

donarntz (donarntz) wrote :

I also ran into this but on maverick

I'm closing the task for Jaunty which has reached EOL.

Changed in mdadm (Ubuntu Jaunty):
status: Confirmed → Won't Fix
Changed in mdadm (Ubuntu Maverick):
status: New → Confirmed

accepting nominations per comment 12 and confirmation in comments 20 and 21.

Daniel Richard G. (skunk) wrote :

More confirmation is needed?

On a fully up-to-date Maverick system, two minutes ago:

# dpkg-reconfigure mdadm
Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV: not found
failed.
 Removing any system startup links for /etc/init.d/mdadm-raid ...
update-initramfs: Generating /boot/initrd.img-2.6.35-24-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
update-rc.d: warning: mdadm start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (S)
update-rc.d: warning: mdadm stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 6)

This is fixed in natty.

mdadm (3.1.4-1+8efb9d1ubuntu1) natty; urgency=low
[...]
    - debian/mdadm.config, debian/mdadm.postinst - let udev do the handling
      instead. Resolved merge conflict by keeping Ubuntu's version.

Setting the natty task to "fix released"
We don't need more confirmation but that someone port the fix from natty to maverick and lucid. Marking those 2 tasks triaged.

Changed in mdadm (Ubuntu):
status: Confirmed → Fix Released
Changed in mdadm (Ubuntu Maverick):
status: Confirmed → Triaged
Changed in mdadm (Ubuntu Lucid):
status: Confirmed → Triaged
Changed in mdadm (Ubuntu Maverick):
importance: Undecided → High
Changed in mdadm (Ubuntu Lucid):
importance: Undecided → High
JC Hulce (soaringsky) wrote :

This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached end-of-life and is no longer supported, so I am closing the bugtask for Maverick. Please upgrade to a newer version of Ubuntu.
More information here: https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html

Changed in mdadm (Ubuntu Maverick):
status: Triaged → Invalid
astrostl (astrostl) wrote :

I just ran into this "high" importance bug from 2009 on the long-term support, server version of Lucid (10.04.4 LTS).

What is the current status?

To post a comment you must log in.