Disk Utility 13 problem with USB drives

There appears to be a problem with Disk Utility 13 (part of OS X 10.9). At least, so far as I can tell, everything traces back to this app, or possibly OS X 10.9 itself.
I recently upgraded my MacBook Air to OS X 10.9 (reformatted hard drive, installed system from scratch, updated with all the latest Apple updates). I pre-checked all my third party software to make sure it was 10.9 compatible before installing it after the system cleanup, so everything I’m running supposedly has been approved as safe for 10.9. But I’m seeing a problem formatting USB drives that I do not encounter when running under 10.8.
I have a Seagate STAA500101 (“FreeAgent GoFlex”) drive connected via Seagate’s USB3 adapter that I’ve used for some time as a Time Machine backup. Post-overhaul, I decided to erase the backup and start fresh. When I attempt to format it (single GUID partition) with Disk Utility, I see the following messages go by:
Formatting disk1s2 as Mac OS Extended (Journaled) with name Untitled 1
Could not mount disk1s2 with name (null) after erase
Then there’s a pause, and the format appears to conclude fine. But if I run a “Verify Disk” immediately, I get this:
Verifying partition map for “Seagate FreeAgent GoFlex Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Volume  on disk1s2 has 0 bytes of trailing loader space and it needs 134217728 bytes
Problems were found with the partition map which might prevent booting
Error: Partition map needs repair because a data partition needs loader space.
As the drive has just been formatted, that seemed odd. I took it over to another Mac still running 10.8.5 and formatted it there — it worked just fine. Verified just fine. Took the drive back to my MacBook Air and tried to verify the disk — same failure.
I wanted to rule out bad media, so I took a Lexar 16GB USB flash drive and tried to format it with Disk Utility 13 — got the same problem.
The only success I’ve had formatting USB drives under 10.9 is to boot up into OS X Recovery. Disk Utility there formatted my Seagate drive without an error. But once I booted back into normal 10.9 operating mode, the drive once again fails to verify; it makes me leery about using it as a Time Machine backup.
I suppose it’s possible there could be some background component like Sophos causing problems when formatting drives, but if I format a drive via OS X Recovery or another Mac under 10.8, that wouldn’t explain why the drives fail to verify.
Anyone got any other observations on this issue?

Problem resolved. I'm posting this note for anyone else who might run into this situation and come across this discussion.
It actually did turn out to be Sophos -- Cloud, that is. I'd been using Sophos' free Mac antivirus software on a variety of systems but forgot that I was now testing out Sophos Cloud on my own MacBook, which is their new endpoint solution, and supposed to be compatible with OS X 10.9 (although the Mac version is listed as "beta") Sophos Cloud includes a new feature called Device Control which allows you to create a company-wide policy to control access to hardware such as USB drives, optical drives, etc. But apparently it's still pretty buggy. I had my Device Control configured with the default setting of "monitor but do not block" but it was most definitely gumming up the system. With Sophos Cloud installed, here's what happens if I try to run "Verify Disk" on any attached drive. Note on the left side how "disk2s2" shows as a sub-volume for each hard drive.
So if I uninstall Sophos Cloud, reboot and rescan, here's what I get:
Works fine. Note that the "disk2s2" subvolumes are also gone. This is the way Disk Utility also appears on a 10.8 or 10.9 system, even if you have the standard free Sophos for Mac software installed. It's only Sophos Cloud that's not playing nice. It also appears to have stopped me from being able to play DVDs from an attached Apple USB SuperDrive -- that problem was likewise solved by removing Sophos Cloud.

Similar Messages

  • Disk Utility says of USB Drive - "This partition can't be modified" "This disk is not writeable and cannot be partitioned"

    Several months ago I bought a 64GB PNY USB memory stick to transpord data quickly.
    It seemed to work fine.  I could format it as a Mac partition and use it.  I hardly ever need
    it so I just put it away.
    Today I wanted to use it to put a file on and take it to the Kinko's/FedEx to print, and I
    find I cannot mount it on any of my computers, iMac, MacMini or MacBookPro.
    In Disk Utility virtually everything is greyed out.
    Disk Utility says: "This partition can't be modified" "This disk is not writeable and cannot be partitioned"
    If I try to mount it, it says "This disk cannot be mounted"
    There is no physical read-only switch or setting on the disk that I can see and it is very small.
    I has a Mac OS installed on it, so I wonder if that is a problem?  I should be able to write over that
    or reformat it I would think.

    Thanks for these replies. 
    I've got regular time machine backups and just backed up some of my data by copying some key folders to an external drive.  I'm bit paranoid about backup integrity and would ideally like to do another full backup to a different drive using a system other than time machine, in the event that something goes wrong with the time machine backup.  Any recommendations on good and affordable backup software to do a backup of my TM backup?
    One other question: I seem to encounter problems like this pretty frequently.  I'd say once a year or so, my drive fails completely or gets near enough to failing that I have to wipe and restore.  (I've never had a TM backup fail to work, though the last go around there were some hiccups which has led to my backup paranoia.)  I've had this happen on multiple computers, so I'm becoming pretty convinced that the problem lies somewhere in my data.  Is it possible (even likely) that there's something in my data causing this recurring problem?  If so, is there anything I might be able to do to try and pinpoint and address this problem?  I'd love to go one year without having to wipe/restore my machine!
    For a while I thought I just had bad luck.  But I think this is like the 4th or 5th time this has happened in the past 4 years and every time, I'm restoring from a backup, so I come back with the same data.  It's the one constant since I've had 3 different machines over this same time period. 

  • Disk Utily - Problem with Hard Drive Erase

    I have just upgraded my 12" PowerBook G4 Aluminium with a 80GB Hitachi Travelstar 5K100. I cannot get the disk to Erase (and hence format) in Disk Utilty.
    I booted from the Mac OS X Panther Disc One and ran the Disk Utilty. The new drive is visible in the left pane. I selected it, clicked on the Erase tab, selected MAC OS Extended (journaled), clicked Erase, and then Erase again (from the "are you sure?" Dialogue box). A progress bar then appears in the bottom right hand corner with the caption "Partitioning" to the left of it, and about 2mm of blue showing as progress. It does not, however, make any further progress, no matter how long I leave it. I understand, from what I have read, that the erase process is normally quite rapid?
    I have tried the Erase routine several times now, each time with the result described above. The caption "partitioning" seems strange, as I am not trying to partition the drive.
    I have spent hours trawling the web looking for a solution to this problem, but without success. I am extremely frustrated by the situation, especially as the physical replacement was actually pretty straight-forward.
    Has anyone come across this problem before? If so, what's the diagnosis and is there a resolution?
    PowerBook G4 12" Aluminium   Mac OS X (10.3)   867MHz, 256MB RAM, 40GB HD

    Hi Gerry:
    When erasing (formatting/initializing, take your pick) a hard drive for the first time, Disk Utility will show one entry for the hard drive in the column on the left. (This entry typically includes the manufacturer and/or model information.) During the initialization process, Disk Utility will by default create one partition (formatted volume) utilizing 100 per cent of the available capacity.
    1. Select the hard drive to be erased.
    2. Go to the Erase tab, select the Volume Format (by default it is Mac OS Extended (Journaled)), and give the volume a name.
    3. Click on Erase. The captioning first states that it is partitioning the drive, and the progress indicator holds at a couple of millimeters for anywhere from a few seconds to a minute. It should then change to "Formatting", and the progress bar will complete within a few more seconds.
    I just erased a 400GB external firewire drive and the whole process took less than a minute. If it gets stuck on "Partitioning" and it never says "Formatting", then I'd suspect the hard drive. Some defect on the drive is preventing Disk Utility from creating the partition.
    You could try using the Partition tab instead of the Erase tab; try to make two equal partitions, and if it's successful, delete the partitions and try to make one. Kappy, who's one of the veterans around here, always suggests using the Partition tab for initializing a new disk. Maybe he knows something we don't.
    Andrew

  • DIsk Utility Question  w/ usb drive

    I have a 2 gig usb drive that i use for everything, keep my school notes, a couple small programs on it etc. and last night i installed xp using bootcamp. i wanted to partition my usb drive into 2 partitions, one that i can continue to use with my mac, and one like a bridge to transfer files etc. i went into disk utility today to do that and then selected my usb drive, went to the partition tab, and it presented me with this statement
    does anyone know how to fix this, or how i can partition this usb drive? and ive already backed up the information on the usb drive to a cd. thanks for the help...
    troy
    g4 mac mini, 2 ghz white macbook   Mac OS X (10.4.8)   3rd generation ipod

    i relaunched disk utility and it said the same thing as before. i restarted, the same thing, shut down for an hour and a half, same thing. the usb drive is just the little dongle kind, the one where you can just carry it around in your pocket, so it doesn't come with a power supply, so thats a no-go. i tried to go into the partition section of my actual harddrive, and it works good, shows the 10 gb winxp partition and the 50(or so) gb mac osx section so it isn't the computer. any other suggestions? thanks
    troy

  • Help Problem with USB Drives

    I connected two USB drives to my MBP yesterday and all I was doing was transferring files from one USB drive to the other. One of the USB drives in the middle of the transfer would disconnect for no reason and the transfer would freeze. I tried to do the same thing on my 12 inch PB G4 running 10.4.11 and I had no problems transferring files with no freezing. Does anyone know what might be happening. Thanks for your help.

    Weird... It happened to my old MBP. I brought it to the Apple Store (I had some other issues too), and they replaced the logic board and it was fine afterwards.

  • Permissions / Sharing - Problem with USB Drives

    Hi,
    I suspect it's possible to do what I want, but not via the "easy" route. I'm very new to OS X, so hoping there's some more advanced functionality I haven't found yet.
    This is what I want to do:
    I have a USB drive connected to a Mac Mini running Snow Leopard. I have two users setup - one admin, one normal. I want only the local admin account to be able to access the files on the USB drive. I want the admin account to share the contents via the local network with my (Vista) laptop (which is setup with the same username / password as the admin account).
    Problem I have is that whenever I try to apply any permissions to the USB drive, they are ignored. From what I've found on the internet, that is "by design" behaviour.
    Are there any ways around this that people can suggest? Scripts? Other utilities? Other settings hidden away somewhere?
    Beyond that, ideally I'd like to encrypt the whole drive as a TrueCrypt partition, mount the drive automatically when the laptop is detected (using a keyfile stored on the laptop), and then only let the laptop access the drive. But I'll accept a simple solution for now!
    Thanks,
    David

    select the external drive in finder and enter command+i. in the resulting popup unlock the lock and uncheck the box to ignore ownership on this drive. permissions won't be ignored now. give your admin user read+write permissions to the drive and remove them from everybody else. that should do it.
    I don't use TrueCrypt and can't comment on that.

  • Problem with USB drive not writing/freezing on unmount.

    I have a sandisk cruzer blade USB drive, which I have used for the past hours extensively. At one point, I couldn't manage to write data to it. It acted like it had, but it didn't, as it silently remounted as readonly. I solved this by remounting as rw and retried.
    Now, when using the same drive, after writing around 2 GiB worth of data to it (creating files), and attempting to unmount, the unmount command freezes for a long period of time. I check dmesg and it says its frozen. So I open up another tab to try and rescue the writes I made by typing sync. This also freezes and generates dmesg messages.
    As I'm typing this the commands seemed to have succeeded, but I'm wondering, what causes these problems? Is the problem known?
    dmesg output:
    [ 1440.339510] INFO: task umount:1540 blocked for more than 120 seconds.
    [ 1440.339518] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 1440.339523] umount D ffff88021da81950 0 1540 1539 0x00000004
    [ 1440.339531] ffff8801d9ad7c70 0000000000000082 0000000000014500 ffff8801d9ad7fd8
    [ 1440.339538] ffff8801d9ad7fd8 0000000000014500 ffff88021da81950 ffff88022ec94500
    [ 1440.339545] ffff8801d9ad7bc0 ffffffff81091995 ffff88022211c380 0000000000000002
    [ 1440.339551] Call Trace:
    [ 1440.339565] [<ffffffff81091995>] ? check_preempt_curr+0x85/0xa0
    [ 1440.339571] [<ffffffff8108ecfa>] ? ttwu_stat+0x9a/0x110
    [ 1440.339579] [<ffffffff81093a0c>] ? try_to_wake_up+0x1fc/0x2c0
    [ 1440.339586] [<ffffffff814e1029>] schedule+0x29/0x70
    [ 1440.339593] [<ffffffff814dd909>] schedule_timeout+0x219/0x290
    [ 1440.339599] [<ffffffff8107b746>] ? __queue_work+0x136/0x390
    [ 1440.339606] [<ffffffff814e03c3>] wait_for_common+0xd3/0x180
    [ 1440.339612] [<ffffffff81093b10>] ? wake_up_process+0x40/0x40
    [ 1440.339617] [<ffffffff814e048d>] wait_for_completion+0x1d/0x20
    [ 1440.339625] [<ffffffff811c8bd0>] writeback_inodes_sb_nr+0x80/0xb0
    [ 1440.339648] [<ffffffff811c8c25>] writeback_inodes_sb+0x25/0x30
    [ 1440.339655] [<ffffffff811cdedd>] sync_filesystem+0x2d/0xa0
    [ 1440.339662] [<ffffffff811a1cb0>] generic_shutdown_super+0x30/0xe0
    [ 1440.339668] [<ffffffff811a1f97>] kill_block_super+0x27/0x70
    [ 1440.339678] [<ffffffff811a22fd>] deactivate_locked_super+0x3d/0x60
    [ 1440.339684] [<ffffffff811a28e6>] deactivate_super+0x46/0x60
    [ 1440.339689] [<ffffffff811bdeaf>] mntput_no_expire+0xef/0x150
    [ 1440.339695] [<ffffffff811bf0b1>] SyS_umount+0x91/0x3b0
    [ 1440.339701] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1f
    [ 1560.250364] INFO: task umount:1540 blocked for more than 120 seconds.
    [ 1560.250371] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 1560.250375] umount D ffff88021da81950 0 1540 1539 0x00000004
    [ 1560.250383] ffff8801d9ad7c70 0000000000000082 0000000000014500 ffff8801d9ad7fd8
    [ 1560.250390] ffff8801d9ad7fd8 0000000000014500 ffff88021da81950 ffff88022ec94500
    [ 1560.250397] ffff8801d9ad7bc0 ffffffff81091995 ffff88022211c380 0000000000000002
    [ 1560.250403] Call Trace:
    [ 1560.250416] [<ffffffff81091995>] ? check_preempt_curr+0x85/0xa0
    [ 1560.250422] [<ffffffff8108ecfa>] ? ttwu_stat+0x9a/0x110
    [ 1560.250429] [<ffffffff81093a0c>] ? try_to_wake_up+0x1fc/0x2c0
    [ 1560.250435] [<ffffffff814e1029>] schedule+0x29/0x70
    [ 1560.250442] [<ffffffff814dd909>] schedule_timeout+0x219/0x290
    [ 1560.250448] [<ffffffff8107b746>] ? __queue_work+0x136/0x390
    [ 1560.250454] [<ffffffff814e03c3>] wait_for_common+0xd3/0x180
    [ 1560.250460] [<ffffffff81093b10>] ? wake_up_process+0x40/0x40
    [ 1560.250465] [<ffffffff814e048d>] wait_for_completion+0x1d/0x20
    [ 1560.250473] [<ffffffff811c8bd0>] writeback_inodes_sb_nr+0x80/0xb0
    [ 1560.250493] [<ffffffff811c8c25>] writeback_inodes_sb+0x25/0x30
    [ 1560.250499] [<ffffffff811cdedd>] sync_filesystem+0x2d/0xa0
    [ 1560.250506] [<ffffffff811a1cb0>] generic_shutdown_super+0x30/0xe0
    [ 1560.250513] [<ffffffff811a1f97>] kill_block_super+0x27/0x70
    [ 1560.250522] [<ffffffff811a22fd>] deactivate_locked_super+0x3d/0x60
    [ 1560.250528] [<ffffffff811a28e6>] deactivate_super+0x46/0x60
    [ 1560.250533] [<ffffffff811bdeaf>] mntput_no_expire+0xef/0x150
    [ 1560.250538] [<ffffffff811bf0b1>] SyS_umount+0x91/0x3b0
    [ 1560.250545] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1f
    [ 1560.250550] INFO: task sync:1547 blocked for more than 120 seconds.
    [ 1560.250553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 1560.250556] sync D ffffffff811cdd00 0 1547 985 0x00000000
    [ 1560.250561] ffff8801be2e1e68 0000000000000086 0000000000014500 ffff8801be2e1fd8
    [ 1560.250567] ffff8801be2e1fd8 0000000000014500 ffff8801c1335460 ffff8801be2e1e70
    [ 1560.250573] ffffffff811326ab ffff8801be2e1de0 ffff88020bdbc280 0000000000000080
    [ 1560.250579] Call Trace:
    [ 1560.250586] [<ffffffff811326ab>] ? filemap_fdatawait_range+0x17b/0x1a0
    [ 1560.250594] [<ffffffff811cdd00>] ? generic_write_sync+0x60/0x60
    [ 1560.250599] [<ffffffff814e1029>] schedule+0x29/0x70
    [ 1560.250604] [<ffffffff814e1d85>] rwsem_down_read_failed+0xc5/0x120
    [ 1560.250610] [<ffffffff81292744>] call_rwsem_down_read_failed+0x14/0x30
    [ 1560.250616] [<ffffffff814dffa7>] ? down_read+0x17/0x20
    [ 1560.250620] [<ffffffff811a34cc>] iterate_supers+0x9c/0x110
    [ 1560.250628] [<ffffffff811cdf85>] sys_sync+0x35/0x90
    [ 1560.250633] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1f

    mr.MikyMaus wrote:You do know that flash memories have limited number of write cycles, right?
    Limited how? Like all storage devices have (in other words, after a while they break)?
    The drive is completely new, like 3 weeks or something.

  • 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?

  • Will Restore in Leopard Disk Utility reliably copy a drive with bootcamp?

    I have a drive partitioned part OS X and part Bootcamp (with Windows XP installed). If I use Apple's Disk Utility to 'Restore' the drive (to copy the drive to a larger drive) will this work reliably for bootcamp as well as the OS X content? Presumably this just clones the drive?

    Once you install MacFUSE you can not use the Startup Disk Utility anymore to boot into Windows, you need to hold the option key every time.
    As you stated, NTFS is owned by Microsoft, its their proprietary format and has many different versions of it. I don't think any company has the full right to format NTFS which basically comes down that you can not complain to any of the companies or MS about data loss.
    My idea with an image is that I can always read it, so in case the WinClone format or write fails I still have all my files (and not just parts of it). Since I am booted the most amount of time on Mac OS X anyway I don't care that a script creates an entire mirror image of my current Windows drive overnight.
    I actually have several basic images that I can always restore in case I want to clean up my drive.

  • HT4848 how to erase the disk utility from my usb portbalbe flash drive

    how do I  erase the disk utility from my usb portbalbe flash drive. I need the flash drive for other stuff and it isn't allowing me to do so.

    Here is information on the recovery partition, includin how to remove it from a drive: http://reviews.cnet.com/8301-13727_7-20083166-263/managing-the-os-x-10.7-lion-re store-drive/

  • How did Disk Utility make my external drive undetectable?

    Greetings all,
    It all started when I dropped a running external hard drive (WD My Book Essential) onto the floor.
    I immediately plugged the disconnected USB back into the drive and waited..
    The first pop-up said the drive could not be read so I re-plugged it.
    It worked and I could read files but it took a long time just to show those files in finder.
    There was obviously a problem with the drive so I opened up Disk Utility and clicked Verify Disk.
    When it was finished verifying I noticed it changed my disk name from "My Book" to "disk1s1." 
    I also got a message saying "This disk needs to be repaired. Click Repair Disk."
    I proceed to click Repair Disk only to end with a message saying "Disk Utility stopped repairing “disk1s1”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files."
    At this point I followed the instructions on screen and proceeded to copy files from the external drive to my internal drive.
    After pasting some files, the usual popup indicating transfer information was stuck at zero. 
    After a long time of waiting it still remained at zero so I had to force close finder and restart.
    Once I restarted the Macbook Pro, my external hard drive no longer showed up on my desktop nor Disk Utility.
    It still spins but stops after a minute.
    Below is the log from Disk Utility.
    Any help regarding this issue will be appreciated.
    2012-11-14 16:47:00 +0800: Disk Utility started.
    2012-11-14 16:49:29 +0800: Verifying volume “My Book”
    2012-11-14 16:49:29 +0800: Starting verification tool:
    2012-11-14 16:53:40 +0800: Checking file system2012-11-14 16:53:40 +0800: Checking Volume /dev/disk1s1...                                               
    2012-11-14 16:53:58 +0800: This is not an NTFS volume.                                                   
    2012-11-14 16:54:39 +0800: Error: This disk needs to be repaired. Click Repair Disk.2012-11-14 16:54:39 +0800:
    2012-11-14 16:54:39 +0800: Disk Utility stopped verifying “disk1s1”: This disk needs to be repaired. Click Repair Disk.
    2012-11-14 16:55:09 +0800:
    2012-11-14 16:55:22 +0800: Verify and Repair volume “disk1s1”
    2012-11-14 16:55:22 +0800: Starting repair tool:
    2012-11-14 16:55:22 +0800: Checking file system2012-11-14 16:55:22 +0800: Checking volume.
    2012-11-14 16:55:22 +0800: Checking main boot region.
    2012-11-14 16:55:35 +0800: Volume repair complete.2012-11-14 16:55:35 +0800: Updating boot support partitions for the volume as required.2012-11-14 16:56:14 +0800: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2012-11-14 16:56:14 +0800:
    2012-11-14 16:56:14 +0800: Disk Utility stopped repairing “disk1s1”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    2012-11-14 16:56:44 +0800:
    2012-11-14 16:58:08 +0800: Disk Utility started.
    2012-11-14 16:58:14 +0800: Eject of “WD My Book 1140 Media” succeeded
    2012-11-14 17:04:21 +0800: Eject of “WD My Book 1140 Media” failed

    In a word, it appears that the "dropped" external drive is physically damaged internally, and so can't run "Repair Disk" properly.  Time for a new external hard drive.
    Hope this helps

  • Problems with firewire drive

    Hi all.
    Ive got a problem I need help with. Just installed Final Cut 3 on this older G3. Would like to do a little editing at home. Have a 240 gig Lacie firewire drive that I would like to use as a scratch drive. The drive was originally used on a pc so I initialized it on the mack Mac OS Extended (Journaled). I can capture video to the internal Mac harddrive but not the Lacie. Capture stops after a few seconds. I have tried transfering captured video from the internal drive to the Lacie but I get an error message and it wont transfer. Any ideas what I need to do to remedy this situation?
    Thanks
    Rocky
    g3   Mac OS X (10.3)   256 mb ram

    This seems wrong. I have two firewire drives daisy-chained and then plugged into my cube, and on the other firewire port I have my cinema display's hub which leads to my ipod mini and my belkin mac mini USB and firewire hub, where I connect my DV camera for import. I have had no problems importing footage to my FW drives. I'd say don't plug the camera into the computer through the FW drive, just straight into the computer. If that doesn't work, try what the other guy said about either reinitializing it or use disk utility to check the drive and maybe verify/repair something on it.
    -Brian

  • MacBook will not start. I have restarted with original CD. I have used Utilities and "no problem" with hard drive. I have reset PRAM. I have tried safe boot. Nothing is work. Gray screen with Apple logo and rotating wheel. Thanks for any suggestions!

    MacBook will not start. I have restarted with original CD. I have used Utilities and "no problem" with hard drive. I have reset PRAM. I have tried safe boot. Nothing is work. Gray screen with Apple logo and rotating wheel. Thanks for any suggestions!

    Snow Leopard is a Mac OS X version. You say that it's the version you have in your Mac (10.6.8). Do a back up of your files, format the hard drive (using Disk Utility) and reinstall again

  • Can Lion disk utility dynamically partition a drive?

    Can Lion disk utility dynamically partition a drive? I see many posts that Leopard Disk utility can but nothing about Lion.

    Yes. I'll post a link to instructions. Be sure to create a full reliable backup before you begin (don't just do the backup, test the backup to be sure it's good), and the only application that should be running until the process is complete is Disk Utility.
    http://osxdaily.com/2009/11/20/resize-partitions-in-mac-os-x-with-disk-utility/
    Some people have problems resizing partitions because of the hidden Recovery HD partition. It sometimes gets in the way because Disk Utility can move it "up" but cannot move it "down".

  • K7N2 deltas mainboards have a problem with usb devices ??

    Ok here is my problem..
    I had installed WinXP Pro with SP1..
    I got a 20 GB USB2.0 disk.i connected it on the both front or rear usb ports.
    When i tried to transfer files to my usb disk or to my PC, in the middle of the copying, i got "Write Delay Failed" error and lost my usb connection..
    I had to plug it out and in again..
    Now, i have an DSL modem..Last night, i was disconnected from internet and my modem's lights gone..I plug it again, no lights..restarted my PC, also completely shutdown Windows XP..Again no lights..
    Then, formatted PC and installed windows 2000 Pr and SP4, until now, my modem worked fine..But USB 2.0 ports are still no use for my usb disk...
    In bios , it's enabled as USB 1.1+2.0..
    I think this K7N2 deltas have a problem with usb 2.0 devices and Win XP Pro..
    Some guys talking about, removing 9th wire earth, but couldn't understand which wire from where ? From mainboard or from usd device's cable ?
    Those cables are fabricated, i think it's impossible ?
    My processor is Athlon 2500+, ram Twinmos 512 DDR 400
    Thanks for reply

    I'm also having this problem. It's happening with my USB flash disk. I was almost buying another one when I tried it with Windows Vista on the same machine and it worked ok, then I tried Arch Linux (with kernel 2.6.30.5) on another machine and got the same error. After that I tried Ubuntu and it worked ok. Seems that Arch's kernel doesn't like my USB flash disk.
    Last edited by esdrasbeleza (2009-09-02 01:16:09)

Maybe you are looking for

  • No Photos in Photo app

    I have just setup my wife's new iPad 3.  Photo Stream is turned on in Settings but there are no photos in the Photos app, however on her iPhone 4s her photos appear in the Photo app.  When going to the Photo app it says, "There are no photos or video

  • Problem with onRelease and onRollOver

    onRelease doesn't do anything in the following. background._visible = false; area.onRollOver = function() { background._visible = true; background.onRollOut = function() { background._visible = false; background.item.onRelease = function() { trace('o

  • ITunes LP did not download off of pre-order

    I downloaded Timberlake's "20/20 Experience (Deluxe)" today..although I got the songs, the iTunes LP did not download - WHY?

  • Printer Driver off line

    I have two offices the same exact printer, HP Officejet 4630.  Both printers were set up wireless.  Every time I bring my laptp from office to office I can't print.  I have to reload the sofdtware, I get a message that the 4630 printer Driver is offl

  • "Views" column works only if excluding its posters

    "Views" column is a good idea, thanks, (and finally we would not need a "Read vs Unread" column if only the small blue dots were not SO small) but it would be nice if it showed the actual number of visits. As it is now, it mainly shows how many times