Ubuntu :: 10.04 Usb Devices Not Unmounting Correctly?
May 6, 2010
I have just installed 10.04 as an upgrade from 9.10.
I am having difficulty because none of the USB drives I am using are unmounting as they should be. normally speaking when erasing data from my USB key when you come to unmounting it it will ask if you would like to send this data to the recycle bin thus giving you back the extra storage space on the device. 10.04 isnt allowing me to send these items to the recycle bin ad doesn't give the option to do this.
10.10 MMeerkat - When I use a USB-stick or external hard drive, I don't get the "unmount" option but instead it says "safely remove drive".When I click this, Nautilus immediately crashes and is gone.Is this a known bug in 10.10?
I've spent the better part of an afternoon looking for a solution to a problem: backing up my installation of 10.10 as an image file to an external hard drive. My research has yielded a lot of suggestions for clonezilla, dd, and partimage/particlone, but those don't seem very appealing, due to a number of issues (can't backup live, copies free space as well, doesn't handle ext4, etc). Also why is clonezilla 150mb?
I'd like a simple solution that can clone an entire disk (used space only) to an explorable image file on a separate hard drive and be able to do it while the operating system is running on the disk. I used to use apricorn ez gig to do this on windows and it worked like a charm, but I can't seem to find a similar solution that creates and explorable .iso image file with linux. I've used superduer on osx, which is awesome and i wish there was something like that for ubuntu/linux.
Very frustrated. I have used Unix for ages so I understood the SysV startup stuff. But I have not had a lot of luck with Upstart. The other day I noticed that on every reboot my disks are getting fsck'd. I just recently put an ext2 on /tmp so this takes a while (the ext4 drives just rip through their journals).
The problem is no one is unmounting them on a KDE restart (4.X). I started out looking at /etc/init.d/umountfs and putting some logging in there. It never runs. This is despite that /etc/init has an upstart job that is supposed to run all the runlevel stuff.
I also tried to log some info in /etc/init/mountall-shell.conf which looks like it tries to do a umount -a on shutdown (which is probably not a good idea; you need to unmount in a particular order). That doesn't seem to happen either. I am not even sure how to troubleshoot this further. I suppose I need to see if the reboot( command has the same problem. Or if I shut down kdm first if it goes away.
I get the following error each time I try to safely remove the USB stick (by right-clicking on the USB stick icon on the desktop and choosing "Remove safely") code...
It used to work without errors when unmounting the USB from Nautilus window, but now, I get the same error when unmounting from there as well. Is it safe to assume that the stick can be removed even though the error message is displayed? What might be the cause? Also, I do not have any Nautilus-windows opened nor any applications that are locking any files on the USB stick while removing it.
I want to move my / partition to the end of my drive (sda). To do this with gparted, I have to unmount it, but I'm not comfortable with the idea of unmounting root partition... Should I do it from a live cd? More important : is the operation safe?
We are using Ubuntu 10.04LTS server on Vmware Vsphere estate. We are using LVM and have / and /var on separate partitions.
We have been experiencing an odd issue with sda1 always being fsck'd after every reboot. We seem to have traced this to the start/kill scripts in rc0.d and rc6.d. It appears that the reason the disk is not being unmounted is because some of the scripts are never being run because they are prefixed with S. We renamed and reordered the scripts to reflect what we thought should be the correct order - i.e. not halting the system before unmounting disks. System reboots cleanly now.
Before list of rc0.d and rc6.d respectively: lrwxrwxrwx 1 root root 17 2010-11-18 15:06 K01apache2 -> ../init.d/apache2 lrwxrwxrwx 1 root root 22 2010-11-16 17:03 K01zabbix-agent -> ../init.d/zabbix-agent lrwxrwxrwx 1 root root 22 2010-11-30 08:16 K03vmware-tools -> ../init.d/vmware-tools
basically are we expected to do these changes as part of building new servers for production use? Quite happy to do this but just surprised that this is the default.
I have an external hard drive (1TB MyBook) mounted via fstab by UUID to a directory. When copying/writing/reading a lot of files from it, it randomly unmounts and remounts as a different device.
It'll start as /dev/sdb1, I'll set a lot of files to copy to it and then it'll unmount and re-acknowledge itself as /dev/sdc1, the file copying process will crash and the current directory in terminal will display an I/O error. Running mount -a remounts it back to the directory specified in fstab as /dev/sdc1 and the loop continues. If it's just idling, there's no issue, only does this under load.
- Nautilus open in browser mode (the default)?- I click the eject symbol to unmount a usb stick in the side pane.- The annoying red exclamation police light looking thing pops up telling me that nautilus crashed.- Not only is the usb stick unmounted, but the device file also disapears (e.g. no longer listed by fdisk).- This problem does NOT occur when I use other methods to unmount (e.g. umount on command line, or right-click on desktop icon and select eject action), only when I click the eject symbol in the nautilus side pane
been puzzling over this for a while, searched forums and net but no issues/solutions found. I have the above device plugged in and working fine. However when un-mounting - either through dolphin or device notifier, I get the report that the item is unmounted but then when removing USB cable from the Zen, it closes down and then rebuilds the entire 16GB collection - this takes quiet a bit of time and I worry that I may end up frying the Zen. Is there a fix for this in Suse or is it the zen. it doesn't happen on my work machine running windows though.
I have a volume that shows as the following when I do a df -h. How would I go about unmounting it so I can run an e2fsck on it, then remounting it? normally it mounts when the server starts, so i'm not sure how to manually do it.
Sometimes I get a problem with the basic "umount" command. I get an error message telling me that for one reason or another, the device couldn't be unmounted. Usually, it says the device is busy, when I can't see how it possibly can be. When this happens I'll use "umount -l" or "umount -f" or sometimes "eject" but I'm still not happy, because at the back of my mind I'm worried about damaging the integrity of the device's filesystem. What's the CORRECT way to deal with this problem?
I stupidly unplugget my USB-cable, which was connected to my Nokia music phone, just as if I were in Windows. What do I do? I've lost my music on the phone, or, it seems it may be there (the correct mass of data), but my phone now tells me there is no music... Can I recover this? And - what is the correct way to unplug a USB unit in Ubuntu? To make it work, and find the phone/drive - I just typed "sudo lsusb" in the terminal, and it found and opened the memory automatically... How should you unmount the USB, and maybe even how do I get my data back?
I have a server with Ubuntu 8.04.4 LTS completely patched up to date.I tried to mount a windows share using smbmount and unmounting it with smbumount. I did it as a non root user (let's say "someuser") and managed to mount the share without problems with "smbmount \\server\share xxx" where "xxx" was a directory on the user's root. After it I could see the shared files in the xxx directory, as it was supposed to be...
The problems came when trying to unmount it. Using "smbumount \\server\share xxx" didn't work giving "This utility only unmounts cifs filesystems." error message. Then I tried "smbumount xxx" and worked. I couldn't see the files in xxx directory anymore, and I could even delete xxx directory.
But now, when looking at /etc/mtab file, I still can see the share listed as mounted! The line is: "//server/share /home/someuser/xxx cifs rw,mand,nosuid,nodev,user=someuser 0 0". Also, df command lists the share as mounted too. But, as I said, the share is not really mounted, and I can even delete xxx directory without any problem... /proc/mounts doesn't list the share as mounted either... And, obviously, fstab file has no entry for this mount.
Moreover, /etc/mtab file group changed from root to someuser!I don't really understand what happened, but I assume some bug with smbumount or smbmount. Anyway, what does really worry me is how to fix this mess... I already changed mtab file group back to root, but I don't know how to return the mtab file to a consistent state.My main question is: can I simply edit mtab file and remove the inconsistent line?? I know one should never have to manually edit this file, but can it really be done in a situation like the one I'm describing? What could happen if I do it?
Also, I'm worried about if I don't do something to fix the inconsistency I could have problems when trying to shutdown the computer, or in any other situation. So, should it be safe to leave things unfixed and let everything return to normality when the system is rebooted?
after some hard times, I finally managed to have my Orange Huawei E1752 HSPA modem running (a USB modem enabling you to surf the net) the only thing is that I have 2 "problems" with this: I cannot find a clean way to eject the stick when I am done using it. when I want to run it, I plug it, it asks me for the PIN code, which I give, then I do the following manipulations: I first run:
usb_modeswitch it "creates" 2 files /dev/ttyUSB0 and /dev/ttyUSB1, what I check with: ls -l /dev/ttyUSB*
then I use the usbserial module to handle the stick: modprobe usbserial vendor=0x12d1 product=0x141b then I check that the stick is working with: dmesg|grep GSM that outputs something like: USB Serial support registered for GSM modem (1-port) option 1-5:1.0: GSM modem (1-port) converter detected usb 1-5: GSM modem (1-port) converter now attached to ttyUSB0 option 1-5:1.1: GSM modem (1-port) converter detected usb 1-5: GSM modem (1-port) converter now attached to ttyUSB1 option: v0.7.2:USB Driver for GSM modems finally I choose the "Orange Default" in the list of available connections in the network manager icon on the panel and I am finally connected The thing is, that when I am done, I just go to the same list and then click "disconnect" I go on "Computer" and left click on the SD 4Gb storage (the SD card also in the stick) safely remote drive or something like this. Then I thought that unmounting the device would work,
As a newbie (and especially regarding the use of those modems) I am running out of ideas to "eject" it cleanly, I also checked in the /dev/ file to see that the ttyUSB0 and ttyUSB1 files are present
A client is having a problem with a recently installed CentOS 5.5 x86_64 Virtual Machine (under VMware ESX 3.5). The problem is reported by the user as "Nautilus windows closing after a time when looking at data from the NFS server".
The folders the user is using are in a file system that is NFS mounted from a Solaris 10 file server cluster (VCS). These are mounted using autofs. These are direct mounts as in:
I have reproduced the problem by logging in and opening a number of folders using Nautilus under /opt/user-data. After a while, all Nautilus folder windows that are under /opt/user-data will close and when this occurs you can see from the command line that autofs has unmounted the area from the file server.
This should not occur because Nautilus having a window open should count as the folder being in use and should stop autofs from unmounting it. I don't know if this is an autofs or Nautilus bug but I suspect it's a Nautilus bug in it not keeping some kind of access open on the folder. System information:
The system was updated at install time. /boot/grub/grub.conf has "divider=10" appended to the kernel line.VMware Tools are installed. NTP is also configured and steps the time to UTC at boot if required (maybe this is overkill). autofs and Nautilus versions are:
I have an external DVD burner hooked up to an EEE PC 701SD. The disk has worked on a dell desktop computer, and a 701 (the first eee pc which I built the install on) without a problem, however when I boot up the install disk on the 701SD, I get a message telling me it's unable to download the kickstart file. It's being set to cdrom:/ks.cfg, which should work, but it isn't.... This exact same disk just did a full install on the 701 15 minutes before I ran it on this computer.
Gnome version 2.28.1 with kernel 2.6.31-14 on an Ubuntu 9.10 Karmic box.I'm wondering how usb drives, etc get automounted in gnome now days. Thought it might be fusermount, but no.Gnome-mount is not installed. Perhaps it is via AL or udev, but what commands control it? I've found posts that talk about using gnome-mount, but these are outdated as this package isn't even installed by default anymore.I would like to unmount certain volumes via the command line, but without having root privileges as gnome is doing by clicking in nautilus. I would like to do the equivalent from the command line.
Are there any command lines commands that will allow me to do this (not talking about pmount which is not installed)?Also, is there a way to prevent automounting of just certain devices, but not all? I have a USB with 7 different things on it (a "built-in" CD for some reason for windoz users, the original NTFS, and 5 linux partitions). I really only want one of the linux partitions (an XFS for DVD isos) to automount but not all the others. I would like not to have to disable ALL automounting as in: Code:
I had a corrupted superblock in my RAID boot drive (/dev/md0), which I fixed with fsck in Recovery Mode.However, after rebooting, the same boot-up problem (hanging for hours) persists.When I re-enter Recovery Mode to examine the boot drive, I found its superblock was corrupted again (which I fixed again using fsck).Is there a proper reboot procedure which is gentle on the boot drive, such that it doesn't corrupt it? Or, is something else amiss
I had a corrupted superblock in my RAID boot drive (/dev/md0), which I fixed with fsck in Recovery Mode.
However, after rebooting, the same boot-up problem (hanging for hours) persists. When I re-enter Recovery Mode to examine the boot drive, I found its superblock was corrupted again (which I fixed again using fsck).
Is there a proper reboot procedure which is gentle on the boot drive, such that it doesn't corrupt it? Or, is something else amiss?
when I am pressing the shut down button inside kde I receive this nice black screen with the green status messages indicating what was done successfuly. At the unmounting file systems though I have to wait for a 20-30mins duration to finished. I have two or three network shares but even a timeout would not take more than 1 min to appear.
I'm working on a server and noticed that the to RAID5 setup is showing 4 Raid devices but only 3 Total devices. It's on a fully updated CentOS 5 system that only has three SATA drives, as it can not hold anymore. I've done some researching but am unable to remove the fourth device, which is listed as removed. The full output of `mdadm -D /dev/md2` can be see below. I've never run into this situation before.Anyone have any pointers on how I can reduced the Raid Devices from 4 to 3? I have tried
Upon shut down I have noticed that my system says "Unmounting Weak file system". I have taken steps to check that all software is installed correctly and up to date but I am quite new to Linux and I am still learning. Does warning at shutdown mean that there is a problem with my file system? Is there anything I can do to fix this?
When I installed Wicd, and ran it for the first time, I got an error something like: "Could not connect to Wicd's dbus session- check the Wicd log file for more info". However, later when I restarted my computer, Wicd started, but I can't connect to my network, it shows up as <hidden>, I can connect to linksys, so I know that wireless is working on that computer. I know that there's nothing wrong with my wireless router, because I can connect to my network in this computer.
I've recently installed Puppy Linux on a "second-hand" machine, and I'm trying to get gcc installed so that I can (hopefully) compile some wireless drivers for the USB adapter I'm trying to make work.
I've tried everything I can think of, including following the instructions on the Puppy website. When I click the devx_430.sfs file, it simply fails to mount ("Failed mounting or unmounting."). So I tried getting the gcc and make packages (+dependencies) from the Ubuntu repos, and install those (Puppy has an "undeb" utility). There are actually supposedly two ways of doing that: one is to click on the file in ROX-Filer, and that opens a confirmation dialog to install, so I tried that first (with all the .debs). That seemed to report a successful installation for each package (confirmation dialogs popped up to report installation success), but when I tried typing "gcc" in the terminal, it still couldn't find it ("bash: gcc: command not found").
So then I tried the second way: using "undeb" in the terminal. That again was supposedly successful (no errors), but still "bash: gcc: command not found" and "/usr/bin/gcc: No such file or directory".
So then I tried "file /usr/bin/gcc" and it gives this:
Code: /usr/bin/gcc: broken symbolic link to 'gcc-4.3' And of course, as expected, "find / -name "gcc-4.3" finds nothing.
Where are these files being extracted to, if at all? And I can't just use the package manager, because I don't have internet (this is how I'm trying to get internet). Am I totally screwed?
For 6 months I have used this computer as a ediacenter/seedbox on a decent TV. It crapped out and we got a new one. Hooked it up, had super messed up resolution. Ran some command (really don't remember) that ran you through the setup configuration asking for keyboard layout etc.
Didn't work. Deleted xorg.cong, didn't work. Blank xorg.conf, didn't work. What happens is it shows the Ubuntu name and loading bar, loads, then at 100% it shows 2 of them in purple around the screen. Obviously X isn't loading correctly.