Bugzilla – Bug 120123
Error on unmounting
Last modified: 2008-06-25 09:52:53 UTC
With every system I tried 10.1 alpha1 on, I get an error on shutdown when it tries to unmount the volumes. Shutdown continues but there´s a "failed" message on the right side of the screen. Since the system shuts down I don´t know how to post a log message about that, but I think it´s reproducible.
Reorder your volumes in /etc/fstab. Currently one or more volumes are unmounted after those volumes which contain the corresponding mount point for the failing volumes.
YaST2 generated my fstab like this: /dev/hda2 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hda3 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/dvd /media/ subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 If the order of the first two partitions is wrong, then this must be a bug in YaST2
The only wrong entry I see is for /dev/dvd. The point point should be /media/dvd but never /media/ because the last / is ignored.
Should I file a seperate bug report abot this about YaST2(I didn´t change the fstab myself)? And is there a log which records the error on shutdown, so that I can send it to you? It just says something like "failed to unmount /dev/sda2" then something about "remounting read-only" and then "I hope it´s ok now".
Which HW belongs to /dev/sda2?
/dev/sda2 is my swap partition. I tried to read the error message (in the short time it displays) and there´s the following line: "unmounting /dev : device is busy" and this is the actual error I think. The rest of the filesystems seems to be unmounted fine.
Please provide the output of `fdisk -l' Then: /dev should not tried to be unmounted because it is not a mount point. So are you sure it displays ``unmounting /dev:...''? Would be useful to have the y2logs of the installation and information about what you told YaST to do (manual setup, automatic setup, ...). Thanks
The exact message is: "umount: /dev : device is busy" when I execute "mount" I get this entry: initramdevs on /dev type tmpfs (rw) could it be that the script tries to unmount this filesystem? Unfortunately I don´t have the installation logs any more (or are they saved in a special place)? I did a regular automatic install. I had a windows partition on /dev/sda1 a reiserfs on /dev/sda2 and a swap one on /dev/sda3
You might read: http://www.opensuse.org/Bug_Reporting_FAQ#YaST And still we need the output of `fdisk -l', thanks.
Created attachment 51635 [details] All YaST2 logs
r098088:/home/michael # fdisk -l Platte /dev/sda: 250.0 GByte, 250059350016 Byte 255 Köpfe, 63 Sektoren/Spuren, 30401 Zylinder Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes Gerät boot. Anfang Ende Blöcke Id System /dev/sda1 1 9858 79184353+ 7 HPFS/NTFS /dev/sda2 9859 26548 134062425 f W95 Erw. (LBA) /dev/sda3 * 26549 30331 30386944 83 Linux /dev/sda4 30332 30401 562275 82 Linux Swap / Solaris /dev/sda5 9859 17080 58010683+ b W95 FAT32 /dev/sda6 17081 19139 16538886 b W95 FAT32 /dev/sda7 19140 19344 1646631 b W95 FAT32 /dev/sda8 19345 26548 57866098+ b W95 FAT32
werner, could you please look at this again?
Hmmm ... now why is there used /dev/hda2, /dev/hda1, and /dev/hda3 wheras later on I see /dev/sda1, /dev/sda2 ...??? Please do not mix old ATA with SATA and SCSI. And is the mount point for the DVD now correct?? Beside this the initrd script should handle its mounts correct.
Sorry, I´ve two computers and the bug occurs on both of them. I sent you the fstab from the first and now the fdisk log from the second. The DVD mountpoint is correct (it was never wrong). Since it happened on both of my computers I thought this was easy to reproduce.
I have the exact same error. I was running 10 and just updated to Alpha 3 and the error persists. Here's my fstab: bip@xxx:~> cat /etc/fstab /dev/hda2 / reiserfs acl,user_xattr 1 1 /dev/hda1 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/hda3 /data1 auto noauto,user 0 0 /dev/dvdram /media/dvdram subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 none /subdomain subdomainfs noauto 0 0 and here's my fdisk -l: bip@xxx:~> sudo /sbin/fdisk -l Disk /dev/hda: 60.0 GB, 60011642880 bytes 255 heads, 63 sectors/track, 7296 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 131 1052226 82 Linux swap / Solaris /dev/hda2 * 132 6790 53480385+ 83 Linux /dev/hda3 6790 7296 4072477 83 Linux
Jan, I remember you having said something about this issue...
No. I said something about busy inodes on umount not about busy filesystems when shutting down. To me it seems that something is mounted on top of /dev. You can use "fuser -vm /dev" to see the processes accessing the /dev mountpoint.
Michael: Have you tried changes the order in fstab as Werner suggested? Does it give any result?
The fstab created by the latest beta is completely unusable (my windows partitions are missing), so I haven´t seen this any more. You can close it, if I experience it again (with a useable fstab) with the next ebta I´ll reopen.
OK, let's close it for now.
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(