.._ARRRGH!!!_; ext3 fs "is write-protected, mounting read-only", new bug?
..summary:
a45:~# mount -t ext3 -v -o remount,rw /dev/hda7 /var
mount: block device /dev/hda7 is write-protected, mounting read-only
/dev/hda7 on /var type ext3 (ro)
a45:~#
..it reboots _nicely_, just like Wintendo:
a45:~# cat /proc/mounts
/dev2/root / ext3 rw 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/hda1 /boot ext3 rw 0 0
/dev/hda6 /tmp ext3 rw 0 0
/dev/hda7 /var ext3 rw 0 0
/dev/hda11 /home ext3 rw 0 0
/dev/hda9 /usr ext3 rw 0 0
/dev/hda8 /usr/local ext3 rw 0 0
/dev/hdb5 /mnt ext3 rw 0 0
a45:~#
...then:...
a45:~# apt-get update # usually uselessly ends like:
...
W: Not using locking for read only lock file /var/lib/apt/lists/lock
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: Unable to write to /var/cache/apt/
E: The package lists or status file could not be parsed or opened.
...because:
a45:~# cat /proc/mounts
/dev2/root / ext3 rw 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/hda1 /boot ext3 rw 0 0
/dev/hda6 /tmp ext3 rw 0 0
/dev/hda7 /var ext3 ro 0 0
/dev/hda11 /home ext3 rw 0 0
/dev/hda9 /usr ext3 rw 0 0
/dev/hda8 /usr/local ext3 rw 0 0
/dev/hdb5 /mnt ext3 rw 0 0
..one of the few thing I found STFW:
a45:~# hdparm /dev/hda
/dev/hda:
multcount = 0 (off)
I/O support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 0 (off)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 10011/255/63, sectors = 160836480, start = 0
busstate = 1 (on)
a45:~# mount -t ext3 -v -o remount,rw /dev/hda7 /var
mount: block device /dev/hda7 is write-protected, mounting read-only
/dev/hda7 on /var type ext3 (ro)
a45:~# hdparm -d 1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on)
a45:~# hdparm /dev/hda
/dev/hda:
multcount = 0 (off)
I/O support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 10011/255/63, sectors = 160836480, start = 0
busstate = 1 (on)
a45:~# mount -t ext3 -v -o remount,rw /dev/hda7 /var
mount: block device /dev/hda7 is write-protected, mounting read-only
/dev/hda7 on /var type ext3 (ro)
..this damned fs _is_ clean:
a45:~# fsck -y -p /dev/hda7
fsck 1.27 (8-Mar-2002)
/dev/hda7 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? yes
/dev/hda7: recovering journal
/dev/hda7: clean, 248832/2621440 files, 3954934/5241198 blocks
a45:~#
a45:~# mount -t ext3 -v -o remount,rw /dev/hda7 /var
mount: block device /dev/hda7 is write-protected, mounting read-only
/dev/hda7 on /var type ext3 (ro)
a45:~#
..now, how do I remount the damned thing read-write???
..to "STFW!" me, beat:
http://www.google.com/search?num=100&hl=en&lr=&ie=UTF-8&oe=UTF-8&as_qdr=all&q=+ext3+%2B%22block+device%22+%2B%22write-protected%2C+mounting+read-only+%22++-cdrom+-lvm+
..have I run into a new bug???
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
Reply to: