Read-Only Filesysten on boot

zkab · 10-18-2010, 08:45 AM

I have Squeeze (amd64).
During sudo aptitude update && sudo aptitude -y full-upgrade && sudo aptitude autoclean the command stalled and did not react on ^C so I forced-quit the terminal window. When rebooting ... the system tells me it is read-only.
To solve the problem I booted from Debian Live CD and did sudo mount -n -o -t ext3 remount,rw /dev/sda1 /.
I also did sudo fsck /dev/sda1 and it was clean.
/etc/mtab gives /dev/sda1 / ext3 rw,errors=remount-ro 0 0
But still ... when I boot from disk ... it is read-only.
Where do I change to get it back to normal ?

scheidel21 · 10-18-2010, 09:43 AM

Change the errors=remount-ro maybe? Is it saying the FS is read only after you are into it? Dealing with an unstable distro can cause all sorts of havoc, I wish you luck.

zkab · 10-18-2010, 10:16 AM

Quote:

Originally Posted by scheidel21

Change the errors=remount-ro maybe?

This is the option when something is wrong with the FS ... then the FS is mounted read-only. But I have fsck the FS and it gave me a clean FS as result.
There must be somewhere else where ro can be changed to rw.
Squeeze is testing version - not unstable - and due to become stable very soon ... this is the first time something strange happened ... been running it for a long time.

scheidel21 · 10-18-2010, 10:32 AM

Can you force a mount in RW and try the failed update again, maybe that might fix it up.

zkab · 10-18-2010, 02:53 PM

I changed in /etc/fstab from /dev/sda1 / ext3 errors=remount-ro 0 1
to /dev/sda1 / ext3 defaults 0 1
but same sad result

zkab · 10-20-2010, 01:22 PM

Syslog looks strange (pastebin.com/jMuWe1rG) ... task dpkg:3968 blocked for more than 120 seconds.