DebuggingRemovableDevices

Differences between revisions 32 and 33
⇤ ← Revision 32 as of 2008-11-23 07:31:16 →
Size: 3682
Editor: c-24-6-152-142
Comment:
← Revision 33 as of 2009-01-28 09:14:47 → ⇥
Size: 2896
Editor: p579DE607
Comment: update for hardy and beyond
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
Some have found that reinstalling hal helps with automount problems.[[http://ubuntuforums.org/showthread.php?t=571768]]
Line 21: Line 19:
 0. stop gvm <<BR>>
  `killall gnome-volume-manager`
 0. start gvm and capture output <<BR>>
  `gnome-volume-manager -n 2>&1 | tee gvm.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>>		  0. in a terminal, start udevadm in monitor mode and capture output <<BR>>
Line 30: Line 22:
 0. wait a few seconds
 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>>		  0. open a second Terminal and capture lshal, dmesg and ls the attached volumes <<BR>>
Line 37: Line 26:
 0. attach `gvm.log`, `lshal.txt`, `devices.txt`, `dmesg.txt` and `udev.log` (dapper only) to the bug report
 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. paste the output of `id` into the bug report
 0. paste the output of `id hal` into the bug report		  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
Line 56: Line 44:
  `sudo /etc/init.d/dbus-1 restart` (in Warty and Hoary)<<BR>> OR <<BR>>
  `sudo /etc/dbus-1/event.d/20hal start` (in Breezy, Dapper, Edgy and Feisty)		   `sudo /etc/init.d/hal restart`

Debugging Central

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:

  1. disconnect the device

  2. in a terminal, start udevadm in monitor mode and capture output

    • sudo udevadm monitor -e | tee udev.log

  3. connect the device

  4. 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

  5. Press Control-C in the first terminal with the "udevadm".

  6. attach lshal.txt, devices.txt, dmesg.txt and udev.log to the bug report

  7. paste the output of ck-list-sessions into the bug report

  8. paste the output of id haldaemon into the bug report

  9. 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:

  1. disconnect the device

  2. stop hald

    • sudo killall hald

  3. start hald while capturing its output

    • sudo hald --daemon=no --verbose=yes 2>&1 | tee hal.log

  4. wait until the flood of messages settled
  5. connect the device
  6. wait again until no more messages appear
  7. press Control-C to stop the foreground hal

  8. restore the background hal:

    • sudo /etc/init.d/hal restart

  9. attach hal.log to the bug report
  10. 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.

CategoryBugSquad CategoryDebugging

DebuggingRemovableDevices (last edited 2011-01-07 14:06:15 by 67-42-160-182)