[SOLVED] How to recover removed partition?

Hello.
I had 600 GB usb drive with a lot of information. It's structure was created via Palimpsest program in a such way:
1)Format drive
  1a)Scheme: Don't partiton. Click: Format.
  1b)Are you shure? Click: Format.
2)Format volume.
  2a)Type: Ext4.  Click: Format.
  2b)Are you shure? Click: Format.
So, it hasn't partitions as /dev/sdc1, /dev/sdc2 etc, but entire device partition /dev/sdc.
Accidentally, when I decided to format another 8 GB usb-stick in the same way, I applied steps 1-1a-1b on 600 GB usb drive. So the drive was cleaned. But the data is still on it, because this steps are concerning partition table (it takes some seconds), and not disk content.
Are any ways to return everything in original state?
I tried testdisk, bit it doesn't find any files.
Thanks for possible help.
Last edited by roina (2011-11-21 16:48:56)

Nevertheless I solved this problem. Yes, testdisk didn't find any files on the drive, but it correctly determine the type of the previously deleted partition (ext4) and wrote the recipe for forthcoming actions "fsck.ext4 -p -b superblock -B blocksize device". I substituted my options:
fsck.ext4 -b 32768 -B 4096 /dev/sdd
and restored etherything. I checked this method on another USB-stick by comparison of md5sums bethore deletion and after restoration: they were identical.
During finding solution I also tested one program for windows which was also capable for undeliting in this situation, but it's free version undeleted only files less than 64kB. So the first described method works perfect.

Similar Messages

  • Due to reinstallation of mac 2nd partition is nt showing how to recover the partition and data

    Due to reinstallation of mac 2nd partition is nt showing how to recover the partition and data

    If you have no backup your only option is to perform incomplete recovery (point-in-time recovery) to the time just before the drop, export the table and then restore the database (for example, from a cold backup taken just before the incomplete recovery,) and import the table. This obviously requires a full backup
    taken before the drop which you don't seem to have, so the answer is "regrettably no."
    If you have a backup;
    Take backup of ur current db, apply previous day backup, do point in time recovery to get table back,export table, shutdown and apply latest backup, import table back
    Regards,

  • How do I remove partitions "PV2" and "Boot Camp"?

    I tried installing Windows 7 in Boot Camp and lost power during install. I want to completely start over but have partitions "PV2" and "Boot Camp" that I can't seem to remove. I have tried to remove partitions in Disk Utility but everything is grayed out. Boot Camp Assistant says "The disk appears to have been partitioned by another utility and can't be removed."

    When I boot to recovery (Command+R) it gives me four options: Restore with Time Machine Backup, Reinstall OS X, Get Help Online, and Disk Utility. I am assuming I should erase the drives usings Disk Utility. I am able to select the PV2 and Boot Camp but when I select the "partition" tab the +/- buttons on the bottom is grayed out. I am not sure how exactly to "erase the entire drive." If you couldn't tell, I am a novice imac owner. I did make a backup using Time Machine earlier today. 

  • [solved] How to recoved data off a masacred filesystem

    I'm in trouble. I am trying to recover my main data partition. Here's how it happened:
    sdb1 - 680gb primary partition, ext4, around 300gb of data on it
    sdb2 - 60gb primary partition, ext4, for backing up system from sda1 with rsync
    Yesterday, while doing rsync backup on sdb2, I run gparted, which indicated that it cannot read partition table on sdb and displayed the whole of it as unallocated. I know that when I run gparted 30 earlier, the partition was still vissible.
    Nevertheless, I thought that's because of rsync and I thought reboot would fix that, because sdb1 was still mounted, and I was accessing all the data on it with no issues.
    When rsync was done, I rebooted an that was the last time I saw my data.
    Automounting during boot gives me:
    superblock could not be read or does not describe correct ext2 filesystem...
    So I tried to run
    $ sudo fsck.ext4 -p -b 98304 -B 4096 /dev/sdb
    fsck.ext4: Bad magic number in super-block while trying to open /dev/sdb
    /dev/sdb:
    The superblock could not be read or does not describe a correct ext2
    filesystem. If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    $ sudo e2fsck -b 8193 /dev/sdb
    [sudo] password for juha:
    e2fsck 1.42.8 (20-Jun-2013)
    e2fsck: Bad magic number in super-block while trying to open /dev/sdb
    The superblock could not be read or does not describe a correct ext2
    filesystem. If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    I tried the same command with all superblock backups that were listed.
    $ sudo fsck -n /dev/sdb1
    fsck from util-linux 2.24
    e2fsck 1.42.8 (20-Jun-2013)
    ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
    fsck.ext4: Group descriptors look bad... trying backup blocks...
    fsck.ext4: Bad magic number in super-block while using the backup blocksfsck.ext4: going back to original superblock
    Superblock has an invalid journal (inode 8).
    Clear? no
    fsck.ext4: Illegal inode number while checking ext3 journal for /dev/sdb1
    /dev/sdb1: ********** WARNING: Filesystem still has errors **********
    I also run testdisk to see if it can find data from sdb1.
    It finds the partition (partition type is automatically selected as None) but it finds no files on sdb1, even after deep search.
    It does find data on sdb2, but that's just system partition backup I don't care about at this point.
    Also, just now I run this
    ]$ sudo fsck.ext4 -v /dev/sdb1
    e2fsck 1.42.8 (20-Jun-2013)
    ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
    fsck.ext4: Group descriptors look bad... trying backup blocks...
    fsck.ext4: Bad magic number in super-block while using the backup blocksfsck.ext4: going back to original superblock
    Superblock has an invalid journal (inode 8).
    Clear<y>? yes
    *** ext3 journal has been deleted - filesystem is now ext2 only ***
    Note: if several inode or block bitmap blocks or part
    of the inode table require relocation, you may wish to try
    running e2fsck with the '-b 32768' option first. The problem
    may lie only with the primary block group descriptors, and
    the backup block group descriptors may be OK.
    Block bitmap for group 256 is not in group. (block 1268396107)
    Relocate<y>? yes
    Inode bitmap for group 256 is not in group. (block 1125246092)
    Relocate<y>? yes
    Inode table for group 256 is not in group. (block 2088878841)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    One or more block group descriptor checksums are invalid. Fix<y>? yes
    Group descriptor 256 checksum is 0x6349, should be 0x9abd. FIXED.
    Inode bitmap for group 257 is not in group. (block 2837529440)
    Relocate<y>? yes
    Inode table for group 257 is not in group. (block 2199953455)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 257 checksum is 0x02d4, should be 0xd13d. FIXED.
    Block bitmap for group 258 is not in group. (block 3896597355)
    Relocate<y>? yes
    Inode bitmap for group 258 is not in group. (block 2097244160)
    Relocate<y>? yes
    Inode table for group 258 is not in group. (block 2609271215)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 258 checksum is 0xee91, should be 0xc246. FIXED.
    Block bitmap for group 259 is not in group. (block 805546298)
    Relocate<y>? yes
    Inode bitmap for group 259 is not in group. (block 3538423854)
    Relocate<y>? yes
    Inode table for group 259 is not in group. (block 2924444292)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 259 checksum is 0xc190, should be 0x4c0d. FIXED.
    Block bitmap for group 260 is not in group. (block 338739984)
    Relocate<y>? yes
    Inode bitmap for group 260 is not in group. (block 902864749)
    Relocate<y>? yes
    Inode table for group 260 is not in group. (block 1901539298)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 260 checksum is 0xac76, should be 0xac63. FIXED.
    Block bitmap for group 261 is not in group. (block 1660969779)
    Relocate<y>? yes
    Inode bitmap for group 261 is not in group. (block 209743725)
    Relocate<y>? yes
    Inode table for group 261 is not in group. (block 879935846)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 261 checksum is 0x800e, should be 0x8fa5. FIXED.
    Block bitmap for group 262 is not in group. (block 1705519300)
    Relocate<y>? yes
    Inode bitmap for group 262 is not in group. (block 1360743755)
    Relocate<y>? yes
    Inode table for group 262 is not in group. (block 4107065764)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 262 checksum is 0xc00d, should be 0xe8f3. FIXED.
    Inode bitmap for group 263 is not in group. (block 2205583287)
    Relocate<y>? yes
    Inode table for group 263 is not in group. (block 3636737468)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? yes
    Group descriptor 263 checksum is 0x69a9, should be 0xb9a9. FIXED.
    Block bitmap for group 264 is not in group. (block 1471470759)
    Relocate<y>? yes
    Inode bitmap for group 264 is not in group. (block 1725839977)
    Relocate<y>? yes
    Inode table for group 264 is not in group. (block 2144458553)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 264 checksum is 0xcd09, should be 0xea3a. FIXED.
    Block bitmap for group 265 is not in group. (block 3617231787)
    Relocate<y>? yes
    Inode bitmap for group 265 is not in group. (block 2640198439)
    Relocate<y>? yes
    Inode table for group 265 is not in group. (block 2725347176)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 265 checksum is 0xbbb8, should be 0xb870. FIXED.
    Block bitmap for group 266 is not in group. (block 1840499818)
    Relocate<y>? yes
    Inode bitmap for group 266 is not in group. (block 3698703324)
    Relocate<y>? yes
    Inode table for group 266 is not in group. (block 2882301371)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 266 checksum is 0xb3c9, should be 0x72d5. FIXED.
    Block bitmap for group 267 is not in group. (block 1968099309)
    Relocate<y>? yes
    Inode bitmap for group 267 is not in group. (block 2125019324)
    Relocate<y>? yes
    Inode table for group 267 is not in group. (block 2616321653)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 267 checksum is 0x72bb, should be 0xc66c. FIXED.
    Block bitmap for group 268 is not in group. (block 3197564106)
    Relocate<y>? yes
    Inode bitmap for group 268 is not in group. (block 1173679527)
    Relocate<y>? yes
    Inode table for group 268 is not in group. (block 3081059840)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 268 checksum is 0xee4e, should be 0x6c67. FIXED.
    Block bitmap for group 269 is not in group. (block 467880860)
    Relocate<y>? yes
    Inode bitmap for group 269 is not in group. (block 3461842583)
    Relocate<y>? yes
    Inode table for group 269 is not in group. (block 903401461)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 269 checksum is 0x701d, should be 0x1735. FIXED.
    Block bitmap for group 270 is not in group. (block 1737084563)
    Relocate<y>? yes
    Inode bitmap for group 270 is not in group. (block 1617385180)
    Relocate<y>? yes
    Inode table for group 270 is not in group. (block 3944519733)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 270 checksum is 0x1c78, should be 0x9f4e. FIXED.
    Block bitmap for group 271 is not in group. (block 3558332121)
    Relocate<y>? yes
    Inode bitmap for group 271 is not in group. (block 1481837154)
    Relocate<y>? yes
    Inode table for group 271 is not in group. (block 1108213120)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 271 checksum is 0x3066, should be 0xce01. FIXED.
    Block bitmap for group 272 is not in group. (block 3294840462)
    Relocate<y>? yes
    Inode bitmap for group 272 is not in group. (block 1680662834)
    Relocate<y>? yes
    Inode table for group 272 is not in group. (block 747037043)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? no
    Group descriptor 272 checksum is 0x7d96, should be 0xde7a. FIXED.
    Block bitmap for group 273 is not in group. (block 805709209)
    Relocate<y>? cancelled!
    Inode bitmap for group 273 is not in group. (block 220354588)
    Relocate<y>? cancelled!
    Inode table for group 273 is not in group. (block 281430039)
    WARNING: SEVERE DATA LOSS POSSIBLE.
    Relocate<y>? cancelled!
    Group descriptor 273 checksum is 0xa378, should be 0x6f41. FIXED.
    /dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
    /dev/sdb1: ********** WARNING: Filesystem still has errors **********
    But as you can see, I chickened out on "SEVERE DATA LOSS POSSIBLE" warnings, and after few repeats, I just hit ctrl+c not sure if I should even touch that.
    What should I do here?
    Last edited by Lockheed (2013-12-19 17:27:12)

    The image is decompressed and takes 650GB, which is as much as the partition was on the drive. But I had not enough free space, so I had to save that image on the drive which had the original partition on it.
    I tried to check for locations of superblock:
    $ dumpe2fs /mnt/Disk_D/backup.img | grep -i superblockdumpe2fs 1.42.8 (20-Jun-2013)
    dumpe2fs: Attempt to read block from filesystem resulted in short read while reading journal super block
    No luck. So I tried this:
    $ mke2fs -n /mnt/Disk_D/backup.img
    mke2fs 1.42.8 (20-Jun-2013)
    /mnt/Disk_D/backup.img is not a block special device.
    Proceed anyway? (y,n) y
    Filesystem label=
    OS type: Linux
    Block size=4096 (log=2)
    Fragment size=4096 (log=2)
    Stride=0 blocks, Stripe width=0 blocks
    41762816 inodes, 167026688 blocks
    8351334 blocks (5.00%) reserved for the super user
    First data block=0
    Maximum filesystem blocks=4294967296
    5098 block groups
    32768 blocks per group, 32768 fragments per group
    8192 inodes per group
    Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
    102400000
    Now, if I understand correctly, to use it in "sb=" parameter with mount, I need to multiply those numbers by 4.
    So I tried the first one:
    $ sudo mount /mnt/Disk_D/backup.img /mnt/arch_backup -o loop,ro,sb=131072
    mount: wrong fs type, bad option, bad superblock on /dev/loop0,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so.
    $ dmesg | tail
    [ 413.993564] CE: hpet increased min_delta_ns to 20115 nsec
    [ 765.048697] loop: module loaded
    [ 1291.820673] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
    But the second one went better, or should I say "different":
    $ sudo mount /mnt/Disk_D/backup.img /mnt/arch_backup -o loop,ro,sb=393216
    mount: wrong fs type, bad option, bad superblock on /dev/loop0,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so.
    $ dmesg | tail
    [ 1354.694258] Buffer I/O error on device loop0, logical block 98304
    [ 1354.694261] lost page write due to I/O error on loop0
    [ 1354.694264] EXT4-fs error (device loop0): ext4_iget:4044: inode #8: comm mount: bad extra_isize (17818 != 256)
    [ 1354.694271] EXT4-fs (loop0): no journal found
    I tried it with every following superblock, but the result was identical.
    What should I do now?
    I found here a similar error, and the advice was to delete journal and recreate it:
    http://tipsaboutmywork.blogspot.com/
    Remove the journal feature from the file system (downgrade to ext2)
    tune2fs -O ^has_journal /dev/sda8
    fsck to delete the journal:
    e2fsck -f /dev/sda8
    recreate the journal (change back to ext3)
    tune2fs -j /dev/sda8
    and finally, remount it.
    Does that have the potential to trash my data (like fsck did earlier) or does it just get rid of the journal, and not touching data?
    And if the later is the case, would that result in loss of filenames and folders like photorec recovery?
    Should I do that, or should I try something else first?
    Last edited by Lockheed (2013-12-07 16:13:40)

  • How to simply remove Partition Schemes or Partition Functions

    Hello,
    Did anyone can instruct how to remove the Partition Schemes & related Partition Functions?
    When try to remove those Partition, it give out a error 7717 and it can see there are many related dependencies tables.  However, I am no idea how to remove it.
    Thanks in advance.

    You should find all related object first, in order to remove the Partition
    https://social.technet.microsoft.com/Forums/sharepoint/en-US/41418b34-d000-49de-8074-9b662b0a3013/deleting-an-incomplete-partition?forum=sqldatabaseengine
      Ronen Ariely
     [Personal Site]    [Blog]    [Facebook]

  • [SOLVED]How to totally remove configuration files that pacman uses?

    Hi,
    Playing with Arch linux with a view to ditching windows completely, but came across one very small issue. One where I have tried to find the answer on the wiki and using the forum search
    Anyway, I installed firefox using pacman, no problems. Then I discovered Yaught (can never spell it right) and found a proper branded firefox package on there.
    I run:
    sudo pacman -R firefox
    and it is rightly removed. The issue is it still seems to keep the installation files on the system.
    How do I completely remove all the installation files?
    Last edited by oxymoron (2009-03-16 14:06:34)

    Dont need a -y to clean your cache. Also -Scc will wipe the whole thing if you dont want them taking room.
    Some thoughts on making use of the cache...
    '-Sc' keeps the currently installed pkges and cleans only uninstalled/old pkges from cache, its a good practise to do it everytime *before* you upgrade. Doing that ensures youll always be able to downgrade to a working set of pkges if theres something wrong with an upgrade.

  • How to recover a partition for ASM

    Hi, folks, I tried to install ASM on Solaris two partitions: c1t1d0s5 and c1t1d0s6. I accidentally deleted c1t1d0s6 by using rm -r /dev/rdsk/c1t1d0s6, so OUI could not find partition c1t1d0s6, can anybody help me to figure out how to add /dev/rdsk/c1t1d0s6 back to solaris? many thanks!
    Edited by: user8641679 on Feb 25, 2010 11:46 AM

    not to put you off on what you're about to do, but depending on what version of 7 you have, pro and ultimate have an option to install a full copy of xp pro sp3 in a virtual machine within windows 7.  it will integrate windows 7 files into it so you can access them.  and it it actually is a full version of xp.  you allocate system memory for it to run and you can either have it set to shut down which will free up the resources or hibernate which won't.  although it loads much faster from hibernate.
    before you do anything, i would burn restore discs in case something gets screwed.  make sure you have restore points set.  
    T430u, x301, x200T, x61T, x61, x32, x41T, x40, U160, ThinkPad Tablet 1838-22R, Z500 touch, Yoga Tab 2 Windows 8.1, Yoga Tablet 3 Pro
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    If someone helped you today, pay it forward. Help Someone Else!
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • [Solved] How to recover the package list from another installation?

    Hello,
    I supposed gparted could make a fine result by moving the partition, but it didn't.
    I was doing that on an USB installation, now fsck recover partially my partition, but mostly many files are gone. It seems that pacman databases are saved, then I would like to recover the list and try to reinstall all packages.
    I can't enter by chroot on that partition, bash fails.
    My attempt is to use pacman -r /mounted/partition packagelist, if I'll get the list, then it mostly possible to regain chroot access
    EDIT
    I got a flashback and I applied modifications in a temporary pacman.conf. In that configuration I modified the paths to all file used by pacman to reflect the other installation.
    Finally I could get the list, but I didn't go for an update, because the installation was too old. I'm doing a fresh install with the recovered package list.
    Last edited by TheSaint (2013-08-02 09:39:59)

    I'm entirely agreed with you.
    Some time I fail to remember such things. I don't regret much the loss, it was just a support installation for emergency cases. Home is safe in another partition
    However it is a good exercise to rescue the package list.

  • [solved] How can I remove a package?

    I used to have a *-32 and a *-64 version of a certain package but recently wrote a PKGBUILD that detects the architecture and downloads the correct archive respectfully, so I want to remove my old two packages.  There used to be a button where I could just remove packages I own, but it somehow disappeared?  I think?  Where is it?
    Last edited by synthead (2008-12-23 12:04:57)

    Sounds good   I wrote to the list, thanks

  • How to recover corrupted partition table?

    I have a disk that somehow got the partition table corrupted. I am getting lots of "Bad Geometry" errors that state the label says one size while the drive says something different.
    I have tried running the TestDisk (http://www.cgsecurity.org) application, and it seems to find the partitions just fine and I believe that my data is in tact. I just need to correct the partition table and access the UFS file system. The TestDisk reports that "write_part_sun" is not implemented, so it cannot correct the problem. I have checked the source code for the current and beta versions of the program and the function still has not been written.
    Is there another application that I can use to rescue my corrupted partition table? I am not finding much support for Solaris out on the net.
    Thanks.

    Is there another application that I can use to rescue my corrupted partition table? I am not finding much support for Solaris out on the net.Hi
    There is some, but you have to look hard.
    I wrote a partition table editor:
    http://paulf.free.fr/pfdisk.html
    If your LBA values are good, you should be able to restore the CHS values from them. If both the LBA and CHS values are corrupt, and you have a good idea of the sizes of the partitions, then with a calculator you should be able to work out what the values should have been.
    Paul

  • (SOLVED) How do I remove dependencies of AUR packages?

    I rather not use sudo and thereof I issue a 'makepkg' instead of a 'makepkg -s' and install dependencies manually. I wonder though what happens when I issue a 'pacman -Rns' to remove an AUR package. Pacman doesn't seem to remove the dependencies. Do I need to issue a 'makepkg -s' in order to automagically remove dependencies with 'pacman -Rns'? What about AUR packages that have other AUR packages as dependency and therefor cannot be installed with 'makepkg -s'?
    Last edited by Kasumi_Ninja (2010-01-03 13:39:51)

    I haven't fully thought this through but I would like --asdeps to take an argument that specifies 'to what'. 
    For example: wicd has an optional dependency for notifcation-daemon, which I want.  I would like to be able to
    pacman -S --asdeps='wicd' notification-daemon
    This would then modify wicd to depend on notification-daemon.  This isn't perfect since it is an optional and not a real dependency.  The only real problem I can think of is if I want to remove notification-daemon.  However pacman should see 'notification-daemon' listed under dependencies AND optional-dependencies, so it could give a warning and an option to go ahead anyway.  If it goes ahead, pacman reverts wicd to nolonger depend notification-daemon.  I feel like it should be pretty easy to add this to pacman.
    I feel like something like yaourt would be responsible for asking if I want to install optional dependencies.  So when I install something with yaourt it asks me about each optional dependency and if I want it. 
    Just my two cents.

  • How to recover windows from 2nd partition

    I have a problem, recovery process crashed almost at the end and when i restart computer i cannot get to the windows (missing files). I installed windows but i didn't have any toshiba utilities for recovery (only those files on 2nd partitions: hdd recovery). And here is my question, how can i recover my system from that files without any toshiba utilities? Can i download them or something? What can i do to restore it, because toshiba recovery media is, i think not available. And if it's not so how can i do? My warranty for laptop expired.
    Solved!
    Go to Solution.

    Satellite A350-110 (PSAL6E-006009G3) 
    how can i recover my system from that files without any toshiba utilities?
     You should order the recovery discs from Toshiba.
       Toshiba Europe Backup Media Online Shop
    After you have restored the hard disk to its original out-of-the-box contents, you should have the recovery utilities and partitions. See the A350 User's Manual (attached) for how to recover after that.
    -Jerry
    Attachments:
    SA350_EN.pdf ‏5918 KB

  • How can I uninstall Bootcamp and Recover the partition for the Mac HD

    How can I uninstall Bootcamp and recover the partition for the IMac HD?

    Boot into OSX.  Go back into the Bootcamp utility in the Utilities folder and re-run it.  It will give you the option to remove the Windows partition and make the OSX partition fill the whole drive again.  OSX will NOT be lost in the process.  No re-installing necessary.  Only takes a few minutes or less to complete.

  • How can I remove the BootCamp partition? as the size i created ws too small to install MS Office on 64Bit Windows 8.1 on MacBook Pro (Aug'13)

    How can I remove the BootCamp partition drive for Windows 8.1, as the size which I created was too small for me to install Microsoft Office onto Windows 8.1 64-BIt. The machine which I have is the MacBook Pro 13' inch purchased in August 2013.

    Either use Paragon's CampTuneX to resize it or use Boot Camp Assistant to remove the partition and restore the drive to one partition. Then create a new, larger Boot Camp partition. This will remove/delete/erase your Windows system.

  • How do I remove Boot Camp and go back to a single partition?

    I originally used boot camp but recently installed Parallell. I didn't realize all my windows info was still in a separate drive. I am now just using Parallells but the boot camp is still out there. How can I remove those items and go back to the one partition
    Thanks

    Hi,
    if your specs are uptodate and you are using OSX 10.4 Tiger, use these instructions: http://support.apple.com/kb/HT1309?viewlocale=en_US
    For OSX 10.5 Leopard use these: http://docs.info.apple.com/article.html?path=Mac/10.5/en/15554.html
    Regards
    Stefan

Maybe you are looking for