intrepid - rm: cannot remove `md0-': Read-only file system

[Savvas Radevic]

Binary package hint: mdadm

I was upgrading some packages and faced this weird errors (see at the end, when it finishes setting up mdadm)
Attached /var/log/dpkg.log

$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  binutils binutils-static mdadm python2.5 python2.5-minimal
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 6968kB of archives.
After this operation, 20.5kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com intrepid/main python2.5 2.5.2-11ubuntu2 [3063kB]
Get:2 http://archive.ubuntu.com intrepid/main python2.5-minimal 2.5.2-11ubuntu2 [1271kB]
Get:3 http://archive.ubuntu.com intrepid/main binutils 2.18.90.20080910-0ubuntu1 [1631kB]
Get:4 http://archive.ubuntu.com intrepid/main binutils-static 2.18.90.20080910-0ubuntu1 [768kB]
Get:5 http://archive.ubuntu.com intrepid/main mdadm 2.6.7-3ubuntu5 [233kB]
Fetched 6968kB in 3min12s (36.1kB/s)
Preconfiguring packages ...
(Reading database ... 129695 files and directories currently installed.)
Preparing to replace python2.5 2.5.2-11ubuntu1 (using .../python2.5_2.5.2-11ubuntu2_amd64.deb) ...
Unpacking replacement python2.5 ...
Preparing to replace python2.5-minimal 2.5.2-11ubuntu1 (using .../python2.5-minimal_2.5.2-11ubuntu2_amd64.deb) ...
Unpacking replacement python2.5-minimal ...
Processing triggers for man-db ...
Setting up python2.5-minimal (2.5.2-11ubuntu2) ...

(Reading database ... 129695 files and directories currently installed.)
Preparing to replace binutils 2.18.50.20080814-0ubuntu1 (using .../binutils_2.18.90.20080910-0ubuntu1_amd64.deb) ...
Unpacking replacement binutils ...
Preparing to replace binutils-static 2.18.50.20080814-0ubuntu1 (using .../binutils-static_2.18.90.20080910-0ubuntu1_amd64.deb) ...
Unpacking replacement binutils-static ...
Preparing to replace mdadm 2.6.7-3ubuntu4 (using .../mdadm_2.6.7-3ubuntu5_amd64.deb) ...
 * Stopping MD monitoring service mdadm --monitor [ OK ]
Unpacking replacement mdadm ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 1 changed doc-base file(s)...
Registering documents with scrollkeeper...
Setting up python2.5 (2.5.2-11ubuntu2) ...

Setting up binutils (2.18.90.20080910-0ubuntu1) ...

Setting up binutils-static (2.18.90.20080910-0ubuntu1) ...
Setting up mdadm (2.6.7-3ubuntu5) ...
Generating array device nodes... rm: cannot remove `md0-': Read-only file system
mknod: `md0-': Read-only file system
rm: cannot remove `md0-': Read-only file system
rm: cannot remove `md1-': Read-only file system
mknod: `md1-': Read-only file system
rm: cannot remove `md1-': Read-only file system
rm: cannot remove `md2-': Read-only file system
mknod: `md2-': Read-only file system
rm: cannot remove `md2-': Read-only file system
rm: cannot remove `md3-': Read-only file system
mknod: `md3-': Read-only file system
rm: cannot remove `md3-': Read-only file system
rm: cannot remove `md4-': Read-only file system
mknod: `md4-': Read-only file system
rm: cannot remove `md4-': Read-only file system
rm: cannot remove `md5-': Read-only file system
mknod: `md5-': Read-only file system
rm: cannot remove `md5-': Read-only file system
rm: cannot remove `md6-': Read-only file system
mknod: `md6-': Read-only file system
rm: cannot remove `md6-': Read-only file system
rm: cannot remove `md7-': Read-only file system
mknod: `md7-': Read-only file system
rm: cannot remove `md7-': Read-only file system
rm: cannot remove `md8-': Read-only file system
mknod: `md8-': Read-only file system
rm: cannot remove `md8-': Read-only file system
rm: cannot remove `md9-': Read-only file system
mknod: `md9-': Read-only file system
rm: cannot remove `md9-': Read-only file system
rm: cannot remove `md10-': Read-only file system
mknod: `md10-': Read-only file system
rm: cannot remove `md10-': Read-only file system
rm: cannot remove `md11-': Read-only file system
mknod: `md11-': Read-only file system
rm: cannot remove `md11-': Read-only file system
rm: cannot remove `md12-': Read-only file system
mknod: `md12-': Read-only file system
rm: cannot remove `md12-': Read-only file system
rm: cannot remove `md13-': Read-only file system
mknod: `md13-': Read-only file system
rm: cannot remove `md13-': Read-only file system
rm: cannot remove `md14-': Read-only file system
mknod: `md14-': Read-only file system
rm: cannot remove `md14-': Read-only file system
rm: cannot remove `md15-': Read-only file system
mknod: `md15-': Read-only file system
rm: cannot remove `md15-': Read-only file system
rm: cannot remove `md16-': Read-only file system
mknod: `md16-': Read-only file system
rm: cannot remove `md16-': Read-only file system
rm: cannot remove `md17-': Read-only file system
mknod: `md17-': Read-only file system
rm: cannot remove `md17-': Read-only file system
rm: cannot remove `md18-': Read-only file system
mknod: `md18-': Read-only file system
rm: cannot remove `md18-': Read-only file system
rm: cannot remove `md19-': Read-only file system
mknod: `md19-': Read-only file system
rm: cannot remove `md19-': Read-only file system
rm: cannot remove `md20-': Read-only file system
mknod: `md20-': Read-only file system
rm: cannot remove `md20-': Read-only file system
rm: cannot remove `md21-': Read-only file system
mknod: `md21-': Read-only file system
rm: cannot remove `md21-': Read-only file system
rm: cannot remove `md22-': Read-only file system
mknod: `md22-': Read-only file system
rm: cannot remove `md22-': Read-only file system
rm: cannot remove `md23-': Read-only file system
mknod: `md23-': Read-only file system
rm: cannot remove `md23-': Read-only file system
rm: cannot remove `md24-': Read-only file system
mknod: `md24-': Read-only file system
rm: cannot remove `md24-': Read-only file system
rm: cannot remove `md25-': Read-only file system
mknod: `md25-': Read-only file system
rm: cannot remove `md25-': Read-only file system
rm: cannot remove `md26-': Read-only file system
mknod: `md26-': Read-only file system
rm: cannot remove `md26-': Read-only file system
rm: cannot remove `md27-': Read-only file system
mknod: `md27-': Read-only file system
rm: cannot remove `md27-': Read-only file system
rm: cannot remove `md28-': Read-only file system
mknod: `md28-': Read-only file system
rm: cannot remove `md28-': Read-only file system
rm: cannot remove `md29-': Read-only file system
mknod: `md29-': Read-only file system
rm: cannot remove `md29-': Read-only file system
rm: cannot remove `md30-': Read-only file system
mknod: `md30-': Read-only file system
rm: cannot remove `md30-': Read-only file system
rm: cannot remove `md31-': Read-only file system
mknod: `md31-': Read-only file system
rm: cannot remove `md31-': Read-only file system
done.
 Removing any system startup links for /etc/init.d/mdadm-raid ...
update-initramfs: deferring update (trigger activated)
 * Starting MD monitoring service mdadm --monitor [ OK ]

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.27-3-generic

$ apt-cache policy mdadm
mdadm:
  Installed: 2.6.7-3ubuntu5
  Candidate: 2.6.7-3ubuntu5
  Version table:
 *** 2.6.7-3ubuntu5 0
        500 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

[Savvas Radevic (medigeek)]

I'm not sure if it causes any problems, but it seems that it's due to
the fact that the mdrun script was removed (?)

[Savvas Radevic (medigeek)]

probably a one-time issue

[Julien Cochuyt (julien-cochuyt)]

Reproduced on a freshly installed&updated Intreprid 64 bits.
Install was clean but same behavior when running

dpkg-reconfigure mdadm

[aftertaf (david-wooffindin)]

I have exact same error on install and also dpkg-reconfigure of mdadm on a fresh kubuntu 8.10 32 bit.

I want to use it to 'mount' as RAID an existing RAID 1 fakeraid with Windows installed on it...

[Daniel Richard G. (skunk)]

The libsensors4 package has a similar problem. See bug #329792.

[JakubPisarczyk (jpisarczyk)]

Same thing with:
# apt-cache policy mdadm
mdadm:
  Installed: 2.6.7-3ubuntu8
  Candidate: 2.6.7-3ubuntu8
  Version table:
 *** 2.6.7-3ubuntu8 0
        500 http://pl.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

# dpkg-reconfigure mdadm
 * Stopping MD monitoring service mdadm --monitor [ OK ]
Generating array device nodes... rm: cannot remove `md0-': Read-only file system
mknod: `md0-': Read-only file system
rm: cannot remove `md0-': Read-only file system
rm: cannot remove `md1-': Read-only file system
mknod: `md1-': Read-only file system
rm: cannot remove `md1-': Read-only file system
rm: cannot remove `md2-': Read-only file system

[Savvas Radevic (medigeek)]

Has anyone noticed this lately? In ubuntu 9.10 karmic alpha 5? I haven't, marking this as incomplete. :)

[ceg (ceg)]

seems or seemed to be a general issue with dpkg or udev or something (search bugs with "rm: cannot remove")

[Launchpad Janitor (janitor)]

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