[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Mounting an iPod via USB



Sergio Cuéllar Valdés said:
>
> 1. connect the ipod and use the dmesg command to see if it was
> detected. You should see somthing like:
>
> usb 3-5: new high speed USB device using ehci_hcd and address 2
> Initializing USB Mass Storage driver...
> ....
> usb-storage: waiting for device to settle before scanning
>   Vendor: Apple     Model: iPod              Rev: 1.62
>   Type:   Direct-Access                      ANSI SCSI revision: 00
> usb-storage: device scan complete
> SCSI device sda: 7999488 512-byte hdwr sectors (4096 MB)
> sda: assuming Write Enabled
> sda: assuming drive cache: write through
> SCSI device sda: 7999488 512-byte hdwr sectors (4096 MB)
> sda: assuming Write Enabled
> sda: assuming drive cache: write through
>  /dev/scsi/host0/bus0/target0/lun0: p1 p2
> Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0

I got something like that...
Here's the relevant information that dmesg outputs about the ipod, but it
doesn't seem to be doing anything with it.

Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi3 : SCSI emulation for USB Mass Storage devices
  Vendor: Apple     Model: iPod              Rev: 1.62
  Type:   Direct-Access                      ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
usb.c: USB disconnect on device 00:10.4-1 address 2
hub.c: new USB device 00:10.4-1, assigned address 3
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
usb.c: USB disconnect on device 00:10.4-1 address 3
hub.c: new USB device 00:10.4-1, assigned address 4
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4
usb.c: USB disconnect on device 00:10.4-1 address 4
hub.c: new USB device 00:10.4-1, assigned address 5
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 5
usb.c: USB disconnect on device 00:10.4-1 address 5
hub.c: new USB device 00:10.4-1, assigned address 6
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 6
usb.c: USB disconnect on device 00:10.4-1 address 6
hub.c: new USB device 00:10.4-1, assigned address 7
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 7
usb.c: USB disconnect on device 00:10.4-1 address 7
hub.c: new USB device 00:10.4-2, assigned address 8
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 8

What's the deal with all these warnings?  Also, any ideas why it would
connect/disconnect like that over and over? Should I restore it to the
factory settings and attempt it from scratch? (I've got the restore tool
installed on my laptop that dual boots with windows)

> 2. Create a mount point for the ipod.
>     # mkdir /media/ipod
> 3 Edit /etc/fstab and add:
> /dev/sda2       /media/ipod     vfat    user,noauto,rw  0       0
>
> No you should be able to mount your ipod with: $ mount /media/ipod

It was recognized as /dev/sda2 and I was able to mount it after creating the
mountpoint.

All of the files are owned by root and I can't write to the thing though. 
When I make changes to my playlist and try and upload them to the iPod I get
an error telling me I can't write to the itunesdb file.

> To get rid of the ipod's message that says to not disconnect the ipod,
> like root:
> # eject /dev/sda2

# eject /dev/sda2
umount: /media/ipod: device is busy
umount: /media/ipod: device is busy
eject: unmount of `/dev/sda2' failed

I'm unable to unmount the device with either that eject command or the umount
command.  Any ideas on what would cause it to resist unmounting?

I issued "umount /media/ipod -l" for the moment to see if it'll eventually
stop being "busy" and unmount itself while I sleep.  We'll see how it goes in
the morning, as of now though it's still flashing "do not disconnect" on the
screen.

-- 
- Josh
www.omg-stfu.com



Reply to: