| View previous topic :: View next topic |
| Author |
Message |
Wizumwalt
Guru
Joined: 20 Aug 2006
Posts: 547
|
 Posted: Sat Dec 27, 2008 4:47 pm Post subject: mounting HFS+ |
 |
|
I was asked to move this into PPC cause some of you guys might have better insights as to what's going on here ... I've been trying to mount my HD from a mac (PPC) to my gentoo box to pull some data off before I wipe it clean and reinstall. It currently won't boot and has no disk space available (which may have caused my problems). I have HFS+ included in my kernel.
When I boot my mac into firewire mode, this is what is shown in /var/log/messages ...
| Code: |
Dec 27 10:36:10 Tux ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
Dec 27 10:36:10 Tux ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Dec 27 10:36:25 Tux ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[000393fffe98c980]
Dec 27 10:36:26 Tux ieee1394: unsolicited response packet received - no tlabel match
Dec 27 10:36:31 Tux scsi5 : SBP-2 IEEE-1394
Dec 27 10:36:32 Tux ieee1394: sbp2: Logged into SBP-2 device
Dec 27 10:36:32 Tux ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Dec 27 10:36:32 Tux scsi 5:0:0:0: Direct-Access-RBC AAPL FireWire Target 0000 PQ: 0 ANSI: 3
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] 78242976 512-byte hardware sectors (40060 MB)
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] Write Protect is off
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] Mode Sense: 10 00 00 00
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] 78242976 512-byte hardware sectors (40060 MB)
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] Write Protect is off
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] Mode Sense: 10 00 00 00
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Dec 27 10:36:32 Tux sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11
Dec 27 10:36:32 Tux sd 5:0:0:0: [sdb] Attached SCSI disk
Dec 27 10:36:32 Tux sd 5:0:0:0: Attached scsi generic sg2 type 14
Dec 27 10:37:33 Tux ieee1394: sbp2: aborting sbp2 command
Dec 27 10:37:33 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 27 10:38:37 Tux ieee1394: sbp2: aborting sbp2 command
Dec 27 10:38:37 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 27 10:38:42 Tux INFO: task vol_id:5641 blocked for more than 120 seconds.
Dec 27 10:38:42 Tux "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 27 10:38:42 Tux vol_id D ffffffff8059d3a0 0 5641 5640
Dec 27 10:38:42 Tux ffff81006d641c58 0000000000000086 0000000000000000 ffffffff8029f587
Dec 27 10:38:42 Tux ffff81006d5b4090 ffffffff80713480 ffff81006d5b42c8 000000006f8d83a0
Dec 27 10:38:42 Tux 00000000ffffffff ffff81006d463000 0000000000000000 0000000000000000
Dec 27 10:38:42 Tux Call Trace:
Dec 27 10:38:42 Tux [<ffffffff8029f587>] block_read_full_page+0x248/0x265
Dec 27 10:38:42 Tux [<ffffffff80257f1d>] sync_page_killable+0x0/0x30
Dec 27 10:38:42 Tux [<ffffffff805811b2>] io_schedule+0x28/0x34
Dec 27 10:38:42 Tux [<ffffffff80256775>] sync_page+0x3c/0x41
Dec 27 10:38:42 Tux [<ffffffff80257f26>] sync_page_killable+0x9/0x30
Dec 27 10:38:42 Tux [<ffffffff805812ef>] __wait_on_bit_lock+0x36/0x66
Dec 27 10:38:42 Tux [<ffffffff802566c1>] __lock_page_killable+0x5e/0x64
Dec 27 10:38:42 Tux [<ffffffff8023df33>] wake_bit_function+0x0/0x23
Dec 27 10:38:42 Tux [<ffffffff8025825f>] generic_file_aio_read+0x312/0x4c6
Dec 27 10:38:42 Tux [<ffffffff80261e5b>] zone_statistics+0x3a/0x8e
Dec 27 10:38:42 Tux [<ffffffff8027e55f>] do_sync_read+0xc9/0x10c
Dec 27 10:38:42 Tux [<ffffffff8023df05>] autoremove_wake_function+0x0/0x2e
Dec 27 10:38:42 Tux [<ffffffff80268f65>] vma_merge+0x147/0x1f4
Dec 27 10:38:42 Tux [<ffffffff8027ecc6>] vfs_read+0xaa/0x132
Dec 27 10:38:42 Tux [<ffffffff8027f062>] sys_read+0x45/0x6e
Dec 27 10:38:42 Tux [<ffffffff8020b00b>] system_call_after_swapgs+0x7b/0x80
Dec 27 10:38:42 Tux
Dec 27 10:38:42 Tux INFO: task vol_id:5643 blocked for more than 120 seconds.
Dec 27 10:38:42 Tux "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 27 10:38:42 Tux vol_id D ffffffff8059d3a0 0 5643 5642
Dec 27 10:38:42 Tux ffff81006d667c58 0000000000000086 0000000000000000 ffffffff8029f587
Dec 27 10:38:42 Tux ffff81006d6631b0 ffff81007fbecc10 ffff81006d6633e8 000000026f8d8198
Dec 27 10:38:42 Tux 00000000ffffffff ffff81006d6a5000 0000000000000000 0000000000000000
Dec 27 10:38:42 Tux Call Trace:
Dec 27 10:38:42 Tux [<ffffffff8029f587>] block_read_full_page+0x248/0x265
Dec 27 10:38:42 Tux [<ffffffff80257f1d>] sync_page_killable+0x0/0x30
Dec 27 10:38:42 Tux [<ffffffff805811b2>] io_schedule+0x28/0x34
Dec 27 10:38:42 Tux [<ffffffff80256775>] sync_page+0x3c/0x41
Dec 27 10:38:42 Tux [<ffffffff80257f26>] sync_page_killable+0x9/0x30
Dec 27 10:38:42 Tux [<ffffffff805812ef>] __wait_on_bit_lock+0x36/0x66
Dec 27 10:38:42 Tux [<ffffffff802566c1>] __lock_page_killable+0x5e/0x64
Dec 27 10:38:42 Tux [<ffffffff8023df33>] wake_bit_function+0x0/0x23
Dec 27 10:38:42 Tux [<ffffffff8025825f>] generic_file_aio_read+0x312/0x4c6
Dec 27 10:38:42 Tux [<ffffffff80261e5b>] zone_statistics+0x3a/0x8e
Dec 27 10:38:42 Tux [<ffffffff8027e55f>] do_sync_read+0xc9/0x10c
Dec 27 10:38:42 Tux [<ffffffff8023df05>] autoremove_wake_function+0x0/0x2e
Dec 27 10:38:42 Tux [<ffffffff8027ecc6>] vfs_read+0xaa/0x132
Dec 27 10:38:42 Tux [<ffffffff8027f062>] sys_read+0x45/0x6e
Dec 27 10:38:42 Tux [<ffffffff8020b00b>] system_call_after_swapgs+0x7b/0x80
Dec 27 10:38:42 Tux
|
Here's what I use to try and mount the disk, and after a few minutes the results ...
| Code: |
$ mount -t hfsplus -o ro /dev/sdb1 /mnt/mac
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
|
And more of this shows up in /var/log/messages ...
| Code: |
Dec 27 10:40:51 Tux INFO: task vol_id:5643 blocked for more than 120 seconds.
Dec 27 10:40:51 Tux "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 27 10:40:51 Tux vol_id D ffffffff8059d3a0 0 5643 1
Dec 27 10:40:51 Tux ffff81006d667c58 0000000000000086 0000000000000000 ffffffff8029f587
Dec 27 10:40:51 Tux ffff81006d6631b0 ffff81007fbecc10 ffff81006d6633e8 000000026f8d8198
Dec 27 10:40:51 Tux 00000000ffffffff ffff81006d6a5000 0000000000000000 0000000000000000
Dec 27 10:40:51 Tux Call Trace:
Dec 27 10:40:51 Tux [<ffffffff8029f587>] block_read_full_page+0x248/0x265
Dec 27 10:40:51 Tux [<ffffffff80257f1d>] sync_page_killable+0x0/0x30
Dec 27 10:40:51 Tux [<ffffffff805811b2>] io_schedule+0x28/0x34
Dec 27 10:40:51 Tux [<ffffffff80256775>] sync_page+0x3c/0x41
Dec 27 10:40:51 Tux [<ffffffff80257f26>] sync_page_killable+0x9/0x30
Dec 27 10:40:51 Tux [<ffffffff805812ef>] __wait_on_bit_lock+0x36/0x66
Dec 27 10:40:51 Tux [<ffffffff802566c1>] __lock_page_killable+0x5e/0x64
Dec 27 10:40:51 Tux [<ffffffff8023df33>] wake_bit_function+0x0/0x23
Dec 27 10:40:51 Tux [<ffffffff8025825f>] generic_file_aio_read+0x312/0x4c6
Dec 27 10:40:51 Tux [<ffffffff80261e5b>] zone_statistics+0x3a/0x8e
Dec 27 10:40:51 Tux [<ffffffff8027e55f>] do_sync_read+0xc9/0x10c
Dec 27 10:40:51 Tux [<ffffffff8023df05>] autoremove_wake_function+0x0/0x2e
Dec 27 10:40:51 Tux [<ffffffff8027ecc6>] vfs_read+0xaa/0x132
Dec 27 10:40:51 Tux [<ffffffff8027f062>] sys_read+0x45/0x6e
Dec 27 10:40:51 Tux [<ffffffff8020b00b>] system_call_after_swapgs+0x7b/0x80
Dec 27 10:40:51 Tux
Dec 27 10:41:38 Tux ieee1394: sbp2: aborting sbp2 command
Dec 27 10:41:38 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 27 10:42:12 Tux INFO: task mount:5647 blocked for more than 120 seconds.
Dec 27 10:42:12 Tux "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 27 10:42:12 Tux mount D ffffffff8059d3a0 0 5647 5588
Dec 27 10:42:12 Tux ffff81006d4f5938 0000000000000086 0000000000000000 ffffffff803617eb
Dec 27 10:42:12 Tux ffff81007e4c0090 ffff81007fbecc10 ffff81007e4c02c8 000000028036182e
Dec 27 10:42:12 Tux 00000000ffffffff ffff81007e832200 0000000000000000 0000000000000000
Dec 27 10:42:12 Tux Call Trace:
Dec 27 10:42:12 Tux [<ffffffff803617eb>] cfq_add_rq_rb+0x6f/0x81
Dec 27 10:42:12 Tux [<ffffffff8029d6b6>] sync_buffer+0x0/0x3f
Dec 27 10:42:12 Tux [<ffffffff805811b2>] io_schedule+0x28/0x34
Dec 27 10:42:12 Tux [<ffffffff8029d6f1>] sync_buffer+0x3b/0x3f
Dec 27 10:42:12 Tux [<ffffffff805813d7>] __wait_on_bit+0x40/0x6e
Dec 27 10:42:12 Tux [<ffffffff8029d6b6>] sync_buffer+0x0/0x3f
Dec 27 10:42:12 Tux [<ffffffff80581471>] out_of_line_wait_on_bit+0x6c/0x78
Dec 27 10:42:12 Tux [<ffffffff8023df33>] wake_bit_function+0x0/0x23
Dec 27 10:42:12 Tux [<ffffffff8029ee89>] __bread+0x68/0x7c
Dec 27 10:42:12 Tux [<ffffffffa0833b54>] :hfsplus:hfsplus_read_wrapper+0xf8/0x384
Dec 27 10:42:12 Tux [<ffffffffa082c797>] :hfsplus:hfsplus_fill_super+0xa8/0x4b1
Dec 27 10:42:12 Tux [<ffffffff8036904a>] vsnprintf+0x575/0x5be
Dec 27 10:42:12 Tux [<ffffffff80364e64>] kobject_get+0x12/0x17
Dec 27 10:42:12 Tux [<ffffffff802a1c1e>] do_open+0x223/0x2b1
Dec 27 10:42:12 Tux [<ffffffff802a1d1c>] __blkdev_get+0x70/0x82
Dec 27 10:42:12 Tux [<ffffffffa082c6ef>] :hfsplus:hfsplus_fill_super+0x0/0x4b1
Dec 27 10:42:12 Tux [<ffffffff8036919d>] snprintf+0x44/0x4c
Dec 27 10:42:12 Tux [<ffffffff805821ff>] __down_write_nested+0x12/0x93
Dec 27 10:42:12 Tux [<ffffffff80291604>] get_filesystem+0x12/0x32
Dec 27 10:42:12 Tux [<ffffffff8027fdd1>] sget+0x356/0x365
Dec 27 10:42:12 Tux [<ffffffff8027f83c>] set_bdev_super+0x0/0xf
Dec 27 10:42:12 Tux [<ffffffffa082c6ef>] :hfsplus:hfsplus_fill_super+0x0/0x4b1
Dec 27 10:42:12 Tux [<ffffffff80280754>] get_sb_bdev+0xf8/0x145
Dec 27 10:42:12 Tux [<ffffffff802801c0>] vfs_kern_mount+0x4f/0x96
Dec 27 10:42:12 Tux [<ffffffff8028025a>] do_kern_mount+0x43/0xdc
Dec 27 10:42:12 Tux [<ffffffff80294267>] do_new_mount+0x5b/0x95
Dec 27 10:42:12 Tux [<ffffffff8029442a>] do_mount+0x189/0x1b6
Dec 27 10:42:12 Tux [<ffffffff8025be43>] __alloc_pages_internal+0xe2/0x3bd
Dec 27 10:42:12 Tux [<ffffffff802944e1>] sys_mount+0x8a/0xd9
Dec 27 10:42:12 Tux [<ffffffff8020b00b>] system_call_after_swapgs+0x7b/0x80
Dec 27 10:42:12 Tux
Dec 27 10:42:39 Tux ieee1394: sbp2: aborting sbp2 command
Dec 27 10:42:39 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 27 10:42:39 Tux sd 5:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK,SUGGEST_OK
Dec 27 10:42:39 Tux end_request: I/O error, dev sdb, sector 269952
Dec 27 10:42:39 Tux __ratelimit: 14 messages suppressed
Dec 27 10:42:39 Tux Buffer I/O error on device sdb10, logical block 748
Dec 27 10:42:39 Tux attempt to access beyond end of device
Dec 27 10:42:39 Tux sdb1: rw=0, want=263971, limit=63
Dec 27 10:42:39 Tux hfs: unable to find HFS+ superblock
Dec 27 10:43:39 Tux ieee1394: sbp2: aborting sbp2 command
Dec 27 10:43:39 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
|
Anyone have any ideas about what I could try?
Also ... I just found this in my dmesg ...
| Code: |
ieee1394: sbp2: Error logging into SBP-2 device - timed out
ieee1394: sbp2: Failed to reconnect to sbp2 device!
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[000393fffe98c980]
scsi 4:0:0:0: [sdb] Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK,SUGGEST_O
K
end_request: I/O error, dev sdb, sector 269952
Buffer I/O error on device sdb10, logical block 748
Buffer I/O error on device sdb10, logical block 748
Buffer I/O error on device sdb10, logical block 0
Buffer I/O error on device sdb10, logical block 1
Buffer I/O error on device sdb10, logical block 2
Buffer I/O error on device sdb10, logical block 3
Buffer I/O error on device sdb10, logical block 4
Buffer I/O error on device sdb10, logical block 5
Buffer I/O error on device sdb10, logical block 6
Buffer I/O error on device sdb10, logical block 7
|
In my /dev I only have sdb1-9 for this device.
And if I try some hfsutils ...
| Code: |
# hmount /dev/sdb
/dev/sdb: contains 1 HFS partition
Volume name is "Haley" (locked)
Volume was created on Fri Jun 2 21:31:25 2006
Volume was last modified on Fri Jun 2 21:31:25 2006
Volume has 0 bytes free
|
|
|
| Back to top |
|
 |
notmynormalself
n00b
Joined: 19 Jun 2008
Posts: 15
Location: Oregon
|
| Posted: Sat Dec 27, 2008 10:55 pm Post subject: Re: mounting HFS+ |
|
|
| Wizumwalt wrote: |
In my /dev I only have sdb1-9 for this device. |
Did you try to mount 9? |
|
| Back to top |
|
|
JoseJX
Retired Dev
Joined: 28 Apr 2002
Posts: 2774
|
| Posted: Sun Dec 28, 2008 2:02 am Post subject: |
|
|
A few things:
1. Do you have Apple partition support in your kernel?
2. HFSutils is only for HFS filesystems, not HFS+.
3. It appears that the disk is having problems reading data, I get these errors with bad disks occasionally: | Quote: | | Buffer I/O error on device sdb10, logical block 748 |
. It could also be an issue with firewire disks, do other disks work with this configuration?
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml |
|
| Back to top |
|
|
Wizumwalt
Guru
Joined: 20 Aug 2006
Posts: 547
|
| Posted: Sun Dec 28, 2008 2:17 am Post subject: |
|
|
1. Yes,
2. Oops.
3. Darn!
Today I updated my kernel to 2.6.27-r7 and after rebooting, I don't see sdb9 anymore, but now I have sdb11. Though it still doesn't mount. Same errors. I don't have any other firewire devices to try.
But when I plug the firewire into my linux box from the mac, I get the following details showing sdb9, sdb10 which I don't see in my /dev dir.
| Code: |
Dec 27 20:14:07 Tux ieee1394: Node added: ID:BUS[0-00:1023] GUID[000393fffe98c980]
Dec 27 20:14:07 Tux ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Dec 27 20:14:07 Tux scsi4 : SBP-2 IEEE-1394
Dec 27 20:14:08 Tux ieee1394: sbp2: Logged into SBP-2 device
Dec 27 20:14:08 Tux ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Dec 27 20:14:08 Tux isa bounce pool size: 16 pages
Dec 27 20:14:08 Tux scsi 4:0:0:0: Direct-Access-RBC AAPL FireWire Target 0000 PQ: 0 ANSI: 3
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] 78242976 512-byte hardware sectors (40060 MB)
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] Write Protect is off
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] Mode Sense: 10 00 00 00
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] 78242976 512-byte hardware sectors (40060 MB)
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] Write Protect is off
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] Mode Sense: 10 00 00 00
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Dec 27 20:14:08 Tux sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11
Dec 27 20:14:08 Tux sd 4:0:0:0: [sdb] Attached SCSI disk
Dec 27 20:14:08 Tux sd 4:0:0:0: Attached scsi generic sg2 type 14
|
|
|
| Back to top |
|
|
JoseJX
Retired Dev
Joined: 28 Apr 2002
Posts: 2774
|
|
| Back to top |
|
|
Wizumwalt
Guru
Joined: 20 Aug 2006
Posts: 547
|
| Posted: Sun Dec 28, 2008 6:59 am Post subject: |
|
|
Here's the results, but it took several minutes for the results to appear.
| Code: |
# mac-fdisk -l /dev/sdb
/dev/sdb
# type name length base ( size ) system
/dev/sdb1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map
/dev/sdb2 Apple_Driver43 Macintosh 56 @ 64 ( 28.0k) Driver 4.3
/dev/sdb3 Apple_Driver43 Macintosh 56 @ 120 ( 28.0k) Driver 4.3
/dev/sdb4 Apple_Driver_ATA Macintosh 56 @ 176 ( 28.0k) Unknown
/dev/sdb5 Apple_Driver_ATA Macintosh 56 @ 232 ( 28.0k) Unknown
/dev/sdb6 Apple_FWDriver Macintosh 512 @ 288 (256.0k) Unknown
/dev/sdb7 Apple_Driver_IOKit Macintosh 512 @ 800 (256.0k) Unknown
/dev/sdb8 Apple_Patches Patch Partition 512 @ 1312 (256.0k) Unknown
/dev/sdb9 Apple_Free 262144 @ 1824 (128.0M) Free space
/dev/sdb10 Apple_HFS Apple_HFS_Untitled_1 77978992 @ 263968 ( 37.2G) HFS
/dev/sdb11 Apple_Free 16 @ 78242960 ( 8.0k) Free space
Block size=512, Number of Blocks=78242976
DeviceType=0x0, DeviceId=0x0
Drivers-
1: @ 64 for 23, type=0x1
2: @ 120 for 36, type=0xffff
3: @ 176 for 21, type=0x701
4: @ 232 for 34, type=0xf8ff
|
And this is what showed up in my /var/log/messages ...
| Code: |
Dec 28 00:42:24 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:42:24 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:43:28 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:43:28 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:44:29 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:44:29 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:45:29 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:45:29 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:46:30 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:46:30 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:47:30 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:47:30 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:47:30 Tux sd 5:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK,SUGGEST_OK
Dec 28 00:47:30 Tux end_request: I/O error, dev sdb, sector 269952
Dec 28 00:47:30 Tux Buffer I/O error on device sdb10, logical block 748
Dec 28 00:48:31 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:48:31 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:49:31 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:49:31 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:50:32 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:50:32 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:51:32 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:51:32 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:52:32 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:52:32 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:53:33 Tux ieee1394: sbp2: aborting sbp2 command
Dec 28 00:53:33 Tux sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 04 1e 80 00 00 08 00
Dec 28 00:53:33 Tux sd 5:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK,SUGGEST_OK
Dec 28 00:53:33 Tux end_request: I/O error, dev sdb, sector 269952
Dec 28 00:53:33 Tux Buffer I/O error on device sdb10, logical block 748
|
|
|
| Back to top |
|
|
DirtyHairy
l33t
Joined: 03 Jul 2006
Posts: 608
Location: Würzburg, Deutschland
|
| Posted: Sun Dec 28, 2008 11:25 am Post subject: |
|
|
| These I/O errors do look bad. Do other firewire drives work on your machine? If you have access to another machine with firewire, you could try and see if it works there; also, you could try to take the disk out of its firewire case and attach it directly (but beware, this might void your warranty on the drive). |
|
| Back to top |
|
|
Wizumwalt
Guru
Joined: 20 Aug 2006
Posts: 547
|
| Posted: Sun Dec 28, 2008 4:54 pm Post subject: |
|
|
This drive is inside a TiPB G4 (no warranty left to void  . I don't have anything else to try it with to see if firewire works. |
|
| Back to top |
|
|
JoseJX
Retired Dev
Joined: 28 Apr 2002
Posts: 2774
|
| Posted: Mon Dec 29, 2008 8:15 pm Post subject: |
|
|
Well, first of all, the device that has the HFS+ filesystem is /dev/sdb10 (from the mac-fdisk results). Try mounting this one and see if it works. If no device exists for that partition, make one with mknod:
But it does appear that there are issues with the disk itself which is causing your I/O errors in dmesg.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on PPC
