Results 1 to 10 of 10

Thread: Mounting a BIN file image (hard disc image)

  1. #1
    Senior Member
    Join Date
    Aug 2004
    Location
    Nottingham
    Posts
    212
    Thanks
    10
    Thanked
    0 times in 0 posts

    Mounting a BIN file image (hard disc image)

    Hey all,

    I have a BIN file of 298gb which is an exact image of a hard drive I'm trying to recover.
    I had some help and created it from Linux...but I don't know how to mount it (ideally in windows).

    I'd like to mount it back to the original disc from whence it came. Does anyone know how to do it? Power ISO seems to only let me do 64gb max.

    Thanks for any help at all!!
    Martin


    AMDX2 6000+, Asus M3A78-CA, 8800GT, Freezer64 Pro, 4GB Corsair TwinX PC2-8500, 22" Belinea Widescreen, Akasa Eclipse-62, Windows 7 Pro 64bit
    MartinBlueprint.co.uk

  2. #2
    Senior Member
    Join Date
    Sep 2005
    Location
    Glasgow
    Posts
    1,469
    Thanks
    38
    Thanked
    61 times in 58 posts

    Re: Mounting a BIN file image (hard disc image)

    Try Virtual Clone drive (which will mount it as a BD-Rom drive if it works at all).

    It should read bin images without issue (though you may need to set it to look for *.* file types) though I've never tried an image of that size.

  3. Received thanks from:

    blueprint (21-09-2010)

  4. #3
    Studmuffin Flibb's Avatar
    Join Date
    Jul 2003
    Location
    Kent
    Posts
    4,904
    Thanks
    31
    Thanked
    324 times in 277 posts
    • Flibb's system
      • Motherboard:
      • Gigabyte GA-970A-UD3
      • CPU:
      • AMD FX-6300
      • Memory:
      • 16GB Crucial Ballistix DDR3 PC3-12800
      • Storage:
      • Samsung SSD 840 EVO 250G
      • Graphics card(s):
      • 3GB MSI Radeon HD 7950 Twin Frozr
      • PSU:
      • FSP
      • Operating System:
      • Win7 64bit
      • Monitor(s):
      • Deffl TFT thing

    Re: Mounting a BIN file image (hard disc image)

    winrar can open iso files, havent a clue about the maximum size

  5. #4
    Senior Member oolon's Avatar
    Join Date
    Mar 2007
    Location
    London
    Posts
    2,294
    Thanks
    150
    Thanked
    302 times in 248 posts
    • oolon's system
      • Motherboard:
      • Asus P6T6
      • CPU:
      • Xeon w3680
      • Memory:
      • 3*4GB Kingston ECC
      • Storage:
      • 160GB Intel G2 SSD
      • Graphics card(s):
      • XFX HD6970 2GB
      • PSU:
      • Corsair HX850
      • Case:
      • Antec P183
      • Operating System:
      • Windows 7 Ultimate and Centos 5
      • Monitor(s):
      • Dell 2408WFP
      • Internet:
      • Be* Unlimied 6 down/1.2 up

    Re: Mounting a BIN file image (hard disc image)

    Personally I bought a copy of disk internals efs recovery quite expensive at 120 quid however it does NTFS encrypted files also can mount drive images, scan and recover deleted ntfs files etc. They do a cheaper NTFS (unencrypted) one for ~65 quid (100 dollars) NTFS recovery.. For future it will even image your drives for you. The demo allows you to preview files so you can see if it works before you buy it.

    BTW for encrypted files you MUST know the password, however for most people who do not know the password it is just "return".
    (\__/) All I wanted in the end was world domination and a whole lot of money to spend. - NMA
    (='.*=)
    (")_(*)

  6. Received thanks from:

    blueprint (21-09-2010)

  7. #5
    Registered+
    Join Date
    Jul 2009
    Posts
    70
    Thanks
    9
    Thanked
    19 times in 16 posts

    Re: Mounting a BIN file image (hard disc image)

    Quote Originally Posted by blueprint View Post
    Hey all,

    I have a BIN file of 298gb which is an exact image of a hard drive I'm trying to recover.
    I had some help and created it from Linux...but I don't know how to mount it (ideally in windows).

    I'd like to mount it back to the original disc from whence it came. Does anyone know how to do it? Power ISO seems to only let me do 64gb max.

    Thanks for any help at all!!
    Mount it, or write it back to the original disk?

    mount it:

    # mount -o loop,offset=32256 whatever.bin /some/directory

    then browse to some directory (please note that the offset doesn't have to be 32256, but I have never seen it as anything else...)

    *assuming* that it's the same disk and you took a raw dump of the *whole* disk, then you can use this to write it back:

    # dd if=whaterver.bin of=/dev/sdX

    /dev/sdX is your original disk, replace X with the disk id (e.g. /dev/sda for your first sata disk). It helps if the disk you're writing to is not already mounted, so you might want to use a linux live cd. **disclaimer** If you don't know which disk is which, you can use "fdisk -l" as root to help you.

  8. Received thanks from:

    blueprint (21-09-2010)

  9. #6
    Senior Member oolon's Avatar
    Join Date
    Mar 2007
    Location
    London
    Posts
    2,294
    Thanks
    150
    Thanked
    302 times in 248 posts
    • oolon's system
      • Motherboard:
      • Asus P6T6
      • CPU:
      • Xeon w3680
      • Memory:
      • 3*4GB Kingston ECC
      • Storage:
      • 160GB Intel G2 SSD
      • Graphics card(s):
      • XFX HD6970 2GB
      • PSU:
      • Corsair HX850
      • Case:
      • Antec P183
      • Operating System:
      • Windows 7 Ultimate and Centos 5
      • Monitor(s):
      • Dell 2408WFP
      • Internet:
      • Be* Unlimied 6 down/1.2 up

    Re: Mounting a BIN file image (hard disc image)

    The OP does not appear to use linux just states a friend imaged it using linux. I prefer to use kpartx so I can access all the partitions on the disk without having to guess at the offset.

    losetup loop4 <name of my file>
    kpartx /dev/loop4
    fdisk -l /dev/loop4

    if you want to mount the first partition do this.
    mkdir /t
    mount /dev/mapper/loop4p1 /t
    (\__/) All I wanted in the end was world domination and a whole lot of money to spend. - NMA
    (='.*=)
    (")_(*)

  10. #7
    Senior Member
    Join Date
    Aug 2004
    Location
    Nottingham
    Posts
    212
    Thanks
    10
    Thanked
    0 times in 0 posts

    Re: Mounting a BIN file image (hard disc image)

    ok, I'll try those suggestions. And yes, I actually meant writing it back to the original disc.
    I only have limited familiarity with the Linux terminal, but I'll try those steps you mentioned.

    Thanks for all the input.
    Martin


    AMDX2 6000+, Asus M3A78-CA, 8800GT, Freezer64 Pro, 4GB Corsair TwinX PC2-8500, 22" Belinea Widescreen, Akasa Eclipse-62, Windows 7 Pro 64bit
    MartinBlueprint.co.uk

  11. #8
    Registered+
    Join Date
    Jul 2009
    Posts
    70
    Thanks
    9
    Thanked
    19 times in 16 posts

    Re: Mounting a BIN file image (hard disc image)

    Quote Originally Posted by oolon View Post
    The OP does not appear to use linux just states a friend imaged it using linux. I prefer to use kpartx so I can access all the partitions on the disk without having to guess at the offset.
    I read it as OP imaged it himself with some help (perhaps from an online forum?).. I also noticed the statement "ideally in Windows", however as I had the suggestion had been made that OP had at least used linux before, I gave solutions which fit the criteria. Incidentally, my suggestions are substantially cheaper than £65 or £120, but it's not my wallet at the end of the day.

    You also don't have to guess the offset, you can calculate it like so:
    Code:
    # fdisk -l
    
    Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
    <SNIP>
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1              63  2930272064  1465136001   fd  Linux raid autodetect
    
    Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
    <SNIP>
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1              63  2930272064  1465136001   fd  Linux raid autodetect
    
    Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
    <SNIP>
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdc1              63  2930272064  1465136001   fd  Linux raid autodetect
    
    Disk /dev/sdd: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0b0b0b0b
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdd1   *          63      192779       96358+  83  Linux
    /dev/sdd2          192780     4192964     2000092+  82  Linux swap / Solaris
    /dev/sdd3         4192965   156296384    76051710   83  Linux
    
    Disk /dev/md0: 3000.6 GB, 3000598396928 bytes
    <SNIP>
    Now... 63 (start) * 512 (sector size) = 32256, and as it's a full disk image (i.e. not a partition) that OP is trying to recover, then we can assume that 32256 is correct (yes, assumption is the mother of all screw ups), but hey - it doesn't matter anyway as OP is going to image it back to disk.

    @OP using dd should work fine for you, but it will take a while and it will have no visual output. Also, as you mentioned that the image was taken as a recovery step, it may be worthwhile using the noerror and sync options for dd.

    # fdisk -l

    (you'll get a similar output to what I posted above - e.g. my root drive above is the 80GB one and I have three identical 1.5TB disks + a 3TB virtual disk. If you can't pinpoint the disk you're after, then it might be an idea to power down and pull the cables from the other disks)

    # dd if=diskimage.bin of=/dev/sda conv=noerror,sync

    (/dev/sda is the first disk, so again, **check this is the one you want - dd will not ask you if you're sure** noerror,sync means that dd doesn't fail on write and if it does come across a bad block, it keeps the filesystem synced).

    If you open another terminal and issue the command:

    # killall -s USR1 dd

    then go back to the terminal running dd, it should give you an output similar to the below (giving you a rough idea of how long it is taking).

    Code:
    2778143+0 records in
    2778143+0 records out
    1422409216 bytes (1.4 GB) copied, 8.79078 s, 162 MB/s
    (note - the "#" at the start of a command denotes running with elevated privileges, e.g. using "su" or "sudo")

  12. Received thanks from:

    blueprint (21-09-2010)

  13. #9
    Senior Member
    Join Date
    Aug 2004
    Location
    Nottingham
    Posts
    212
    Thanks
    10
    Thanked
    0 times in 0 posts

    Re: Mounting a BIN file image (hard disc image)

    OK.
    Ive tried these options as best I know how.

    @Skinleech That Slysoft clone drive won't accept the BIN file. It seems to think it's corrupt, so won't mount it to a virtual CD-rom drive

    @walls I don't know what an offset is BTW. I did try fdisk -l and just fdisk on its own and Terminal couldnt recognise the command.

    If I tell you that I dont know how to change directory to the place it's in, hopefully that gives you an idea of how familiar I am.
    The BIN file is at H:\bin\recovered.bin
    The name of the USB drive I want to extract it back to is sde and has one parition on it (sde1)

    Does that make this easier? I think I'm right in saying this BIN file may have the original errors on it too, so it would be good if those could be ignored or even omitted?

    Thanks for all help so far...
    Martin


    AMDX2 6000+, Asus M3A78-CA, 8800GT, Freezer64 Pro, 4GB Corsair TwinX PC2-8500, 22" Belinea Widescreen, Akasa Eclipse-62, Windows 7 Pro 64bit
    MartinBlueprint.co.uk

  14. #10
    Registered+
    Join Date
    Jul 2009
    Posts
    70
    Thanks
    9
    Thanked
    19 times in 16 posts

    Re: Mounting a BIN file image (hard disc image)

    You won't need to worry about the offset (essentially just the distance to the start of the partition that we want to recover) as we're not planning on mounting it.

    As it turns out: we can probably use dd in windows, but you'll need to get a copy that has been compiled for windows:
    gui based
    cli based

    I've never used either, so try your hand at the gui version, if that doesn't work out for you, the cli version syntax is as I've written above, except I assume it will be G: (or whatever your brive is) instead of /dev/sde - so probably something along the lines of
    Code:
    dd if=H:\bin\recovered.bin of=g:\ conv=noerror,sync
    But you'll need to confirm the windows syntax yourself.

    You're absolutely correct, the image is likely to have the original errors, but the "noerror,sync" options should work around that (hoping that any bad blocks were unused/useless areas).

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 63
    Last Post: 14-11-2011, 09:17 AM
  2. file eating monster: virus, XP or hard drive
    By justravis in forum PC Hardware and Components
    Replies: 16
    Last Post: 26-02-2009, 02:58 AM
  3. best disk cloning software?
    By DsW in forum Software
    Replies: 30
    Last Post: 02-07-2008, 09:01 PM
  4. Looking for a Database Programmer
    By tillyoubreakit in forum Software
    Replies: 35
    Last Post: 25-04-2004, 05:00 PM
  5. New hard disc decisions –
    By dgr in forum PC Hardware and Components
    Replies: 22
    Last Post: 07-08-2003, 09:38 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •