External usbdisk fail to mount at boot time

[Giovanni Bortolozzo]

I don't know if i'm reporting the bug to the right package, anyway I have an external usb disk, and I like to mount it automatically at the boot time.

Seem like that this is mounted too early (or something like this) while if I try to access it just after the boot it is not accessible (and I get an i/o error in console), but if I umount it and mount again, or if I disconnect and reconnect it works without any problem (see the attached dmesg output, at boot time I get strange errors).

Note this disk works without any problem under Debian/sid with a custum 2.6.30 vanilla kernel. I check it under windows with chkdsk /f and i can't find any problem.

ProblemType: Bug
Architecture: i386
Date: Sun Jul 26 20:27:17 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=bcf548d7-27f5-4833-a040-bb768d9f4b82
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 059f:1019 LaCie, Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-4-generic 2.6.31-4.22
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-4-generic root=UUID=6501ccba-6176-47e1-8cec-45fc88a76cb4 ro splash #GRUB_DISABLE_LINUX_UUID=true quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
RelatedPackageVersions: linux-backports-modules-2.6.31-4-generic N/A
SourcePackage: linux
Uname: Linux 2.6.31-4-generic i686
dmi.bios.date: 09/25/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1301
dmi.board.name: P5N-E SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1301:bd09/25/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Jeremy Foshee (jeremyfoshee)]

Hi Giovanni,

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 from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 404976

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/KernelMainlineBuilds . 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. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Giovanni Bortolozzo (giovanni-bortolozzo)]

I just upgrade yesterday to the last beta.

Today when I cold boot the PC all works fine. Yesterday on the reboot after the upgrade, the boot process fail because it can't mount the external disk. In the next days I will make more test and I can give you more information.

Regards.

Giovanni

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]