Migrating to a mac with a smaller hard disk size?

I would like to migrate from an iMac (991/1000 GB used) to a MBP Retina (OSX partition 115/150 GB used). I am selling my iMac and would like to "import" my entire system from my iMac onto my MBP. I have a 3 TB external drive. What is the best way to approach this?

There's simply no way to fit 991GB onto a 150GB drive, as you're aware, so there's no way to import your entire system from the old drive to the new.
You could partition your 3TB drive with a 1TB partition and clone your old drive onto the partition, but you're still going to need to reinstall applications anew and then move whatever user data you can fit onto your smaller drive. Why? Because your root Library and your user Library and even your System folder contain support files that may not be compatible with your new system.
If I were you, I would then use the 1TB partition as 'working' space and the remaining 2TB as a Time Machine backup drive. But then, I'm crazy for backups because my data is too precious to lose.
Good luck,
Clinton
MacBook Pro (15” Late 2011), OS X Yosemite 10.10, 16GB Crucial RAM, 960GB M500 Crucial SSD, 27” Apple Thunderbolt Display

Similar Messages

  • Time Machine backup created on Mac with a large hard disk. What happens when restore to MacBook Air with small SSD drive?

    What if a Time Machine backup was created on a Mac with a large hard disk, e.g. 500GB iMac - and I buy a new MacBook Air with a small SSD hard disk e.g 128GB. What happens when I need to use the larger Time Machine file to set up the new MacBook Air? What happens to all those files that can't fit on the smaller SSD drive?

    It is not the HD size, but rather the size of the data it contains. If you right-click your 500GB drive and select "Get Info" you can see how much is actually being used.
    Naturally if you are using more space than the new drive has, then you have to make some choices about what you want to keep and what you want to keep archived.
    I don't know what options are available but you may simply have to do a manual restore of files you want, in groups.

  • Have photoshop cs6 for windows and am now migrating to a mac with Yosemite installed.  Where can I download the cs6 for mac? And can I use the same serial no that  I received for windows.

    Have photoshop cs6 for windows and am now migrating to a mac with Yosemite installed. 
    Where can I download the cs6 for mac? And can I use the same serial no that  I received for windows.

    You need to run a platform swap:
    Order product | Platform, language swap
    Until it's through, you can use the trial version.
    Download CS6 products
    Mylenium

  • Sync a folder on my Mac with an external hard drive

    Is it possible to use the time machine to sync a folder on my Mac with an external hard drive?

    Not using time Machine.
    I use ChronoSync. Works great for me.
    http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html

  • HT1338 My mac Mini shows full hard disk when it is not really full. Shows some free space upon start up that gradually disappears without doing anything with the Mac.

    My Mac shows a full hard disk even though the disk is not full. There are several GB of unused space if I add the sizes of all the folders in the disk. Under the disk info window the free space shrinks to zero after a short period of time. It shows more space upon restart, but then it shrinks eventually to zero space available. is there a way to solve this?

    OmniDisksweeper can help you find what's hogging your disk space.

  • HT5945 maverick make my mac can't detect hard disk

    after I've installed maverick, my mac cannot detect my hard disk. what should i do to allow my mac to be able to use the hard disk? My hard disk is TRANSCEND

    I am having the exact same problem with my Belkin hub after upgrading to Mountain Lion.  The only temporary fix is to shutdown and restart the computer.  It then works again, but then for some reason after awhile it stops working again and you have to shut down again.  Strange.  Any possible permanent fix?

  • I am running iTunes on an IBM comp system Win XP with a 70gb hard disk. I have 4 kids with 4 IPOD Touches. Their apps and album art are eating up the hard disk space. I changed the Media Folder to an external hard disk. How do I get the apps to go their?

    I am running iTunes on an IBM compatible system running Windows XP with a relatively small hard disk (70gb). I have 4 kids with 4 IPOD Touches, multiple IPOD Nanos, etc. Their apps and album art are eating up the hard disk space. I changed the Media Folder through Edit, Prferences, Advances, iTunes Media Folder to an external hard disk. The new music downloads and purchases go there but the apps and other items do not. How do I get the apps and other iTunes software and downloads to go to the external hard disk

    There is no built in function to make this happen.
    Your options are:
    Upgrade the existing hard drive.
    Try creating a link for the app folder on the external drive... this may or may not work.
    Realistically, a larger hard drive is a better solution, then use the external drive for keeping a backup of the ENTIRE iTunes folder and any other personal data on the system.

  • I have purchased a macbook air with 64 gb hard disk. the available space is only 10gb. With this available space, i can't use the system effectively. kindly advise.

    I have purchased a macbook air with 64 gb hard disk. the available space is only 10gb. With this available space, i can't use the system effectively. kindly advise.

    You should have bought one with a larger SSD. You can regain some space by disabling the sleepimage file:
    To disable safe sleep, run the two following commands in Terminal:
    $ sudo pmset -a hibernatemode 0
    $ sudo nvram "use-nvramrc?"=false
    When done, restart your computer. Now go delete the file "/private/var/vm/sleepimage" to free up some hard drive space. When you put your computer to sleep it, should happen in under five seconds; my MacBook now goes to sleep in two seconds.
    [robg adds: To state the obvious, with safe sleep disabled, a total power loss will wipe out whatever was open on your machine. To enable safe sleep mode again, repeat the above commands, but change hibernatemode 0 on the first line to hibernatemode 3, and =false to =true on the second line. You'll then need to reboot again. Personally, I prefer the safe sleep mode, even with the slower sleep time and hard drive consumption -- even if for no other reason than it's great when changing batteries on a flight.]
    You can also delete unneeded files:
    Freeing Up Space on The Hard Drive
      1. See Lion/Mountain Lion's Storage Display.
      2. You can remove data from your Home folder except for the /Home/Library/ folder.
      3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
      4. Also see Freeing space on your Mac OS X startup disk.
      5. See Where did my Disk Space go?.
      6. See The Storage Display.
    You must Empty the Trash in order to recover the space they occupied on the hard drive.
    You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
    Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.

  • My 3 apple products, an imac, a macbook air and a macbook lost their contact with their external hard disks. They were LaCie make. And every time I turn my laptops, I find the positions of the keys on their  keyboards changed.  Why is Apple silent?

    After the latest apple IOS upgrade my 3 apple products, an imac, a macbook air and a macbook, lost their contact with their external hard disks. They were LaCie make. And every time I turn my laptops, I find the positions of the keys on their  keyboards changed.  Why is Apple silent? There are so many people complaining about this issue and expecting Apple to correct this issue that they have created.

    Probably because it's not an Apple issue. I have Lacie EHD's connected to my MBAir and iMac, all work perfectly on Mavericks. In addition I don't have any keyboard issues on any of my Apple products. BTW IOS is only for IOS devices such as iPads, iPods and iPhones, Macs use OS X. The two OS's are seperate  products designed to run on seperate products.

  • DV9000 Maximum Hard Disk Size Supported?

    I'm searching for a used HP Pavilion DV9000.  I need to know the maximum hard disk size the DV9000 series laptops support.  To be clear, could I put a 750G or 1TB disk in each bay?
    HP's web site isn't helpful. It gives only the "official" numbers at time of release which state it supports up to 240G, 120 in each bay. Those kinds of numbers are almost never an accurate statement of the limitation as I have seen similar "official" numbers for other HP laptops (supposedly limited to 120G or 250G or whatever) that have no problem supporting 640G in the real world.
    The size of hard disk a computer supports is usually a function of the main board's chipset and I don't know how to determine the exact chipset or find the chipset's hard disk support capability. Again, HP's web site isn't helpful here either. They may list it has an nVidia chipset; but, they don't mention which nVidia chipset.
    To be clear, I don't own a DV9000 yet and I need to know how to find this information maybe with the exact model number. The model series may be DV9000; but, there are dozens of more exacting model numbers on the bottoms of the DV9000 series computers (example: DV9025ea).  I don't want to purchase a DV9000 and then find that its limitation really is 120G per bay.

    Hard drive size is a limitation of the Bios, not the chipset, this was overcome with the implementation of Large Block Addressing 48bit in modern bios's in 2003
    Hp does not state which bios's on older laptops support this or not.
    Looking at the production dates of the 9000 series, I would be willing to bet it supports any size hard drive (48bit LBA), since 48bit LBA was introduced in 2003
    http://en.wikipedia.org/wiki/Logical_block_addressing
    That being said, there could be brand compatibility issues, so be sure to buy the hard drives from a source that has a friendly return policy.
    Maybe some one can post that has actually installed a large hard drive in a 9000 series.

  • Does Labview RT 8.5 impose a limit on FAT32 partition / hard disk size?

    We will be using a PXI RT system (spec below) to collect, analyse and store a
    large amount of data (~30 to 40GB per experiment).
    We don't want to keep the Windows host PXI attached
    and so the RT PXI must be able to store all the data from an
    experiment.
    It would be desirable to keep data from all
    experiments on the H/D, so a capacity of ~300GB would be useful.
    Q: Is there a limit on the hard disk size imposed by the Labview RT 8.5 Operating System and if so what is
    it?
    An older
    post (~2005) suggests that the partitioning tool limited FAT32 partitions to 32GB.
    Thus the question I'm asking that if I created a large FAT32 partition with
    a third party tool could I install and run Labview RT
    8.5?
    Q: Is there any other way of connecting a
    large capacity H/D to the RT System?  For example using H/D partitions, slave H/D. Other
    ideas?
    Thanks,
    Michael
    NI-1000B with
    NI-8176 embedded controller
    PIII
    1.266MHz
    128MB RAM
    Labview RT
    8.5
    Solved!
    Go to Solution.

    > The size limitation has nothing to do with
    the LabVIEW RT OS. FAT32 limits you to 32GB. This cannot be changed since it's a
    limitation of the file system format.
    Thanks for
    reply.
    I have, however, gained the impression from a
    number of web sites that there isn't a 32GB partition limit on FAT32 -- see [**]
    below -- but the limit is with the
    partitioning tool.  It looks like the
    partitioning tool that comes with RT has a 32GB limit (Is that correct?). Hence
    my question if you were able to create a large FAT32 partition could you install
    and run RT?
    Regards,
    Michael
    [**] The following was copied from http://en.wikipedia.org/wiki/File_Allocation_Table#FAT32
    Windows 2000 and Windows XP can read and write to
    FAT32 file systems of any size, but the format program included in Windows 2000
    and higher can only create FAT32 file systems of 32 GiB or less. ... This
    limitation can be bypassed by using third-party formatting
    utilities.

  • How to move all or partial data from Mac to an external hard disk?

    Hei,
    I need to learn how to move the movies/projects/events from mac hard drive to another external hard drive.
    So basically, I have always imported all events from my video camera (the original clips) to iMovie located in my MacBook Pro hard drive. But after videoing for one year, the hard disc is starting to get full, and I cannot continue using only the laptop's hard drive.
    So I would like to move part OR all of my iMovie related stuff to another external disk drive (connected with USB wire). How do I do that? Is it possible to have some events located in Mac's own hard drive, and some clips/projects in the external hard disk? How to arrange all this?
    I know that "projects" are linked to the original event clips, so if I would be able to export some part of my iMovie data to the external hard drive, I should export both, for example, everything from the same year (the events) which is linked to the projects that are using those data.
    Any tips would be greatly appreciated.

    ok First with IM9, you can easily move stuff around. Here are some lessons learned from my experience managing projects across 6 different drives.
    1. All Drives must be formatted macos extended journaled
    2. The large terabyte drives are great for long term storage of events
    3. When you are working on a project, if possible, try to move the clips the current clips you will need to your internal hard drive. This is only necessary if you care about any time machine back ups.
    4. I have also worked on project straight from the external drives. I also use portable drives such as WD passports. These are small 500 gig drives that can travel with you. I have three of those. LOVE THEM.
    5. One way to move projects and clips and keep things organized is to move the project using command drag. It will ask, do you want to move just the project or project and clips. Then voila all clips and project are then moved to that drive!
    6. REMEMBER...MOVE WITHIN IMOVIE using COMMAND Drag. NEVER EVER USE THE FINDER. This is for both projects and events. Using the Command Key will ensure the projects are moved and not just copied!
    7. Last but not least, if you have changed the dates of events using change date function in imovie....For some reason, there is a bug. It inconsistently will change the date. Don't know why and have reported the issue, but it is still not fixed!
    But its still a great little app!

  • How do I copy my time machine back up from a smaller Hard disk to a larger hard disk; so that I can then continue to back up, through Time machine, on the larger hard disk?

    I am using time machine for backing up on an external hard disk. This has now become full and every back up results in the deletion of the first back up on the hard drive.
    I have bought a larger hard drive now and am trying to copy the back up from the smaller hard drive to the new larger hard drive, using Finder. This is not happening and the message I am getting is
    "The volume has the wrong case sensitivity for a back up"

    Hello UmeshNB,
    Thanks for the question. Based on what you stated, it seems like you are not able to move a backup to another drive. I would recommend that you read this article, it may be able to help you isolate or resolve the issue.
    Time Machine: How to transfer backups from the current backup drive to a new backup drive - Apple Support
    If it is not formatted as Mac OS Extended (Journaled), reformat the drive as Mac OS Extended (Journaled) with a GUID partition. If you do not know how, see the steps in this article. 
    If the drive is formatted as Mac OS Extended but without journaling, OS X may state that "the volume has the wrong case sensitivity" to be used as a back up disk.
    Thanks for using Apple Support Communities.
    Cheers,
    Mario

  • Issue with amount of Hard Disk allocated to User

    I have recently come across an unexpected issue that I have managed to work around but not in a way that is particularly satisfactory.
    Using iMovie I was alarmed to see that on uploading about an hour of video that I was rapidly running out of hard disk space. This was odd as I had previously simply used Migration Assistant to migrate from my old iMac with a 30Gb drive to a new iMac with a 500Gb drive and as far as I could see my tape was using a maximum of 13Gb. ie I should have about 400Gb as a minimum available on my Hard Drive. Thinking it must be a glitch that iMovie was incorrectly reading the amount of space available i continued with what I was doing only for the whole thing to stop due to lack of available space.
    Having checked my hard drive I realised that I did have the space however my user account (File Vaulted Protected) only has 10Gb allocated to it. By moving the file out of my user account to the general drive (through copying first and then deleting the original) I was able to continue the project as well as regain disk space in my user account.
    It would appear that in using file vault I have in effect partitioned my disk which was not what I had anticipated; I am now in the dubious position of having to work on very large files outside of security provided by File Vault.
    Have I got this right and if so is there someway that I can allocate more space to my user account? (I am the only one using the iMac and so having the whole HD available to my user account would be ideal).
    Thanks in advance for any help.

    VK I tried the solution you suggested but it would not allow me to turn off File Vault. The message I got was that I had insufficient hard disk space to turn off File Vault (It states that I need 76Gb of space but at the moment I have less than 6Gb available - this is in spite of the fact I have 350Gb available overall on my Hard Drive.
    I suspect the only way I am going to solve this is through radical measures, however if anyone else has come across this before and solved it your input would be appreciated.

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

Maybe you are looking for