Access my USB external 250 Gb drive

I am alway carrying my file cabinet of a USB external 250 GB drive (Samsung S1 small drive) in business trip. With iPad, is there any way to access my drive in wired way or wireless way?

As an alternative, you could install the Dropbox software, and buy the 9.99 per month 100 gig cloud storage, selectively load your files on it, and then you can access it from anywhere. As a plus for no extra cost you can also install on your imac and phone and they would all have synchronized access to the dropbox. Dont know if thats a practical expense for you, but thats about the only option that would work at this point.

Similar Messages

Portege R500: XP installation with USB external CD/DVD drive - SOLUTION

Hello all !
Just wanted to take five minutes to inform you that installing XP on a Portege R500 with USB external CD/DVD drive is possible, even if you already have erased Vista and only with a bootable CD of Win XP in hand.
First go into your BIOS and check / set first boot device is CD/DVD drive
Start your installation of win XP from the CD without the F6 thing and let it go his way
After a while, the installation stops and says "can't find the file xxxx" and you are invited to say where this file is
You "just" have to replace the drive letter "C:" that is given by default with the drive letter of your CD/DVD (and let the rest just like it is) and the installation will continue until the next "can't find..." and you will again replace the drive letter, etc..
After a complete "manually assisted automatic" installation, you are welcome in Win XP !
Next question is "Where can I find my CD/DVD drive letter ?" and the answer is "this is the next letter after your last HDD letter" (I consider you have only your Portege with nothing else plugged than your CD/DVD) so in most cases it will be "E" because C: is the first partition of your HDD and D: is the hidden / recovery partition that win creates.
But do not worry, if you type the wrong letter you will have as many tries as you wish until you find the good one and for the following "can't find..." it will remain the same.
I hope these pieces of information will help some of you who want a clean install of win XP starting from a newly formatted HDD.
With kind Regards,
Mage.

What a great information!
Thanks a lot for this posting.
I think it could be useful for others here.
Bye

Access NTFS USB external drive from OEL5

I am not able to access NTFS file system from OEL5 VMWare image. It says it doesn't support NTFS file system. How do I create VMWare Image of OEL5 which is compatible with NTFS file system?
Thanks Gurus!!

Not possible on OEL out-of-the-box. Can be done, with varying degrees of success, using techniques like this:
http://wiki.centos.org/TipsAndTricks/NTFSPartitions
Good luck.

Problem with USB External Hard Disk Drive

I have similar problem with hard disk MK6025GAS in Sweex casing connected via USB as Raistlfiren in this post but I am not sure if it has something to do with kernel. The problem is that when I plug the hard disk via USB it is not even shown with in /dev/ or by fdisk -l. I had similar problems with the drive before but it was always shown in /dev.
I got same output from dmesg as Raistlfiren in the post before
# dmesg | tail
sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
Info fld=0x0
I was browsing net for a lot of time to find a solution but nothing helped a lot. The problem is closes to the one described on Gentoo Forum
I can see that it is recognized by computer since it is shown with lsusb
# lsusb
Bus 001 Device 005: ID 13fd:0540 Initio Corporation
# lsusb -d 13fd:0540 -v
Bus 001 Device 005: ID 13fd:0540 Initio Corporation
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13fd Initio Corporation
idProduct 0x0540
bcdDevice 0.00
iManufacturer 1 Initio
iProduct 2 MK6025GAS
iSerial 3 0010100500000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
From the beginning I though and I still think that the partition table is screwed up but the programs like TestDisk and fixdisktable work only with disks shown in /dev/
Additionally, I have checked the content of /var/log/kernel.log
Sep 16 22:03:58 hramat kernel: usb 1-2: new high speed USB device using ehci_hcd and address 5
Sep 16 22:03:58 hramat kernel: usb 1-2: configuration #1 chosen from 1 choice
Sep 16 22:03:58 hramat kernel: scsi4 : SCSI emulation for USB Mass Storage devices
Sep 16 22:03:58 hramat kernel: usb-storage: device found at 5
Sep 16 22:03:58 hramat kernel: usb-storage: waiting for device to settle before scanning
Sep 16 22:04:03 hramat kernel: scsi 4:0:0:0: Direct-Access Initio MK6025GAS 2.23 PQ: 0 ANSI: 0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
Sep 16 22:04:03 hramat kernel: usb-storage: device scan complete
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB)
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Write Protect is off
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Mode Sense: 86 0b 00 02
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sdd:<6>sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
Sep 16 22:04:03 hramat kernel: Info fld=0x0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
and /var/log/errors.log
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:07:35 hramat kernel: INFO: task async/0:3957 blocked for more than 120 seconds.
Sep 16 22:07:35 hramat kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
The only thing I understand from these logs is that the disk is blocked, therefore not listed in /dev.
Assuming the newer kernel problems I could try to use some older live linux CD to see if that would work. I am also thinking of connecting this hard drive directly to my laptop, using live linux CD and maybe check the output of hdparm. Is there anything else I could check or try?
Thank you for any help or suggestions
Matej

Thank you nTia89 for response. Sorry for not providing enough information.
I believe the problem is not system dependent. I have dual boot with windows and there the disk has also problems. However, I do have Arch32 with Kernel 2.6.30, using Gnome. hal and dbus are also running.
I did not tried to connect the disk to the computer directly, I will try it today.
Yesterday I have used SystemRescueCD 0.4.1 with Kernel 2.6.22. I wanted to see if it will be recognized by the system and placed in /dev/. Yes it was. This means that the problem highlighted in Gentoo forum can be true, but it doesn't solve my problem. I have tried to connect the drive several times to Arch and it was not shown in /dev/sd*, in SystemRescueCD it was placed as /dev/sdb. Now I am sure that the partition table is screwed up.
So I have started to play with the drive in SystemRescueCD with TestDisk and FixDiskTable but without success.
% fdisk -l
Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1530 12289693+ 7 HPFS/NTFS
/dev/sda2 1531 6672 41303115 7 HPFS/NTFS
/dev/sda3 6673 12161 44090392+ f W95 Ext'd (LBA)
/dev/sda5 * 6673 11908 42058138+ 83 Linux
/dev/sda6 11909 12161 2032191 82 Linux swap / Solaris
Disk /dev/sdb: 60.0 GB, 60011642880 bytes
64 heads, 32 sectors/track, 57231 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk /dev/sdb doesn't contain a valid partition table
Manufacturer disk geometry: Heads: 16; Cylinders: 16383; Sectors: 63; Logical Blocks (LBA): 117210240
TestDisk found only Linux partitions with 43Gb while disk had only one 60Gb partitioned with FAT32/NTFS.
Also recognized 64 heads, 57231 cylinders and 32 sectors (same as from fdisk -l), which obviously differs from manufacturer disk geometry.
testdisk.log:
Thu Sep 17 19:09:26 2009
Command line: TestDisk
TestDisk 6.8, Data Recovery Utility, August 2007
Christophe GRENIER
Linux version (ext2fs lib: 1.40.2, ntfs lib: 9:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none)
Using locale 'C'.
Hard disk list
Disk /dev/sda - 100 GB / 93 GiB - CHS 12161 255 63, sector size=512
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32, sector size=512
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
Interface Advanced
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Computes LBA from CHS for Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Allow partial last cylinder : Yes
search_vista_part: 1
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
interface_write()
No partition found or selected for recovery
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Allow partial last cylinder : Yes
search_vista_part: 1
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Results
interface_write()
No partition found or selected for recovery
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
NTFS at 8956/63/32
heads/cylinder 255 (NTFS) != 64 (HD)
sect/track 63 (NTFS) != 32 (HD)
filesystem size 24579387
sectors_per_cluster 8
mft_lcn 1024141
mftmirr_lcn 1650676
clusters_per_mft_record -10
clusters_per_index_record 1
NTFS part_offset=9392094720, part_size=12584646144, sector_size=512
NTFS partition cannot be added (part_offset<part_size).
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34129 1 1 75201 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=69896224, size=84116272, end=154012495, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34632 2 1 75704 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=70926400, size=84116272, end=155042671, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34668 0 1 75740 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71000064, size=84116272, end=155116335, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34673 1 1 75745 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71010336, size=84116272, end=155126607, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34699 2 1 75771 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71063616, size=84116272, end=155179887, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34708 2 1 75780 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71082048, size=84116272, end=155198319, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36338 0 1 77410 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74420224, size=84116272, end=158536495, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36367 0 1 77439 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74479616, size=84116272, end=158595887, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36401 2 1 77473 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74549312, size=84116272, end=158665583, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36414 2 1 77486 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74575936, size=84116272, end=158692207, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37949 1 1 79021 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77719584, size=84116272, end=161835855, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37955 1 1 79027 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77731872, size=84116272, end=161848143, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37989 1 1 79061 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77801504, size=84116272, end=161917775, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 38404 0 1 79476 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=78651392, size=84116272, end=162767663, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 39636 2 1 80708 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=81174592, size=84116272, end=165290863, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41263 1 1 82335 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=84506656, size=84116272, end=168622927, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41266 1 1 82338 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=84512800, size=84116272, end=168629071, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41660 0 1 82732 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=85319680, size=84116272, end=169435951, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 42898 0 1 83970 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=87855104, size=84116272, end=171971375, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 43244 1 1 84316 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=88563744, size=84116272, end=172680015, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 44870 2 1 85942 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=91893824, size=84116272, end=176010095, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 44930 2 1 86002 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=92016704, size=84116272, end=176132975, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 46961 0 1 88033 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=96176128, size=84116272, end=180292399, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 47312 0 1 88384 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=96894976, size=84116272, end=181011247, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 48393 2 1 89465 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=99108928, size=84116272, end=183225199, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 49633 2 1 90705 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=101648448, size=84116272, end=185764719, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 50767 1 1 91839 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=103970848, size=84116272, end=188087119, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 51150 1 1 92222 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=104755232, size=84116272, end=188871503, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 51941 1 1 93013 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=106375200, size=84116272, end=190491471, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 52759 0 1 93831 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=108050432, size=84116272, end=192166703, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 53069 1 1 94141 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=108685344, size=84116272, end=192801615, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 53768 0 1 94840 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=110116864, size=84116272, end=194233135, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54287 0 1 95359 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=111179776, size=84116272, end=195296047, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54493 2 1 95565 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=111601728, size=84116272, end=195717999, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54861 1 1 95933 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112355360, size=84116272, end=196471631, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54890 2 1 95962 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112414784, size=84116272, end=196531055, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54953 2 1 96025 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112543808, size=84116272, end=196660079, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 56330 1 1 97402 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=115363872, size=84116272, end=199480143, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 56334 0 1 97406 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=115372032, size=84116272, end=199488303, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 57203 0 1 98275 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=117151744, size=84116272, end=201268015, disk end=117211136)
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (60 GB / 55 GiB) seems too small! (< 103 GB / 95 GiB)
The following partitions can't be recovered:
D Linux 34129 1 1 75201 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34632 2 1 75704 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34668 0 1 75740 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34673 1 1 75745 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34699 2 1 75771 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34708 2 1 75780 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36338 0 1 77410 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36367 0 1 77439 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36401 2 1 77473 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36414 2 1 77486 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37949 1 1 79021 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37955 1 1 79027 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37989 1 1 79061 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 38404 0 1 79476 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 39636 2 1 80708 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41263 1 1 82335 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41266 1 1 82338 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41660 0 1 82732 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 42898 0 1 83970 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 43244 1 1 84316 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 44870 2 1 85942 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 44930 2 1 86002 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 46961 0 1 88033 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 47312 0 1 88384 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 48393 2 1 89465 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 49633 2 1 90705 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 50767 1 1 91839 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 51150 1 1 92222 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 51941 1 1 93013 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 52759 0 1 93831 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 53069 1 1 94141 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 53768 0 1 94840 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54287 0 1 95359 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54493 2 1 95565 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54861 1 1 95933 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54890 2 1 95962 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54953 2 1 96025 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 56330 1 1 97402 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 56334 0 1 97406 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 57203 0 1 98275 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
Results
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
Interface Advanced
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Allow partial last cylinder : No
search_vista_part: 0
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
Can't open backup.log file: No such file or directory
interface_load
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
TestDisk exited normally.
fixdisktable first output:
% ./fixdisktable -d /dev/sdb
Getting hard disk geometry
cylinders=57231, heads=64, sectors=32
end_offset: 2147482624
FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
EXT2 partition at offset 56832, length=(41072.398 MB) 43067531264
Sectors: start= 111, end= 84116382, length= 84116272
Hd,Sec,Cyl: start(3,16,0) end(28,31,41072)
Done searching for partitions.
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 3 16 0 63 32 1023 111 84116273 83 (Interpretted)
1 80 3 16 0 63 224 255 111 84116273 83 (RAW)
1: 8003 1000 833f e0ff 6f00 0000 3183 0305
2: 0000 0000 0000 0000 0000 0000 0000 0000
3: 0000 0000 0000 0000 0000 0000 0000 0000
4: 0000 0000 0000 0000 0000 0000 0000 0000
Do you wish to write this partition table to disk (yes/no)? no
fixdisktable second output:
% ./fixdisktable -d -r -v /dev/sdb
Getting hard disk geometry
cylinders=57231, heads=64, sectors=32
end_offset: 2147482624
FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
NTFS partition at offset 17483776, length=(17592186043512.582 MB) 184467440727622 49216
Sectors: start= 34148, end=36028797017147916, length=36028797017113768
Hd,Sec,Cyl: start(43,5,16) end(16,12,2096265)
Done searching for partitions.
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 43 5 16 63 32 1023 34148 -1850199 07 (Interpretted)
1 80 43 5 16 63 224 255 34148 -1850199 07 (RAW)
1: 802b 0510 073f e0ff 6485 0000 a9c4 e3ff
2: 0000 0000 0000 0000 0000 0000 0000 0000
3: 0000 0000 0000 0000 0000 0000 0000 0000
4: 0000 0000 0000 0000 0000 0000 0000 0000
Do you wish to write this partition table to disk (yes/no)? no
This string "FfEeSsNnBbUu" was repeating there for longer time and it was most probably related to debugging or a verbose mode of fixdisktable
As I have mentioned I will try to connect the disk directly to the computer and see what will happen.
Shall I try to correct the disk geometry to the one specified by manufacturer? Is it possible?
Any suggestions?

10.5.6 update - NO access to some external FireWire hard drives

Have been capturing footage, editing, etc on external Western Digital MyBook Premium hard drive lately, including last night, and everything HAD worked fine under 10.5.5.
Just installed 10.5.6 update before going to bed, this morning Finder doesn't recognize same external MyBook hooked up via FireWire.
I tried:
(*) Reinstalling WD "button" software for MacOSX and rebooting... drive doesn't appear,
(*) Cycling power on external HD... drive doesn't appear,
(*) Different FireWire ports... drive doesn't appear,
(*) Disk Utility... drive doesn't appear,
(*) System Profiler... reports FIREWIRE BUS--> UNKNOWN DEVICE
Note: my old-school Granite Digital external FireWire drive does get recognized by both Finder and Disk Utility, so maybe it's only some external FireWire drives like the MyBook?
This may be related to similar thread in Leopard discussions about TimeMachine no longer recognizing external hard drives.
Really bad timing (my fault for installing 10.5.6 before more reports were in), and hope Apple gets a fix for this asap.
Message was edited by: krisvannest

On the Intel iMac, resetting the SMC is as easy as removing the power cord for at least 15 seconds. - http://support.apple.com/kb/HT1543
Resetting PRAM involves the "4-finger salute" at start-up Command-Option-P-R. http://support.apple.com/kb/HT1379 You hold those down until you hear the computer make the startup sound again.

Please Help! - Cannot Access Or See External USB/Firewire Drive

Can anyone help or advise me as I’m really at a loss as how to fix a problem I have with my external hard drive and OX 10.4.6.
I had just completed a fresh install of OS X on my PowerPC iMac G5 using the “Erase & Install” feature.
Everything had gone extremely well, all my applications and settings had been re-set as I normally have them (I made backups) and was able to access my external hard disk, which is a Maxtor OneTouch USB/FireWire 250 GB model.
I then setup a second account for my brother, which I setup as a “Standard” account.
When I then went to access some of the files on my external disk and tried to copy them over to my Desktop, it refused me permission and said that I had to ask the permission of the “Owner’ which it said was Steve (my Brother) which was strange because as I said his account was only setup as a standard account whereas I had an administrator account (and am the main user of the computer).
I went into the Steve's account and looked at the Permissions information using the “Get Info” dialogue box. This showed that the owner was indeed Steve, so I changed it to my Name (Andrew) went back to my account, and found could no longer see the external disk at all.
Returning to Steve’s account I checked the permissions again, and asked it to ignore permissions.
But now I cannot see or access the disk at all in either account, it just does not show up on the desktop or in the Finder Sidebar.
The strange thing is I can see it in “Disk Utility” but when I ask it to either verify or Repair the Disk permissions, it reports that they are all or OK and “no repairs were necessary”.
I have tried connecting the disk with both types of connection - USB2 and the Firewire drive, and the results are exactly the same, the drive is not visible on the Desktop or the Finder Sidebar, but is visible to Disk Utility.
The disk is formatted as a ‘Mac OS Extended (Journaled) drive
Can anyone please tell me how I can get my external disk to show on my computer again, as ALL my backup documents and programs are on the disk, and most of the data cannot be replaced.
Would doing a complete fresh install of the OS X operating system fix this as a last resort?
I hope someone can advise, as I really am desperate.
Thanks
Drusus
20' iMac G5 PowerPC (iSight) 1.5GB Ram Mac OS X (10.4.6)
20' iMac G5 PowerPC (iSight) 1.5GB Ram Mac OS X (10.4.6)

Yes, I didn't think it was very good either!
You are correct in I should have said "Repair Disk" - Verify Permissions is not available on the maxtor drive ( it is dimmed) in Repair Disk.
Until now, the drive has worked perfectly, and I did not install any of Maxtors software when I originally connected the drive to this system, I just formatted it as a Mac Extended and it worked great. It was only after the fresh Erase & Install - even then it worked fine. It was only when I created a new account that the problem started.
What I have done is get hold of a demo version of a program called "Mac Drive 6" which allows you to read any Mac formatted disk or drive on a Windows system, - fortunately i still have my Windows XP Pro system which I have also connected to my home network.
So for the next four days (the length of the demo) I can access all of my files on the disk and copy them to my Windows system.
This is really great because I have all my data and images back which were my biggest concern.
I thought I might get another drive anyhow, and when I have everything backed up on a new drive and on the Windows system, I can then reformat the Maxtor drive and start afresh with it.
Thanks for all your help anyhow.

I have an external hard drive from my time capsule that stopped working on me. I am attempting to access the data with a hard drive reader on my MAC. I am able to see the drive in disk utility and under system info USB. But I am unable to access the data.

I have an external hard drive from my time capsule that stopped working on me. I am attempting to access the data with a hard drive reader on my MAC. I am able to see the drive in disk utility and under system info USB. But I am unable to access the data and it does not show on the desktop when connected.

Ok if disk utility was able to verify the drive I doubt there is any problem.. are you trying to open a TM backup??
You need to mount the sparsebundle then check the actual info inside the bundle.
Don't use disk warrior.. if the disk has verified then unless you deliberately deleted files there is nothing that is going to do.
Pondini has a lot of stuff about getting access to the sparsebundle.
http://pondini.org/TM/17.html
But if you have copied info to the TC that is now gone.. and the disk is ok.. I am not sure.. the TC will not have deleted the files itself.

Can no longer access USB external hard drive

Hi - I am running OS X 10.8.4 on my iMac (21.5-inch, Late 2009), and have been using a La Cie USB external hard drive for several years for my Time Machine backups without issues. All of a sudden yesterday, the external hard drive disappeared from Finder and my Desktop, and as a result, no more Time Machine backups I rebooted both the external hard drive and iMac several times and changed the USB cable but with no success. Disk Utility and Time Machine cannot see the external hard drive but it does appear under System Information => USB (see below). I connected it to my Windows 8 laptop. The Windows laptop can see the external hard drive under Disk Management as an uninitialized disk. But I will not allow me to initialize it and therefore cannot acces it.
Product ID:          0x0951
Vendor ID:          0x059f (LaCie)
Version:           0.00
Serial Number:          152D203380B6
Speed:          Up to 480 Mb/sec
Manufacturer:          LaCie
Location ID:          0x24300000 / 4
Current Available (mA):          500
Current Required (mA):          2
Any help to restore the external hard drive would be appreciated.
Ron

Thank you for your quick response. Disk Utility does not see the hard drive. Windows 8 does see it under Device Manager and says that it is working propoerly but it will not allow me to initialize it.   As indicated to Lin Davis, I'll buy a new external hard drive.

Using a usb external drive with logic

I have a 500 GB Lacie usb hard drive which I'm currently using just to backup my system. (Still on Tiger by the way.) I'm in an older intel iMac (1.83. 2 gigs ram, 250 gig internal hard drive). After installing LP 8 and all the bells and whistles on the internal drive I now have less than half of my internal drive space available. My logic project files are there as well. Not a big problem but I'm trying to look further down the road... Usb drives are slower than firewire but my projects are relatively simple. I don't record more than 2 tracks simultaneously and rarely exceed 24 tracks total for a song. Two questions. First can I get by with my usb external drive? And second how do I move my projects onto and external drive and still have logic know where they are? Thanks

I have the oldest macbook (1.83. 2 gigs ram, 60 gig internal hard drive)
I have all my logic content on my external maxtor firewire 400 drive (usb 2.0 is actually faster than firewire 400) and everything is fine. the good thing is if your external drive has 7200rpm, but the ones with 5600rpm should do as well.
Once you drag your apple loops to logic from your external drive, logic will remember for the next visit. And when you are opening a project which is on the external drive , just find it with logic finder and all should be fine.

Problem mapping USB external drive connected to Airport Extreme on my PC

I am having a problem mapping my USB external drive in my PC running WIndows Vista. Here is what I have so far:
USB External Drive connected to my AirPort Extreme which is connected to my Century Link modem/router.
I have installed the USB drive using the Airport Utility. In the Disks section the Enable File Sharing is checked, Secure Shared Disks is set to With a Disk Password, I have entered the password in the next 2 rows, and finally AirPort Disks Gues Access is set to Not Allowed. The section below named These Settings Configure Windows File Sharing is empty. Am I supposed to put something here?
I was also told I need to map the drive in my PC, but when I go to do that via the Computer and the Map Network Drive, I get stuck where it asks me to enter a folder name. I read many of the posts which tell me I need to enter among other things the disk's ip address, but I am unable to find it anywhere. Where do I find what to put here?
Can someone please help this frustrated user?

I had my USB drive on my APE working with Time Machine under 10.5.1 very reliably. A few days ago however, I needed to suspend a backup operation, and when I came back to restart it, time machine refused to mount the disk image on the drive. After several attempts to get it to connect with no luck I decided to delete the image (the sparce image file) and start over. Now TM refuses to create a new image.
BTW, on the Mac OSX hints site there have been suggestions to start a backup with the drive directly connected, then stop the backup, move the sparce image file to the root of the drive, reconnect the drive to the APE base station to get it working. I tried this again, but I think Apple has changed something in 10.5.2, because when directly connected TM no longer creates a sparce image file.
Anybody else seen this behavior after upgrading to 10.5.2?

External USB 2.0 hard drive reconnects on its own after power-down

I have an external USB 2.0 hard drive which I'm trying to power off (after unmounting all partitions, of course) using:
$ udisksctl power-off --block-device /dev/sdb
When I do this, the drive spins back up after a few seconds. Only when I issue the same command again does the drive stay powered off.
I'm running:
linux 3.13.7-1
udisks2 2.1.3-1
This is what I see in the journal log when I:
- Plug in the drive's USB cable
- Issue the power-off command
- After the drive spins up again, issue the command again
Mar 29 19:51:01 miki-desktop kernel: usb 1-5: new high-speed USB device number 10 using ehci-pci
Mar 29 19:51:01 miki-desktop kernel: usb-storage 1-5:1.0: USB Mass Storage device detected
Mar 29 19:51:01 miki-desktop kernel: usb-storage 1-5:1.0: Quirks match for vid 1058 pid 0704: 8000
Mar 29 19:51:01 miki-desktop kernel: scsi12 : usb-storage 1-5:1.0
Mar 29 19:51:01 miki-desktop mtp-probe[21301]: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:04.1/usb1/1-5"
Mar 29 19:51:01 miki-desktop mtp-probe[21301]: bus: 1, device: 10 was not an MTP device
Mar 29 19:51:02 miki-desktop kernel: scsi 12:0:0:0: Direct-Access WD 5000BMV External 1.75 PQ: 0 ANSI: 4
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Write Protect is off
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Mode Sense: 23 00 00 00
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:02 miki-desktop kernel: sdb: sdb1 sdb2
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Attached SCSI disk
Mar 29 19:51:47 miki-desktop udisksd[21107]: Powering off /dev/sdb - successfully sent SCSI command START STOP UNIT
Mar 29 19:51:47 miki-desktop udisksd[21107]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:04.1/usb1/1-5/remove
Mar 29 19:51:47 miki-desktop kernel: usb 1-5: USB disconnect, device number 10
Mar 29 19:51:47 miki-desktop kernel: usb 2-5: new full-speed USB device number 9 using ohci-pci
Mar 29 19:51:48 miki-desktop kernel: usb 2-5: not running at top speed; connect to a high speed hub
Mar 29 19:51:48 miki-desktop kernel: usb-storage 2-5:1.0: USB Mass Storage device detected
Mar 29 19:51:48 miki-desktop kernel: usb-storage 2-5:1.0: Quirks match for vid 1058 pid 0704: 8000
Mar 29 19:51:48 miki-desktop kernel: scsi13 : usb-storage 2-5:1.0
Mar 29 19:51:48 miki-desktop mtp-probe[21555]: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:04.0/usb2/2-5"
Mar 29 19:51:48 miki-desktop mtp-probe[21555]: bus: 2, device: 9 was not an MTP device
Mar 29 19:51:49 miki-desktop kernel: scsi 13:0:0:0: Direct-Access WD 5000BMV External 1.75 PQ: 0 ANSI: 4
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Write Protect is off
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Mode Sense: 23 00 00 00
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:52 miki-desktop kernel: sdb: sdb1 sdb2
Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] Attached SCSI disk
Mar 29 19:52:20 miki-desktop udisksd[21107]: Powering off /dev/sdb - successfully sent SCSI command START STOP UNIT
Mar 29 19:52:20 miki-desktop udisksd[21107]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:04.0/usb2/2-5/remove
Mar 29 19:52:20 miki-desktop kernel: usb 2-5: USB disconnect, device number 9
What is interesting is that on first connect, the drive is using ehci-pci driver, then after the first try powering it off, the drive appears to reconnect using the ohci-pci driver. Not just that, it appears to 'jump' from one USB bus to another. How is this even possible?
$ lspci
00:00.0 Host bridge: NVIDIA Corporation MCP73 Host Bridge (rev a2)
00:00.1 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a2)
00:01.0 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.1 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.2 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.3 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.4 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.5 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.6 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:02.0 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:03.0 ISA bridge: NVIDIA Corporation MCP73 LPC Bridge (rev a2)
00:03.1 SMBus: NVIDIA Corporation MCP73 SMBus (rev a1)
00:03.2 RAM memory: NVIDIA Corporation MCP73 Memory Controller (rev a1)
00:03.3 Co-processor: NVIDIA Corporation MCP73 Co-processor (rev a2)
00:03.4 RAM memory: NVIDIA Corporation MCP73 Memory Controller (rev a1)
00:04.0 USB controller: NVIDIA Corporation GeForce 7100/nForce 630i USB (rev a1)
00:04.1 USB controller: NVIDIA Corporation MCP73 [nForce 630i] USB 2.0 Controller (EHCI) (rev a1)
00:0a.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
00:0b.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
00:0c.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
00:0e.0 IDE interface: NVIDIA Corporation MCP73 IDE (rev a2)
00:0f.0 Ethernet controller: NVIDIA Corporation MCP73 Ethernet (rev a2)
01:06.0 Multimedia audio controller: C-Media Electronics Inc CMI8738/CMI8768 PCI Audio (rev 10)
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4550]
02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV710/730 HDMI Audio [Radeon HD 4000 series]
$ lsusb
Bus 001 Device 009: ID 1058:0704 Western Digital Technologies, Inc. Passport External HDD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 007: ID 15ca:0101 Textech International Ltd. MIDI Interface cable
Bus 002 Device 003: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 002 Device 002: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Before the first power-off attempt:
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M
|__ Port 5: Dev 9, If 0, Class=Mass Storage, Driver=usb-storage, 480M
After the first power-off attempt:
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 5: Dev 10, If 0, Class=Mass Storage, Driver=usb-storage, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M
Does anyone know how to fix this problem? Is it a device quirk, a driver bug or something?
Last edited by ackalker (2014-03-29 19:21:04)

Just to be sure, I rebooted my system, shut down lightdm from another VT, made sure that really nothing is using the drive, no partitions are mounted, no services that could try to use the drive (except udisks2.service, could this one be the problem? But how am I supposed to use the udisksctl command when the service isn't running?).
Tried the same command again. same result: I needed to run it twice in a row for it to 'take'.
What I find even more fascinating: how can a USB device jump from one USB bus to another like that? I've honestly never seen anything like this before :-)
Last edited by ackalker (2014-03-29 19:35:29)

Is it possible to hook a USB external hard drive to an iPad?.....the HD has video on it that I wanna watch on my iPad but don't wanna store it on iPad or iTunes....and way format does the video need to be in to watch on iPad?

Is it possible to hook a USB external hard drive to an iPad?.....the HD has video on it that I wanna watch on my iPad but don't wanna store it on iPad or iTunes....and way format does the video need to be in to watch on iPad?

There are some wireless external hard drives that can be used with the iPad.
The Kingston Wi-Drive, which costs $50 for the 16 Gigabyte, and then $30 more for every 16 gigs more. It works by you turning it on and then accessing the files on it from an app that you download on your iDevice. You can access music, movies, and other stuff. No connections or anything, it works like a WiFi connection, you connect to it from the setting on the iPad under wireless networks.
Then there is the Seagate GoFlex, which some would recommend over the Wi-Drive. But this one costs $199 and had 500 Gigabytes of storage. It works the sameway as the Kingston: no wires, runs over its wireless connection. You can actually fit up to 300 HD movies on it.
Another option:
Expand your iPad's storage capacity with HyperDrive
http://www.macworld.com/article/1153935/hyperdrive.html
On the road with a camera, an iPad, and a Hyperdrive
http://www.macworld.com/article/1160231/ipadhyperdrive.html
Pad2, the new iPad Supported Video Formats & Movie Formats
H.264 video up to 1080p, 30 frames per second, High Profile level 4.1 with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats;
MPEG-4 video up to 2.5 Mbps, 640 by 480 pixels, 30 frames per second, Simple Profile with AAC-LC audio up to 160 Kbps per channel, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats;
Motion JPEG (M-JPEG) up to 35 Mbps, 1280 by 720 pixels, 30 frames per second, audio in ulaw, PCM stereo audio in .avi file format
 Cheers, Tom

Accessing a USB hard drive connected to a AEBS from Windows XP SP2

Hi everybody my problem is this, I am using the AEBS. I have an iMac G5 and a Sony vaio laptop running Windows XP SP2. After some initial problems both connect to the Internet and if I attach a USB printer to the AEBS both allow you to print remotely however if I attach an external hard drive only the iMac can access it. The airport disk agent for Windows pops up that a disk has become available but when you try to access it you get an alert message that says, “unknown user, incorrect password, or login is disabled. Please retype login information or contact the disk’s administrator.” If you click on the preferences in Airport Disk, in Windows, no disk is visible although the disk is visible in the Airport Utility! I have tried different hard drives and all the different settings in the Airport Utility for accessing a USB hard drive connected to the AEBS and get the same message regardless. HELP1

Hi John,
My hard drive is already formatted to fat 32. If I "check disks" in AirPort Utillity in windows it see's the disk and knows how much free and used space there is on it. It also knows when I'm accessing the disk from my iMac but when I try to connect to the hard drive from windows I just get the error message in my first post. When I click on AirPort Disk in windows my base station name doesn't appear, it does on my mac. I tried you suggestion but it hasn't helped. Thanks anyway. If you've got any other suggestion i'll gladly give them a try.
Thanks again.

USB External Drive Boot with Internal Drive DEAD

Can I boot from an external USB drive on my iMac when I know that my internal (250 GB) drive is dead?
I have run a diagnostic on the computer and everything but the internal drive is fine.
Thanks for the help.
Kevin

Answer is 'definitely'.
I'm doing it myself for the same reason. BUT, I greatly prefer Firewire 800 if that option is available to you (If not, you could always buy a cheap {=> quality but Fugly Firewire 800 case ....}
I would ALSO like to be able to 'tell the iMac' that it doesn't have an internal drive so that it powers the drive down and 'rests' it....(or never powers it up) I really don't like the idea of all those electrons and Quarks being pumped into a electro-mech device which may well have friction/heat problems... I wonder if I can get the back off the Mac and unplug/sever the power to it... {until I can get around to a permanent fix, of course...}
{It won't let me 'eject" or "dismount" the drive.}
As always: the ONE really big disadvantage of the otherwise magnificent iMacs, MacBooks etc... Us tech heads can't really get at them...

USB External Drive Solutions

USB solutions for MacBook Air:
USB port powered SSD or thumb drives with minimal power requirements seem a good fit.
A USB external hard drive with extraordinarily low power requirements would be another option; possibly one of the green drives might get away with using just USB bus power? Most hard drives do require AC power to safely work with a USB connection. It would be great to determine which if any external hard drives can operate using the minimal current provided through the USB port but I suspect that specific goal will be limited to external flash drives.
Would love to have an external SSD drive with substantial capacity which operates solely on USB power. One nice feature on a cost basis is that it would not need to be especially fast since the bus itself is so limited, so it seems reasonable that there is a scramble going on as I type by vendors seeking to fill this price sensitive niche for all the new Air owners. A relatively slow form of SSD drive would suffice, even something along the lines of a large capacity ordinary thumb drive might be good since the USB bus itself is so limited in speed.
My goal would be something fast enough to saturate all the speed the USB 2 port is capable of, which renders most of the slower ordinary USB thumb drives "not good enough".
Some of the latest USB 3 capable thumb drives might be just the ticket; maybe even several small ones. I can see having one on each side of the Air (balanced with care!). A small flexible dongle would be good in this regard because it could cause serious damage to have a thumb drive's leverage cranking on the USB port of such a thin light device.
Ideally the storage devices would be of the 128 Gb or larger range so as to be able to fit things like Aperture and iTunes libraries.
Of course they will be slow with the Air but they will be portable and functional in a pinch. There would still be speed where it would be needed most, which would be updating that type of database from one's main machine, since the use on the Air would for many of us be modest access to the data.
So you'd have a device which is fast to sync up from your main machine, and as fast and light and nimble as possible for use with the Air on the road where no power is available.

One of the enclosures which feature USB2 and FireWire 800 ports would be great, but many of the ones I am seeing seem to be larger than the USB only models. Of course there's more going on inside those cases that also have FireWire on their boards, but if there's a super slim one out there somewhere that would be cool to know about. This new 750 Gb 7200 RPM drive in a case that can use the speed would be interesting:
http://www.hitachigst.com/internal-drives/mobile/travelstar/travelstar-7k750
The new 320 Gb 7mm drive is also compelling for it's minimal size and the fact that it's a 7200 RPM model too, but of course it has less capacity. It will be interesting to see if it has less drain on the battery; in that regard, a single platter slower spindle speed drive would have the most advantage in theory but this one brings speed and a lighter thinner single platter design to the table so it's pretty interesting. In a form fitted super slim case it would be nifty
http://www.hitachigst.com/internal-drives/mobile/travelstar/travelstar-z5k320
Goal: obtain the fastest speed from a desktop Mac or MacBook Pro with FireWire 800 to the drive, then using the drive via USB with the Air with minimal power draw and a small physical size. I'm certainly not alone in this desire, the sheer lack of size of the 11" Air is such a game changer that smaller add ons become that much more compelling for maximum mobility.
It's like the first time I used a Duo, or the 1400, or the 2400, or the 12" PowerBook, only a LOT better! I've used almost every model over the years and dismantled them all too, my first PowerBook was almost 20 years ago. Been using the 11" non stop for 2 days now and I still bust out laughing every time I fire it up.

Access my USB external 250 Gb drive

Similar Messages

Maybe you are looking for