Installing from USB-Stick causes problems with gnome-volume-manager after install

Bug #157153 reported by Erik Vetters on 2007-10-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Express
Undecided
Unassigned

Bug Description

Explanation:

I had feisty before and wanted to install Gutsy from scratch. I always updated before, never did a fresh install it was easier.
But now I had to to a fresh install of Gutsy because I had a new laptop a Dell D420.

So I did the following I download the gutsy release a converted it to a usb-stick with isotostick.sh found
here http://janimo.blogspot.com/2007/10/live-cd-on-usb-key.html ( I found that on planet.ubuntu.com )

I did this all because I have forgotten my external cd-drive and docking station at work. But wanted to install Gutsy.
The Dell D420 only have an External Drive or a Docking Station called Media-Bay.

The I booted from the USB and installed Gutsy wich caused no problems. Everything worked out of the box. ( thx to the devs )

Later:

I wanted to mount a usb-stick and external harddisk via usb.

I got the following error message:

Can't mount the volume Invalid option the to mount the volume "ERIK"

That was strange, I digged deeper in that problems, syslog said after plugin in the external drive
or disk hardware

Oct 25 13:57:17 siXel kernel: [ 400.312000] usb 1-7: new high speed USB device using ehci_hcd and address 9
Oct 25 13:57:18 siXel kernel: [ 400.444000] usb 1-7: configuration #1 chosen from 1 choice
Oct 25 13:57:18 siXel kernel: [ 400.444000] scsi3 : SCSI emulation for USB Mass Storage devices
Oct 25 13:57:18 siXel kernel: [ 400.444000] usb-storage: device found at 9
Oct 25 13:57:18 siXel kernel: [ 400.444000] usb-storage: waiting for device to settle before scanning
Oct 25 13:57:18 siXel NetworkManager: <debug> [1193313438.097827] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_702_noserial').
Oct 25 13:57:18 siXel NetworkManager: <debug> [1193313438.191861] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_702_noserial_if0').
Oct 25 13:57:18 siXel NetworkManager: <debug> [1193313438.195812] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_702_noserial_usbraw').
Oct 25 13:57:23 siXel kernel: [ 405.444000] usb-storage: device scan complete
Oct 25 13:57:23 siXel kernel: [ 405.648000] scsi 3:0:0:0: Direct-Access ST94011A 0811 PQ: 0 ANSI: 0
Oct 25 13:57:23 siXel kernel: [ 405.652000] sd 3:0:0:0: [sdb] 78140160 512-byte hardware sectors (40008 MB)
Oct 25 13:57:23 siXel kernel: [ 405.652000] sd 3:0:0:0: [sdb] Test WP failed, assume Write Enabled
Oct 25 13:57:23 siXel kernel: [ 405.652000] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Oct 25 13:57:23 siXel kernel: [ 405.656000] sd 3:0:0:0: [sdb] 78140160 512-byte hardware sectors (40008 MB)
Oct 25 13:57:23 siXel kernel: [ 405.656000] sd 3:0:0:0: [sdb] Test WP failed, assume Write Enabled
Oct 25 13:57:23 siXel kernel: [ 405.656000] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Oct 25 13:57:23 siXel kernel: [ 405.656000] sdb: sdb1
Oct 25 13:57:23 siXel kernel: [ 405.676000] sd 3:0:0:0: [sdb] Attached SCSI disk
Oct 25 13:57:23 siXel kernel: [ 405.676000] sd 3:0:0:0: Attached scsi generic sg1 type 0
Oct 25 13:57:23 siXel NetworkManager: <debug> [1193313443.574846] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_702_noserial_if0_scsi_host').
Oct 25 13:57:23 siXel NetworkManager: <debug> [1193313443.577540] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_702_noserial_if0_scsi_host_scsi_device_lun0').
Oct 25 13:57:23 siXel NetworkManager: <debug> [1193313443.579002] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_702_noserial_if0_scsi_host_scsi_device_lun0_scsi_generic').
Oct 25 13:57:23 siXel NetworkManager: <debug> [1193313443.642857] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/storage_serial_ST94011A_USB_TO_IDE_0_0').
Oct 25 13:57:23 siXel NetworkManager: <debug> [1193313443.703857] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_uuid_00B2_3DE2').
Oct 25 13:57:23 siXel kernel: [ 406.260000] UDF-fs: No VRS found
Oct 25 13:57:23 siXel kernel: [ 406.308000] Unable to identify CD-ROM format.

I assumed I had forgotten to install some filesystem types or whatever, but regardless of the
fs-type the volume didn't get mounted always the same error message.

So I digged a little bit deeper ... and found something.

The installer ad the line

/dev/sdb1 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0

to fstab, wich is I think correct .... I removed the line and of course everything
worked fine then. This all was caused because after install if I plug in a device
wich also get connected to /dev/sdb1 then g-v-m tries to mount the with FS-Type
udf and that is of course not correct.

Should there be a workaround for this ? A normal user wouldn't have not found the
error and give up using Ubuntu because he can't plugin external usb drivers.

Just a question, I know this is hard to track down.

Normally you have hd[a,b,c] for cd-drives. But what happens when install via usb-cd-drive ?

Greetings
Erik

Erik Vetters (evetters) wrote :

Syslog installer log

Erik Vetters (evetters) wrote :

partman installer log

Erik Vetters (evetters) wrote :

casper installer log

Shaved Wookie (shavedwookie) wrote :

This bug still blocks automounting usb drives in Intrepid Beta 1. Furthermore, I suspect it's about to affect a *lot* more people with the release of usb-creator ( http://ubuntuforums.org/showthread.php?p=5927513 ).

Does this affect machines *with* a cdrom drive?

Shaved Wookie (shavedwookie) wrote :
Shaved Wookie (shavedwookie) wrote :
Shaved Wookie (shavedwookie) wrote :
Shaved Wookie (shavedwookie) wrote :
Changed in ubuntu-express:
status: New → Confirmed
Shaved Wookie (shavedwookie) wrote :

I don't seem to get this in Jaunty. Unsubscribing.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Patches