File system in VM has errors

Every time I boot M7 in VirtualBox, I am getting the message

/dev/sda2 contains a file system with errors, check forced.

Alternately, like clockwork, fsck fixes the errors and everything seems to run normally. The next time, fsck fails, and the file system is mounted read-only. I did a new install, deleting the original vm, but the problem is the same. I did a checksum on the DVD image, and that looks fine, and I’m not having any problems on other VMs. Have other people who installed from the DVD had this problem?

Does the VM shut down completely?

In a real machine, neither the i686 or x86_64 installations from the
KDE Live CD have any problems of that sort.

I have to power it off from the VBox menu. As it is, the VM is mounting read-only half of the time, so I can’t log on can’t shut it down gracefully.

I should mention, this happened after a clean install, too, and shutting down within VM. Do you know of a way to find out if the VM is not actually shutting down?

Something I hadn’t noticed before, I am seeing a message “Umount failed, trying to remount read-only” when I shut down from the terminal.

chief sealth wrote:
> Something I hadn’t noticed before, I am seeing a message “Umount failed,
> trying to remount read-only” when I shut down from the terminal.

That is the problem. Some process is not shutting down. Before you
shut down, have a look at the process list to see what might unusual.

Based on the messages, everything is shutting down, except SuSEfirewall (skipped), but I’ve shut that down manually with no effect. I don’t see anything unusual in ps, but I could be missing something.

Output of ps -A:


  PID TTY          TIME CMD
    1 ?        00:00:02 init
    2 ?        00:00:00 kthreadd
    3 ?        00:00:00 migration/0
    4 ?        00:00:00 ksoftirqd/0
    5 ?        00:00:00 watchdog/0
    6 ?        00:00:00 events/0
    7 ?        00:00:00 cpuset
    8 ?        00:00:00 khelper
    9 ?        00:00:00 netns
   10 ?        00:00:00 async/mgr
   11 ?        00:00:00 kintegrityd/0
   12 ?        00:00:01 kblockd/0
   13 ?        00:00:00 kacpid
   14 ?        00:00:00 kacpi_notify
   15 ?        00:00:00 kacpi_hotplug
   16 ?        00:00:00 ksuspend_usbd
   17 ?        00:00:00 khubd
   18 ?        00:00:00 kseriod
   19 ?        00:00:00 kondemand/0
   20 ?        00:00:00 khungtaskd
   21 ?        00:00:00 pdflush
   22 ?        00:00:00 pdflush
   23 ?        00:00:00 kswapd0
   24 ?        00:00:00 aio/0
   25 ?        00:00:00 kpsmoused
   53 ?        00:00:00 ata/0
   54 ?        00:00:00 ata_aux
   59 ?        00:00:00 scsi_eh_0
   60 ?        00:00:00 scsi_eh_1
  184 ?        00:00:00 kjournald2
  246 ?        00:00:01 stapio
  251 ?        00:00:03 systemtap/0
  264 ?        00:00:00 startpar
  278 ?        00:00:00 udevd
  421 ?        00:00:00 kauditd
  435 ?        00:00:00 kstriped
  829 ?        00:00:00 acpid
  832 ?        00:00:00 dbus-daemon
  940 ?        00:00:01 hald
  951 ?        00:00:00 console-kit-dae
  952 ?        00:00:00 hald-runner
 1092 ?        00:00:00 hald-addon-inpu
 1125 ?        00:00:00 hald-addon-stor
 1132 ?        00:00:00 hald-addon-stor
 1136 ?        00:00:00 hald-addon-acpi
 2107 ?        00:00:00 rsyslogd
 2148 ?        00:00:00 rpcbind
 2161 ?        00:00:00 auditd
 2165 ?        00:00:00 audispd
 2186 ?        00:00:00 udevd
 2211 ?        00:00:00 dhcpcd
 2214 ?        00:00:00 udevd
 2249 ?        00:00:00 avahi-daemon
 2281 ?        00:00:00 cupsd
 2518 ?        00:00:00 master
 2546 ?        00:00:00 qmgr
 2550 ?        00:00:00 cron
 2576 ?        00:00:00 ntpd
 2637 ?        00:00:00 stop_preload
 2641 ?        00:00:00 startpar
 2643 ?        00:00:00 waitforidle
 2730 ?        00:00:00 login
 2731 tty2     00:00:00 mingetty
 2732 tty3     00:00:00 mingetty
 2733 tty4     00:00:00 mingetty
 2734 tty5     00:00:00 mingetty
 2735 tty6     00:00:00 mingetty
 2751 ?        00:00:00 pickup
 2754 tty1     00:00:00 bash
 2783 tty1     00:00:00 ps

chief sealth wrote:
> lwfinger;2039372 Wrote:
>> chief sealth wrote:
>>> Something I hadn’t noticed before, I am seeing a message “Umount
>> failed,
>>> trying to remount read-only” when I shut down from the terminal.
>> That is the problem. Some process is not shutting down. Before you
>> shut down, have a look at the process list to see what might unusual.
>
> Based on the messages, everything is shutting down, except SuSEfirewall
> (skipped), but I’ve shut that down manually with no effect. I don’t see
> anything unusual in ps, but I could be missing something.
>
>
> Output of ps -A:

If you use ‘ps ax’, you will see the process status.

Hi
I have a similar error and it appears the /etc/init.d/boot.clock is not
working correctly ( I need to debug some more)

As a hack, down in the timzone case of boot.clock, change --noadjfile to
–localtime fixes the issue.


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.2 Milestone 7 (i586) Kernel 2.6.31-rc9-7-desktop
up 0:03, 2 users, load average: 0.95, 0.79, 0.34
ASUS eeePC 1000HE ATOM N280 1.66GHz | GPU Mobile 945GM/GMS/GME