WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: 2.1: Can't remount read-only  (Read 2285 times)

Offline danielibarnes

  • Hero Member
  • *****
  • Posts: 548
2.1: Can't remount read-only
« on: July 14, 2009, 02:32:54 PM »
If I have a .tcz loaded, when I shutdown I get the message:
umount: Can't remount /dev/hda read-only
after "Unmounting all filesystems..."

On startup, I have to e2fsck /dev/hda:
/dev/hda was not cleanly unmounted, check forced.

This is a pretty big problem; I can't be the only one seeing it unless I'm doing something completely wrong. Does anyone have any ideas? It appears as though the loop processes aren't killed. If I umount and losetup -d all of the loop devices then I can shutdown without error.

Steps to reproduce:
1) Boot TC 2.1
2) Log in as tc user and tce-load any .tcz extension
3) shutdown or reboot

This occurs on a standard 2.1 release with no additional boot options.

Thanks,
Daniel
« Last Edit: July 15, 2009, 03:38:12 PM by danielibarnes »

Offline danielibarnes

  • Hero Member
  • *****
  • Posts: 548
Re: 2.1: Can't remount read-only
« Reply #1 on: July 15, 2009, 03:39:57 PM »
Does anyone else see this error? Adding the following to /etc/init.d/rc.shutdown right before "/bin/umount -arf" prevents it:

for loop in $(losetup -a|cut -d: -f1); do umount -d $loop 2>/dev/null; done
for loop in $(losetup -a|cut -d: -f1); do umount -d $loop 2>/dev/null; done

It is repeated twice in case there is a loop device mounted within a loopback file.

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: 2.1: Can't remount read-only
« Reply #2 on: July 15, 2009, 05:26:34 PM »
I have not experienced...
Quote
On startup, I have to e2fsck /dev/hda:
/dev/hda was not cleanly unmounted, check forced.
However, I see no reason not to add code to specifically unmount mounted loop files. You suggestion will be in the next RC.
 
Thanks for your input..
10+ Years Contributing to Linux Open Source Projects.