"Read-only file system" errors during install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lm-sensors-3 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: libsensors4
This concerns libsensors4 version 1:3.0.2-1ubuntu2 in Intrepid.
On installing libsensors4 for the first time, I see the following (excerpted) in the output of apt-get:
----begin----
Setting up libsensors4 (1:3.0.2-1ubuntu2) ...
udev active, devices will be created in /dev/.static/dev/
rm: cannot remove `i2c-0-': Read-only file system
mknod: `i2c-0-': Read-only file system
makedev i2c-0 c 89 0 root root 0600: failed
rm: cannot remove `i2c-0-': Read-only file system
rm: cannot remove `i2c-1-': Read-only file system
mknod: `i2c-1-': Read-only file system
makedev i2c-1 c 89 1 root root 0600: failed
rm: cannot remove `i2c-1-': Read-only file system
rm: cannot remove `i2c-2-': Read-only file system
mknod: `i2c-2-': Read-only file system
makedev i2c-2 c 89 2 root root 0600: failed
rm: cannot remove `i2c-2-': Read-only file system
rm: cannot remove `i2c-3-': Read-only file system
mknod: `i2c-3-': Read-only file system
makedev i2c-3 c 89 3 root root 0600: failed
rm: cannot remove `i2c-3-': Read-only file system
rm: cannot remove `i2c-4-': Read-only file system
mknod: `i2c-4-': Read-only file system
makedev i2c-4 c 89 4 root root 0600: failed
rm: cannot remove `i2c-4-': Read-only file system
rm: cannot remove `i2c-5-': Read-only file system
mknod: `i2c-5-': Read-only file system
makedev i2c-5 c 89 5 root root 0600: failed
rm: cannot remove `i2c-5-': Read-only file system
rm: cannot remove `i2c-6-': Read-only file system
mknod: `i2c-6-': Read-only file system
makedev i2c-6 c 89 6 root root 0600: failed
rm: cannot remove `i2c-6-': Read-only file system
rm: cannot remove `i2c-7-': Read-only file system
mknod: `i2c-7-': Read-only file system
makedev i2c-7 c 89 7 root root 0600: failed
rm: cannot remove `i2c-7-': Read-only file system
Creating config file /etc/sensors3.conf with new version
----end----
See bug #270043 for a similar problem reported against mdadm.
seems or seemed to be a general issue with dpkg or udev or something (search bugs with "rm: cannot remove")