DebuggingRemovableDevices
|
Size: 1343
Comment: updated hal call for breezy
|
Size: 2896
Comment: update for hardy and beyond
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = DebuggingRemovableDevices = | <<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>>|| = 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 = How to report = |
| Line 6: | Line 19: |
| 0. `killall gnome-volume-manager` 0. `gnome-volume-manager 2>&1 | tee gvm.log` |
0. in a terminal, start udevadm in monitor mode and capture output <<BR>> `sudo udevadm monitor -e | tee udev.log` |
| Line 9: | Line 22: |
| 0. wait a few seconds 0. Press Control-C to stop the foreground gnome-volume-manager 0. `lshal > lshal.txt` 0. `dmesg > dmesg.txt` 0. attach `gvm.log`, `lshal.txt`, and `dmesg.txt` to the bug report 0. restart your Gnome session to get a proper background g-v-m back 0. paste the output of `id` into the bug report |
0. open a second Terminal and capture lshal, dmesg and ls the attached volumes <<BR>> `lshal > lshal.txt` <<BR>> `dmesg > dmesg.txt` <<BR>> `ls -l /dev/sd* > devices.txt` 0. Press Control-C in the first terminal with the "udevadm". 0. attach `lshal.txt`, `devices.txt`, `dmesg.txt` and `udev.log` to the bug report 0. paste the output of `ck-list-sessions` into the bug report 0. paste the output of `id haldaemon` into the bug report 0. paste the output of `uname -a` into the bug report |
| Line 20: | Line 35: |
| 0. `sudo killall hald` 0. In Warty and Hoary: `sudo hald --drop-privileges --daemon=no --verbose=yes 2>&1 | tee hal.log` In Breezy: |
0. stop hald <<BR>> `sudo killall hald` 0. start hald while capturing its output <<BR>> |
| Line 27: | Line 41: |
| 0. wait again until no messages appear any more | 0. wait again until no more messages appear |
| Line 29: | Line 43: |
| 0. `sudo /etc/init.d/dbus-1 restart` to properly restore the background hal | 0. restore the background hal: <<BR>> `sudo /etc/init.d/hal restart` |
| Line 31: | Line 46: |
| 0. restart your desktop session = Debugging procedure = TBD. = Known bugs = Description of known issues, how to recognise them and stock responses/actions. '''Open''' ||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' || || TBD. || TBD. || TBD. || '''Closed''' ||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' || || TBD. || TBD. || TBD. || = Non-bugs = TBD. ---- 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
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
in a terminal, start udevadm in monitor mode and capture output
sudo udevadm monitor -e | tee udev.log
- connect the device
open a second Terminal and capture lshal, dmesg and ls the attached volumes
lshal > lshal.txt
dmesg > dmesg.txt
ls -l /dev/sd* > devices.txt
- Press Control-C in the first terminal with the "udevadm".
attach lshal.txt, devices.txt, dmesg.txt and udev.log to the bug report
paste the output of ck-list-sessions 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/hal restart
- 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)