HITACHI external USB disk won't automount always
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
I have always connected through a USB port, a HITACHI external hard drive. But it won't always automount, after every boot. Technical details and command output is automatically provided bellow, by ubuntu-bug.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-
NonfreeKernelMo
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on Jul 6 2010 for kernel 2.6.32-
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfdffc000 irq 26'
Mixer name : 'Realtek ALC259'
Components : 'HDA:10ec0269,
Controls : 13
Simple ctrls : 9
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfddfc000 irq 16'
Mixer name : 'Nvidia GT220 HDMI'
Components : 'HDA:10de000a,
Controls : 16
Simple ctrls : 4
Card2.Amixer.info:
Card hw:2 'Camera'/'Vimicro Corp. Venus USB2.0 Camera at usb-0000:00:1d.7-4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB0ac8:3420'
Controls : 2
Simple ctrls : 1
Card2.Amixer.
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 48
Mono: Capture 0 [0%] [-27.00dB] [on]
Date: Mon Aug 30 14:26:05 2010
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=/dev/sda1
HotplugNewDevices:
HotplugNewMounts:
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: Dell Inc. OptiPlex 380
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageV
RfKill:
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
dmi.bios.date: 03/11/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0HN7XN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: OptiPlex 380
dmi.sys.vendor: Dell Inc.
affects: | ubuntu → linux (Ubuntu) |
tags: | added: acpi-table-checksum |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Aristotelis Mikropoulos, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command in the development release from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux <replace- with-bug- number>
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. As well, please comment on which kernel version specifically you tested.
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel- unable- to-test- upstream' , and comment as to why specifically you were unable to test it.
Please let us know your results. Thanks in advance.