Local Network (Ethernet) Hard Disk

I have seen information suggesting that it is possible to network a large hard disk on an Ethernet network to archive graphic content so that all computers are able to access it without a server.
However, setup and software was not explained.
Also, the hard disk suggested was an HP and I am not sure that is the best. Who has had experience with such a setup? Would something like the Data Solutions 2 degrees frost (www.2degreesfrost.com) be a choice that would connect directly to ethernet?
Frank
MacBook   Mac OS X (10.4.8)   I also have a G3 and G4 iBook and a G5 Tower. The G3 runs system 9 yet.

Well, unless you have an External HDD that has an Ethernet port on it (to connect to your Router) or a USB port (to possibly try and connect to a USB port on a Router), then it can't be done with your normal equipment.
If you have a USB port with cable from an External HDD and have a USB port on your Router (mine has one, the small A type port I think, the same as our Printer's USB port) and I know that can be used to connect to the Internet/Network from computer to Router, so it has a chance of being able to connect to the Router from an External HDD.
The 2 main problems/concerns about this are that the USB port may only be 1.1 (most likely there on the Router for use as a Printer port and 2.0 speed not needed as quite a few printers have only 1.1 USB ports on them. If it worked, speed would be slow. The other problem is that if you did try this, you may not be able to get the USB port on the Router working with the External HDD as your Router may need to have a special USB Device Driver installed on the "computer" that wants to use the USB port on the Router (again, my 2Wire brand Router that I got when I signed up for AT&T (SBC) Yahoo DSL also needs this to allow the Router to recognize the connected device on the other end of the Ethernet Cable).
If your Router has a USB port that was made to be a connection for a Printer (acting as a Print Server), then you might get lucky and not need a driver for this though you may need to configure things in your Router's System Settings which may not allow anything other than a Printer, all you could do is try and see what works or not.
The main 2 ways that people connect Hard Drives to a Network (without having them being connected to a specific computer on the Network as an External or Internal Drive) is to either purchase a NAS (basically an External HDD that also includes an Ethernet port on it (and comes with cable) to attach to your Router, and usually has a couple USB ports on it as well, for another External HDD or 2 to be attached to the NAS or for Printer to act as a Print Server.
Buffalo Tech. is a pretty good brand of above average External HDDs, NAS units, SAN units and so on... I got my basic 250 GB Buffalo Tech NAS at www.tigerdirect.com for $199 back in Sept, and it is great. You can change the settings for how you want to use it, for example, you can have it automatically turn off at a certain time/turn back on at a certain time, meaning you can have it save power during your sleep hours without having to do anything. Or you can have it auto- on schedule- Backup the whole NAS drive to an attached USB HDD to always have that backup around, you can have multiple access settings as well as listed below.
You can set up different "users" and "passwords", or a specific "all" sharing folder for all allowed computers and a "windows" folder for only Windows systems to have access to, as well as having a "mac" folder for only Mac systems to access, therefore being able to sort/separate the items on the NAS by what computer systems they might be used on -universal file types can be thrown in the "all" folder for both windows and macs systems to access.
You can also let your NAS through the Settings, be able to accept FTP so that you can give someone your URL address -your ISP internet number address thingy with the network location name -computer's name or NAS's name etc- and the proper user name and password, and they can then remotely access your NAS (or whatever areas of the NAS that you let them) from anywhere that is connected to the internet.
You can also Set certain Permissions and Authorized Users for different folders on the NAS, which allows a specific person to choose to allow only certain "computers" available on the network, meaning you can create areas that are blocked from, let's say, a child's/teenager's computer so that they don't have access to any adult content stored on there that you may want access to from your computer.
Ok, that was way long. I still have one other option to list, which is basically the same as the NAS idea, except you might not get the bonuses of using an actual NAS...
You can find little units that aren't cheap (usually seen at around $70 or more) which let you take anywhere from 2-4 USB External HDDs and connect them to this unit, which then has an Ethernet Port on it which lets you connect it to your Router. The unit might also have a "built-in" print server, so that you can plug in a USB Printer to it as well. Since these units are not part of the Hard Drives, Your Router, or any Computer (all which you will need to have already, or will purchase afterwards if needed) this means that they are probably harder to have access to/control over in the way of settings... Less features available that a NAS unit might be able to do, but is cheaper than a NAS (which does come with a built-in HDD of up to 500-750GB now) and is perfect if you just want the connectivity aspect and already have 1 or more USB HDD that you want to be able to reuse in this manner.
So there are several possible options available, depending on the amount of $$ that you want to spend, what you already have and would like to use in the set-up, and if you want to try and test out the cheaper ways first to see if they work or not, or if you just want to buy something and attach it (install any needed software/drivers) etc. I will add as a note that some NAS say that they have 2 USB ports on them, which they do, but also state that you can connect up to 2 USB HDDs or a Printer to the device. This is missleading, as some (which you may only find out from the Manufacturer's Website, or in the Instructions Manual etc) can actually only handle one USB HDD and one USB Printer. The NAS I have is like this, the USB port on the back is for USB HDD only, and the front panel USB port is for USB Printer only. So no 2 USB HDD at the same time... Also, printers that will actually work as a print server through this will vary. Check the Manufacturers website (Mine was not listed, so I emailed them. They said it was not tested by them, it may work and that as long as it wasn't a multi-use printer -as in printer, scanner, copier, fax etc all in one- that it could work). I then took my question to Canon (my Printer manufacturer) and they has no idea. It ended up not working, which I suspect is because of my needing the iPixma Device Drivers to install on my computer, and the NAS can't access the drivers needed. My printer shares on the Network just fine when installed and attached to one (our main) computer, and I can even have it do an auto turn off after 15 minutes of inactivity and turn on again when needed, the only problem is then needing to have that specific computer turned on when wanting to print (or we just go and use that computer when anything needs printing...
Ok, again, waaaayy too long. Sorry about that. I tend to ramble on quite a bit, not like you haven't noticed already.

Similar Messages

  • Express and ethernet hard disk

    So I'm trying to make an ethernet hard disk wireless with my airport express. Apparently this is possible by changing some settings, but I don't really know what I'm doing. Any help or ideas would be wonderful.

    Corneillious, Welcome to the discussion area!
    Unfortunately this is only possible if a unique set of conditions are met.
    Normally the Ethernet port on the AirPort Express (AX) is NOT active. The ONLY way to make the AX's Ethernet port active is to have the AX use WDS to wirelessly join a network. This is easily done if your network is created by another AX or even an AirPort Extreme base station (AEBS). However if your wireless network is created by another device this is almost certainly not possible. Very, very, very few non-Apple devices are compatible with Apple's WDS.

  • Using an external ethernet hard disk to store music for itunes

    I would like to use an external hard disk to stiore music which then I will listen with different macs connected to the network...
    how can I do so?
    what are the setting to use on the macs?
    anuy advice on how I should copy my music from my portable to the external hard disk?
    thanks,
    luciano

    Are you wanting each machine to view those photos thru iPhoto? There are several ways of sharing and others can fill you in more on the conventional ways. Some are:
    http://ad.hominem.org/log/2005/07/acl.php
    http://www.macosxhints.com/article.php?story=20030925091034677&query=share+iphot o
    http://www.macosxhints.com/article.php?story=20030925091034677&query=share+iphot o
    Let me suggest another possible way.
    That is use iPhoto in it's alias mode on each of the machines. Then store your source files on the external HD and let each machine create an alias based library of those files. Each machine will have an independent, unique library whose edits, slideshows, etc will be unique to that machine. Those machines can only delete the alias files from their library, they can't touch the original source files. The only caveat is if the external HD is not mounted the library will only be able to be used in a limited way, viewing thumbnails, adding comments and keywords only. You can put a few photos in a folder on the external HD and create a test alias library to experiment.
    I've created some Tutorials to assist users in converting over to an alias based system.

  • Using an external ethernet hard disk to store photos

    I would like to use an external hard disk to view my photos with iphoto from different macs connected to the ethernet external hardisk
    Is it possible? and how should I set my machines?
    thanks ,
    Luciano

    Are you wanting each machine to view those photos thru iPhoto? There are several ways of sharing and others can fill you in more on the conventional ways. Some are:
    http://ad.hominem.org/log/2005/07/acl.php
    http://www.macosxhints.com/article.php?story=20030925091034677&query=share+iphot o
    http://www.macosxhints.com/article.php?story=20030925091034677&query=share+iphot o
    Let me suggest another possible way.
    That is use iPhoto in it's alias mode on each of the machines. Then store your source files on the external HD and let each machine create an alias based library of those files. Each machine will have an independent, unique library whose edits, slideshows, etc will be unique to that machine. Those machines can only delete the alias files from their library, they can't touch the original source files. The only caveat is if the external HD is not mounted the library will only be able to be used in a limited way, viewing thumbnails, adding comments and keywords only. You can put a few photos in a folder on the external HD and create a test alias library to experiment.
    I've created some Tutorials to assist users in converting over to an alias based system.

  • Is there a way to avoid a iPlanet Messaging Express home user to copy from the email message ( email content ) body and paste on to a local place( it Hard disk, for an ex )?

    Is there a way to avoid a iPlanet Messaging Express home user to copy and paste email body content and avoid attachment deliver attempts?Cause this could grant home users to take ownership of enterprise's documents, sending to them selves and after that, in their own homes, they access Messaging Express, recieve their email with the forbbiden content and then copy and paste to it's own's hard disk.

    It may be possible, but then what would prevent the user from running a "screen grabber" to capture the data. The underlying question that you need to ask is, "Who can you trust?" If you're concerned about confidential documents being stolen/disclosed, then that is where your security starts. If someone can't access a document, they can't E-mail it or transport it elsewhere. Who says they can only use E-mail? Using ftp is more efficient, or a floppy/Zip/Jazz drive could also be used. Trying to "secure" the E-mail client would be like plugging a single hole in a water pipe full of leaks. You have to shut off the water at the source.

  • Importing Local DCs from hard disk into NWDS

    Hi..
    I have a Local Webdynpro DC zipped file in my .dtc folder under a package folder (say com.sap).
    I have extracted this file under this folder.
    Now I need to extract this in my NWDS local development.
    I am not using NWDI... I am using only Local DCs.
    I want to import the file into a Webdynpro Local DC into my NWDS..
    Please provide your valuable suggestions...
    Thanks and Regards,
    Sayan Ghosh

    Hi Sayan,
    Go to the Development Configurations Perspective(Window->Open Perspective->Development Configurations)-> Local Dcs->MyComponents->here you can see all your DCs, Right click on the DC->Create Project-> DC will be created. You can see that DC in the Webdynpro Perspective.
    Or
    You can create the the new DC with the required name, once it is done then copy the src folder from the old DC to Newly created DC->Reload DC.
    Thanks n Regards,
    Jhansi Miryala

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

  • Can you use a Ethernet hard drive on a airpot express

    Can you use a ethernet hard disk on a airport express?
    such as this one?
    http://www.currys.co.uk:80/martprd/store/curpage.jsp?BV_SessionID=@@@@1258649623.1206555836@@@@&BVEngineID=cccdadedjieihldcflgceggdhhmdgmj.0&page=Accessory&sku=306727

    More than likely this is NOT possible since most Belkin routers are NOT compatible with Apple's WDS.
    However if you are using a Belkin F5D7230-4 or F5D7231 you might be able to get it to work. You need to configure the Belkin and the AirPort Express (AX) to connect wirelessly using WDS. Only then is the AX's Ethernet port enabled.

  • Compressor 4 is using all my hard disk space?!

    I have a Mac Pro, 3.7 Ghz Quad-Core Intel, 12 GB Memory.
    Im trying to compress a video from FCP X (10.1.3), but Compressor (4.1.3) is using all of my hard disk space. The video I am trying to compress has 4 one minute HD interview segments and about 100 different photos. It's a tribute video that combines both forms of media into a presentation. The total time for the video is 11:23.
    The project library itself works off an external hard drive that has 1.45 TB available. The only thing that goes locally to my hard disk are the FCP X backup folders.
    I received a message saying that I needed more Virtual Memory, but am having a hard time understanding virtual memory and how to free up more of it.
    Any advice?

    This is the message from my last attempt.

  • Window for my hard disk looks entirely different suddenly/icons gone!

    When I usually open the icon on my desktop for my hard disk (the internal hard disk), on the left-hand side is usually the standard array of icons for pictures, movies, etc. etc. (and when I open other folder icons on my desktop, I still see those same items - nothing has changed there). But when I now open the icon of the internal hard disk, all of those usual items (and the whole look and feel of the window) has changed. The only icons on the left side are network, the hard disk icon itself, and the icon for my MobileMe "air" disk (I think it's called iDisk - whatever... you probably know what I'm talking about).
    I can't figure out what happened?! I ran disk utility and it supposedly did repairs that were necessary on my system. I rebooted and restarted and even shut down entirely and then restarted again. I really miss that usual interface giving me all of those options so easily available. What's up here and how do I fix????!!

    Select Preferences from the Finder's menu, click on the Sidebar tab. Be sure what you want displayed is checked.

  • How do I set up a network hard disk so I can restart my MacBook from it?

    I have a 2TB Freecom XS Network hard disk, and I want to be able to restart my MacBook from it with my current OS, Leopard 10.5.8, when I have upgraded the OS on the MacBook to Snow Leopard 10.6.3 [as a possible precursor to Mavericks or even Yosemite]. The problem is that the MacBook doesn't recognise the XS as a network disk: the XS has been assigned an IP number, and I can mount it as a server volume, and I have copied all the system folders/files onto it, but that is no use if the system doesn't recognise it as a network disk for a restart [I've tried]. The system/library/users/applications folders are in a Macintosh HD folder as on the MacBook, but this folder is inside a root folder named PUBLIC: could this be part of the problem? I thought I might be able to reinstal the OS on the network disk using the original system installation discs, but after restarting the MacBook as instructed, the network disk isn't recognised as a destination for installing the OS. I don't want to instal Snow Leopard on the MacBook before I'm sure I can reboot it with Leopard, using the network disk.

    Hi BDAqua.
    Thank you for your reply. I don't know how much what I omitted to disclose in my original post might affect what you've told me, but I have a wireless network set up with a 500GB Time Capsule, to which a broadband router and another backup disk [1TB, daisy-chained to the TC] are connected. Given the difficulty I had initially, setting up the network [mainly because of my ineptitude where comms are concerned], I didn't want to risk connecting the Freecom drive to the TC, in case it changed the network settings [or worse, disrupt my internet access], and I haven't done it hitherto. I did try connecting the ethernet cable to the wireless router however, with neutral results: still possible to manually mount the drive as a server, and it shows in the Network folder in my MacBook's root folder.
    Further to an email from Freecom's support department [effectively just a request for part number, proof of purchase, etc.], I followed their suggestion and tried connecting the drive to the MacBook using the USB 2 cable, and the drive showed up in the device section of the Finder window sidebar, but I would guess that this option wouldn't enable the drive to function as a boot drive either? Also, unless I'm mistaken, USB offers much slower data transfer speeds than Gigabit Ethernet? I'm hoping I've not dropped a monumental bollock, because I'm positive from my pre-purchase research that Gigabit Ethernet is faster than FireWire or USB2, which is why I chose this drive over cheaper USB drives [like the 1TB Western Digital drive daisy-chained to the TC]; or am I mistaken?
    To get back to your answer though, I don't dispute what you say, because I'm sure I'm much less of an expert than you might be, but I would nevertheless like to be able to boot up from the Freecom drive, if a way to do that is possible, even if it means biting the bullet and connecting it to the Time Capsule [assuming that this will work: can you advise?], without needing to investigate and purchase additional kit. I've had a scan of the forum, and I've seen a few suggestions which mention cloning, but I don't know how this works: I presume I'd have to buy the appropriate app for that? Your answer seems to suggest installing the new OS onto an external drive [although, worryingly, you don't mention Ethernet as an option] using cloning, so I'd be grateful if you could explain that.
    I just hope that my desire to save the cost of a newer Mac of some description, be it new or refurbished, but giving me the newest OS possible on the MacBook [Yosemite, I'm guessing], doesn't end up costing me something uncomfortably similar, cumulatively.
    Any practical and reasonably-priced suggestions welcome and considered! Thanks again

  • Publish iCal calendar to local network disk?

    The Misses and I would like to share calalendars in a way other than shouting out information to one another across the room. We recently purchased a Time Capsule and would like to publish our calendars to the TC harddisk. (We did this previously with another network disk we have but used a different router to configure it)
    Based on our previous success at doing this, I presume we only need an ip address for the hard disk to set it up. I can't remember how we did this in the past and I don't want to use a program other than ical to do this.
    I just want my calendar and her calendar to publish to the disk so that we can each subscribe to the others.
    Can anyone help me with this?

    There was a previous discussion that may help. Do a search for local network shareing, but expand out to all year. This may be what you need. Haven't tried it myself yet, but it looks like it may be the answer. I have the same need as you, BTW.
    Re: Entering iCal from a network
    Posted: Mar 22, 2008 5:51 PM in response to: Fulvio Pietramala
    You need to use a product like BusySync to selectively share calendars across a network. Your present approach is guaranteed to fail, and to corrupt your event and task data.

  • How can I backup my network hard disk?

    I have Time Machine which backs up my local hard disk to a Time Capsule, no problem. However, I also have a networked hard drive, which I would like to back up to another hard drive or DVD. Is it possible to this in Mac OS X? If not, does anyone know of any (free) third-party software to do this easily?

    Did you reformat or repartition the disk before using it as your Time Machine volume? Are the previous contents on the drive different from your machine's contents? Also, please verify your OSX and state the model of your Macbook Pro.

  • Imac will not see my hard drive on start up, wants to start from network start up disk that does not exist. How to get rid of it? So there is just one choice / my hard drive.

    I have a Intel duo Imac. Everything has been running relatively smoothly for a few years now. All of a sudden my computer will not start. I get the flashing folder with a question mark.
    When I go to Start up disk in my system perfernces while the computer is on. I see 2 possible choices. One is my hard drive with the operating system shown. The other is a non-existant Network Start up disk with a question mark in it ( looks like a hard drive with a question mark and it say's its a "network start up disk).
    All I think I want to do is get rid of the Network startup with the question mark. I can not find anywhere how one can just remove an old or non existant start up disk without reformatting.
    I believe this came from a clients hard drive who had a network system on it. We no longer have that drive. It no longer exists. But a latent icon shows up in start up disk.
    When I go to change the start up disk. I can change it to either the hard drive or the network with the question mark. But when I select my hard drive and then got to restart the computer. I get the flashing folder with a question mark on start up. I have also seen the flashing globe a couple times.
    When I attempt to run disk utility from may install disk ( holding down "C" on start-up ). Disk utility does not see my hard drive. Just the Apple install disk with the disk utility on it.
    What can I do to remedy this short of re-installing? Will a program like Disk Warrior or Tech Tool help?

    Thank you. That's what I thought will need to happen.
    One more question. I tried using the Apple install disk that came with the computer. It's an OS 10.5.6 disk. It does not see my 10.6.8 system internal hard drive to repair. All it see's is itself 10.5.6 disk. Do you think I can use a 10.8+ disk utillity since that is a higher system it will see the 10.6.8. Where the 10.5.6 does not?
    I don't want to turn the computer off for fear I'll get the question mark again. P-Ram got me going last time but for how long I don't know?  It would be nice to be able to turn the computer off for the night and startup as usual to give it a rest and try to reset itself.
    Thanks for your help, I know I will eventually need to re-install. But I am in the middle of a project with tight deadlines and all I can do right now is back-up. Trying to migrate to another computer temporarily to finish the job. That's a lot of extra work in the short time also.
    Just trying to put a band-aid on it for another couple weeks.

  • Shared Hard disk is not appearing on networked computer

    I recently set up a network with my new iMac and my older iMac (both on 10.5.3). Everything was working perfectly until a couple of days ago I noticed that the primary computer's hard disk is no longer showing up when I connect the second iMac. However, my external Time Machine disk and an extra storage disk are both showing up and can be accessed from my second computer. I haven't even set up Time Machine to network and the disk is not set to be shared. I would really like to get my HD sharing again as that is where all my files are stored which I want to access on my second computer. I have deleted it and added it several times in the file sharing window on the primary computer's system preferences. It is set to read and write for my account, just as the extra disk is. I can't get it to work at all.
    As an alternative I can screen share and access the files that way but I would like to get direct access back again which I was using before.
    Any ideas as to what has happened? The older iMac has been having power problems - shutting down when going to sleep and taking several attempts to restart. I have no idea if this has in some way damaged the connection.
    Cheers,
    Mark

    Further to what I wrote a few days ago, it seems the problem was caused by starting my computer in "Safe mode". I managed the restart my computer in the normal mode and the problem was fixed. Unfortunately I can no longer start my computer at all and will have to take it in to be fixed.

Maybe you are looking for