DebuggingRemovableDevices
|
Size: 2862
Comment: making terminal commands slightly clearer with indents
|
Size: 3682
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| | <<Include(Debugging/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>|| |
| Line 6: | Line 7: |
= Things to try first = Run fsck (dosfsck?) on the disk to make sure it does not have any configuration errors. Sometimes a misconfigured drive will work fine in Windows but not in Linux. In Hardy or later, remove the "usefree" option with gconf-editor (Applications --> System Tools --> Configuration Editor). This can prevent drives from auto-mounting.[[https://bugs.launchpad.net/ubuntu/+source/gnome-mount/+bug/151025]] The "usefree" option should be removed from system --> storage --> default_options --> vfat --> mount_options Some have found that reinstalling hal helps with automount problems.[[http://ubuntuforums.org/showthread.php?t=571768]] |
|
| Line 12: | Line 21: |
| 0. stop gvm [[BR]] | 0. stop gvm <<BR>> |
| Line 14: | Line 23: |
| 0. start gvm and capture output [[BR]] | 0. start gvm and capture output <<BR>> |
| Line 16: | Line 25: |
| 0. and in another terminal, start udevmonitor and capture output [[BR]] `sudo udevmonitor -e | tee udev.log` |
0. if that doesn't work, try <<BR>> `/usr/lib/gnome-volume-manager/gnome-volume-manager -n 2>&1 | tee gvm.log` 0. and in another terminal, start udevadm in monitor mode and capture output <<BR>> `sudo udevadm monitor -e | tee udev.log` |
| Line 20: | Line 31: |
| 0. Press Control-C to stop the foreground gnome-volume-manager 0. press Control-C to stop the udevmonitor 0. capture lshal, dmesg and ls the attached volumes [[BR]] `lshal > lshal.txt` [[BR]] `dmesg > dmesg.txt` [[BR]] |
0. press Control-C in the first terminal to stop the foreground gnome-volume-manager 0. press Control-C in the second terminal to stop the udevmonitor 0. capture lshal, dmesg and ls the attached volumes <<BR>> `lshal > lshal.txt` <<BR>> `dmesg > dmesg.txt` <<BR>> |
| Line 27: | Line 38: |
| 0. Press Alt-F2 and type `gnome-volume-manager` to get your background g-v-m back (or just log out and back in again) | 0. press Alt-F2 and type `gnome-volume-manager` to get your background g-v-m back (or just log out and back in again) |
| Line 36: | Line 47: |
| 0. stop hald [[BR]] | 0. stop hald <<BR>> |
| Line 38: | Line 49: |
| 0. start hald while capturing its output [[BR]] | 0. start hald while capturing its output <<BR>> |
| Line 44: | Line 55: |
| 0. Restore the background hal: [[BR]] `sudo /etc/init.d/dbus-1 restart` (in Warty and Hoary)[[BR]] OR [[BR]] |
0. restore the background hal: <<BR>> `sudo /etc/init.d/dbus-1 restart` (in Warty and Hoary)<<BR>> OR <<BR>> |
| Line 48: | Line 59: |
| 0. Restart your desktop session | 0. restart your desktop session |
| Line 69: | Line 80: |
| ------ '''Also see:''' * DebuggingProcedures |
|
| Line 76: | Line 81: |
| CategoryBugSquad | CategoryBugSquad CategoryDebugging |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Introduction
Help on debugging removable device issues.
Things to try first
Run fsck (dosfsck?) on the disk to make sure it does not have any configuration errors. Sometimes a misconfigured drive will work fine in Windows but not in Linux.
In Hardy or later, remove the "usefree" option with gconf-editor (Applications --> System Tools --> Configuration Editor). This can prevent drives from auto-mounting.https://bugs.launchpad.net/ubuntu/+source/gnome-mount/+bug/151025 The "usefree" option should be removed from system --> storage --> default_options --> vfat --> mount_options
Some have found that reinstalling hal helps with automount problems.http://ubuntuforums.org/showthread.php?t=571768
How to report
When reporting a problem with removable devices, such as USB storage devices ("keys", hard drives, card readers, music players, digital cameras, etc.), please do the following steps:
- disconnect the device
stop gvm
killall gnome-volume-manager
start gvm and capture output
gnome-volume-manager -n 2>&1 | tee gvm.log
if that doesn't work, try
/usr/lib/gnome-volume-manager/gnome-volume-manager -n 2>&1 | tee gvm.log
and in another terminal, start udevadm in monitor mode and capture output
sudo udevadm monitor -e | tee udev.log
- connect the device
- wait a few seconds
- press Control-C in the first terminal to stop the foreground gnome-volume-manager
- press Control-C in the second terminal to stop the udevmonitor
capture lshal, dmesg and ls the attached volumes
lshal > lshal.txt
dmesg > dmesg.txt
ls -l /dev/sd* > devices.txt
attach gvm.log, lshal.txt, devices.txt, dmesg.txt and udev.log (dapper only) to the bug report
press Alt-F2 and type gnome-volume-manager to get your background g-v-m back (or just log out and back in again)
paste the output of id into the bug report
paste the output of id hal into the bug report
paste the output of id haldaemon into the bug report
paste the output of uname -a into the bug report
In easy cases this is everything that is needed. However, you might be asked for a "hal debug output"; please do the following steps to get it:
- disconnect the device
stop hald
sudo killall hald
start hald while capturing its output
sudo hald --daemon=no --verbose=yes 2>&1 | tee hal.log
- wait until the flood of messages settled
- connect the device
- wait again until no more messages appear
- press Control-C to stop the foreground hal
restore the background hal:
sudo /etc/init.d/dbus-1 restart (in Warty and Hoary)
OR
sudo /etc/dbus-1/event.d/20hal start (in Breezy, Dapper, Edgy and Feisty)
- attach hal.log to the bug report
- restart your desktop session
Debugging procedure
TBD.
Known bugs
Description of known issues, how to recognise them and stock responses/actions.
Open
Bug# |
Description |
Action |
TBD. |
TBD. |
TBD. |
Closed
Bug# |
Description |
Action |
TBD. |
TBD. |
TBD. |
Non-bugs
TBD.
DebuggingRemovableDevices (last edited 2011-01-07 14:06:15 by 67-42-160-182)