I am running OpenSuse 12.2 64. I have a genuine OS X Lion thumb drive but I cannot read the contents.
/var/log/messages shows:
Feb 22 17:06:37 linux-3qfy kernel: 1276.648025] usb 1-7: new high-speed USB device number 5 using ehci_hcd
Feb 22 17:06:37 linux-3qfy kernel: 1276.809104] usb 1-7: New USB device found, idVendor=05ac, idProduct=1502
Feb 22 17:06:37 linux-3qfy kernel: 1276.809109] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 22 17:06:37 linux-3qfy kernel: 1276.809112] usb 1-7: Product: USB DISK
Feb 22 17:06:37 linux-3qfy kernel: 1276.809115] usb 1-7: Manufacturer: APPLE
Feb 22 17:06:37 linux-3qfy kernel: 1276.809117] usb 1-7: SerialNumber: AAHO2UO2SHASED93
Feb 22 17:06:37 linux-3qfy mtp-probe: checking bus 1, device 5: “/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7”
Feb 22 17:06:37 linux-3qfy mtp-probe: bus: 1, device: 5 was not an MTP device
Feb 22 17:06:37 linux-3qfy kernel: 1276.849616] Initializing USB Mass Storage driver…
Feb 22 17:06:37 linux-3qfy kernel: 1276.849763] scsi2 : usb-storage 1-7:1.0
Feb 22 17:06:37 linux-3qfy kernel: 1276.849837] usbcore: registered new interface driver usb-storage
Feb 22 17:06:37 linux-3qfy kernel: 1276.849838] USB Mass Storage support registered.
Feb 22 17:06:37 linux-3qfy dbus-daemon[573]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/scsi_host/host2
Feb 22 17:06:37 linux-3qfy dbus-daemon[573]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/scsi_host/host2
Feb 22 17:06:38 linux-3qfy kernel: 1278.257622] scsi 2:0:0:0: CD-ROM APPLE USB DISK 1100 PQ: 0 ANSI: 2
Feb 22 17:06:38 linux-3qfy kernel: 1278.257685] scsi 2:0:0:0: alua: supports implicit and explicit TPGS
Feb 22 17:06:38 linux-3qfy kernel: 1278.260486] scsi 2:0:0:0: alua: port group 7300 rel port ffffffff
Feb 22 17:06:38 linux-3qfy kernel: 1278.262865] scsi 2:0:0:0: alua: rtpg failed with 8000002
Feb 22 17:06:38 linux-3qfy kernel: 1278.262869] scsi 2:0:0:0: alua: rtpg sense code 05/20/00
Feb 22 17:06:38 linux-3qfy kernel: 1278.262871] scsi 2:0:0:0: alua: not attached
Feb 22 17:06:38 linux-3qfy kernel: 1278.265237] sr1: scsi3-mmc drive: 94x/94x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 22 17:06:38 linux-3qfy kernel: 1278.265380] sr 2:0:0:0: Attached scsi CD-ROM sr1
Feb 22 17:06:38 linux-3qfy kernel: 1278.265471] sr 2:0:0:0: Attached scsi generic sg2 type 5
Feb 22 17:06:39 linux-3qfy dbus-daemon[573]: **** ADDING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sr1
Feb 22 17:06:39 linux-3qfy dbus-daemon[573]: **** UPDATING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sr1
Feb 22 17:06:39 linux-3qfy dbus-daemon[573]: **** ADDED /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sr1
Feb 22 17:06:39 linux-3qfy dbus-daemon[573]: **** EMITTING ADDED for /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sr1
Feb 22 17:06:39 linux-3qfy dbus-daemon[573]: **** CHANGING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sr1
Feb 22 17:06:39 linux-3qfy dbus-daemon[573]: **** UPDATING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sr1
Feb 22 17:06:39 linux-3qfy dbus-daemon[573]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sr1
Feb 22 17:06:39 linux-3qfy dbus-daemon[573]: **** CHANGED /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sr1
I have searched “alua rtpg failed with 8000002” etc on Google but got no useful results.
“Cannot read” is a bit vague. It can mean anything between “I see nothing happen at all” and “I lost my glasses”.
Do you run a desktop? And when yes, which one? <ost desktops will show a popup when a mass storage device is connected. Does this happen?
From your /var/log/message it seems thatthe system recognises it
(BTW, please put computer output like this between CODE tgas, you get them by clocking on the # button in the toolbar abocve the post editor).
What shows
lsusb
)Again, copy/paste this inclusing the prompt, the command, the listing anf the next prompt in one sweep between the CODE tags).
And were ddevice special file created? Maybe that can best be answered by
I am using KDE and it does not offer to mount the drive.
Before plugging in the stick lsusb shows:
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd
Bus 001 Device 004: ID 0603:00f2 Novatek Microelectronics Corp.
After plugging in the stick lsusb shows:
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 007: ID 05ac:1502 Apple, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd
Bus 001 Device 004: ID 0603:00f2 Novatek Microelectronics Corp.
I obviously found code tags but how do you get the original command in the output?. lsusb > output.txt captures the output but not the original command.
No need to redirect the output to a file. These days in GUI desktops there is the copy/paste function of the mouse. In your terminal emulation you click the left button down while the cursor is at the beginning of the text. Then, while holding that button down, you move the mouse to the end of the text to be copied. A colour change will echo this to you. Then you let loose the mouse button. You now have the selected text in a buffer. You now click in between the CODE tags (that you created earlier) with the left button to denote the place where you want to paste. Do not move the mouse. When you now click the middle button, the buffered/delected text will be put where you want it.
How long do you already use GUI interfaces without knowing how to coy/paste?
And that is the (link to the) block device special file created for it. It apperently sees it as a storage device, but the fact that it uses /dev/sr1 shows that it is more like a CD-ROM or DVD device then real mass storage. I have no idea what an Apple OSX Lion Thumb Drive is supposed to be (I hope you have).
Let us see if it is mounted with
mount | grep sr1
If that gives nothing then try to mount yourself:
su -c 'mount /dev/sr1 /mnt'
When no error messages, look if you can see things in /mnt.
I am trying to install OSX Lion on virtualbox, as I no longer have a mac, and I do not believe in using a pirate copy so I am trying to use my genuine Apple OSX Lion thumb drive containing, presumably, an image of the OS.
It is bootable so from what we have done so far, it looks like it is emulating a cdrom.
linux-3qfy:~ # mount | grep sr1
linux-3qfy:~ #
linux-3qfy:~ # mount /dev/sr1 /mnt/macdrive
mount: /dev/sr1 is write-protected, mounting read-only
mount: unknown filesystem type '(null)'
linux-3qfy:~ #
After browsing I also tried
linux-3qfy:~ # mount -t hfsplus /dev/sr1 /mnt/macdrive
mount: /dev/sr1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sr1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
linux-3qfy:~ #
I think you also came to the conclusion that the file system type that is on there can not be determined by the kernel. And you helping by suggesting it is hfsplus does not work.
As I do not know very much (even less then that) about MAC, I can not suggest which type of OS is on there.
And thus I can not tell you also if, when you find out which type it is, this is supported by Linux.
All I can suggest is try to find out what it is.
A Linux installation CD/DVD (like the openSUSE ones) have an iso9660 file system on them. But when I insert one in my system, KDE comes up with notifier popup and I can then use it and it is mounted. Thus is09660 is no problem and thus most probably not what you have there.