> If the disk is connected via Firewire vold can not mount the
> disk nor can I mount it manually after stopping vold
IIRC, a manual mount might work after stopping vold, *and*
after hot removing + hot plugging the firewire device.
(You may also have to power cycle the firewire device)
> In my understanding Firewire is as simple as USB -
> just connect the disk with the Firewire cable and it should work. Or am I
> missing something here?
Nope. That's the way it is supposed to work.
> Aug 8 18:55:45 unknown usba: [ID 349649 kern.info] Prolific Technology
> Inc. ATAPI-6 Bridge Controller 1A03
Do you know what kind of chipset is used in this firewire external enclosure?
Is it perhaps a "Prolific PL3507" chipset?
> Aug 8 18:57:44 unknown Error for Command: read Error Level: Retryable
> Aug 8 18:57:44 unknown scsi: [ID 107833 kern.notice] Requested Block: 0 Error
> Block: 0
> Aug 8 18:57:44 unknown scsi: [ID 107833 kern.notice] Vendor: SAMSUNG Serial
> Number: {5
> Aug 8 18:57:44 unknown scsi: [ID 107833 kern.notice] Sense Key: Media_Error
> Aug 8 18:57:44 unknown scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered
> read error), ASCQ: 0x0, FRU: 0x0
Hmm, IIRC my Firewire device with PL3507 chipset shows exactly the same
media error when vold tries to automatically mount the device.
My current theory is that it's a Prolific PL3507 firmware bug.
Prolific has some firmware updates...
http://www.prolific.com.tw/eng/downloads.asp?ID=44
A firmware update has helped with another issue (MODE SENSE hanging / timeout),
but it didn't fix the "Media_Error" issue.
This message posted from opensolaris.org
