TRF, Thanks for the detailed explanation. I see where we differ. To use chkdsk I open an Admin command prompt and type... chkdsk /f If I'm trying to repair bad sectors I use... chkdsk /r I've used the above method since WinXP.
Longboard, The TeraByte apps have always baulked at resizing a partition with file system errors. Resizing that partition could cause further problems so it's sensible to fix the errors before the resize.
Just a comment on restoring Win8 and Win10 UEFI systems to a new HD (or SSD) with IFW etc. With UEFI installs in Win8 and Win10 you get 4 partitions.... Recovery 300 MiB EFI system partition 99MiB Microsoft reserved partition 128 MiB Basic data partition (the OS) The easy way is to create and restore an Entire drive image. But if you want to make it exciting you can restore these partitions individually in random order, anywhere on a blank drive you like and the OS will boot. To do this use the "Restore First Track" option with the first image restore and the "Update Boot Partition" option with the last image restore.
Hi Brian! I'm not sure they're so different (other than the error #) Sure, the structure error itself may be different... different file structures, different OS, but the nature of the error appears to be the same. To the OS, the error is benign (hopefully), but to IFW, which really can't make that determination, it must follow the rules... and when it finds the rules broken, it must act accordingly. What I'm scared of is that W8.1.1 might be getting as sloppy at managing its file structure as Ubunto is... which eventually will cause many more errors to be had by BIBM/IFW, etc. Of course if I had known this before, I would just have used the COMMAND PROMPT (and ChkDsk) on IFW's WinPE to "fix" the volume in question while I was already out there imaging anyway. This is a good example of why ERROR #s are basically useless without explanations. Had I known the above, the whole process would have been much less painful Thanks once again for all your help with this... you da (IFW) man!
Since my last post I must done hundred backups+restores with no failures yet on desktop+laptop; except for one minor differential backup that needed multipass for restore but made a backup to replace it afterwards. Every other backup app failed me at least once before trying IFW/IFL+DS. Also bought a new Macbook Pro Ret (new to Macs) and found IFL works with HFS+ partitions along with it's Boot Camp Windows. Without IFL I would've needed more backup solutions specifically for Mac OSX (aside from Time Machine) and for Boot Camp, saving me SSD backup drives space as well. Will be buying another bundle for the Mac <3 Terabyte
Some hints about IFL and Mac. A) You can boot IFL directly from a Mac partition (and there are 2 ways to do it, during boot with the "option" pressed): - 1st you copy the contents of an IFL CD/DVD to any Mac HFS+ partition. or - 2nd you create a small Fat32 partition and copy the contents of an IFL USB flash disk. B) You can have bootcamp with multiple partitions and not be restricted with only 2. Just use the IFL's Partition Manager(Bootit BM) and place the windows partition on the hybrid mbr in position 3 or 4 for vista/7/8 and on position 4 for xp. I dual boot my mini and is partitioned like this: Mac OSX, OSX recovery, OSX data, Windows 7, Windows Data, IFL fat32 partition And my partition Hybrid partition table is: GPT Reserved Mac OSX Windows 7 Windows Data Panagiotis
Nice tips thanks! A)1st did as you described and it just boots OSX from Macintosh drive. Simpler option is IFL on Easy2boot USB flash drive works for PC's and Mac without any changes. B) is the setup I want but with two data partitions. One in exFat for cross platform read/write and one in HFS for Superduper sandboxing app or convert to exFat if I don't like it and go Deep Freeze Mac. Going try it soon after this getting to know Mac test phase. backups satisfied, now onto firewalls (Little Snitch vs Hands Off), AV/AM (Bitdefender vs Avast vs Intego), hardening OS X etc. wipe and start fresh.
You are welcome. I just reread need to clarify 1-2 things: A. I did not mean the partition/s where OSX is placed B. Do not use the partition manager of IFL/Bootit BM to partition the disk. Use OSX's disk utility to partition the disk and then use IFL/Bootit BM to make the adjustments in the hybrid mbr. (Windows XP/Vista/7) will only see the 3 partitions that are in the mbr (will treat the disk as mbr type and not as gtp). Windows 8.x should be able to see all the partitions but I have not tested it. Panagiotis
Oooo... Posts 357 - 359: wow ! Textbook in themselves: nice info. Am having to consider some Macs @home & @Work: have been ruminating re backups and imagers Thank you both
Image for Windows: Upgrade History Version 2.94 - February 8, 2015 Added new /altregview option to consolidate variables and passwords. Added new IFW Notify system tray utility. Added new /wait option (must be first) to wait for already running copy to end. Updated /recover option to work with latest versions. Adjust GPT placeholder when adding a partition to the MBR on GPT drive. Support EXT4 64bit feature. Other potential changes, updates and enhancements. Image for DOS: Upgrade History Version 2.94 - February 8, 2015 Updated /recover option to work with latest versions. Adjust GPT placeholder when adding a partition to the MBR on GPT drive. Support EXT4 64bit feature. Other potential changes, updates and enhancements. Image for Linux: Upgrade History Version 2.94 - February 8, 2015 Updated /recover option to work with latest versions. Adjust GPT placeholder when adding a partition to the MBR on GPT drive. Support EXT4 64bit feature. Update Linux Boot Disk (LBD251EN)(3.18.6). Other potential changes, updates and enhancements. OSD Tool Suite: Upgrade History Version 1.57 - February 8, 2015 Update to OSDTOOL.TBS, TBIDTOOL.TBS, COPYP2V.TBS, TBEXPLO.TBS, SETWINDL.TBS, MOVEUSER.TBS scripts. Added new COPYWIN.TBS script. Fix version checking on .INF files. Support EXT4 64bit feature. Other potential changes, updates and enhancements. BootIt® Bare Metal: Upgrade History Version 1.29a - February 8, 2015 Updated with IFD version 2.94. Updated with TBOSDT version 1.57. Support EXT4 64bit feature. Other potential changes, updates and enhancements.
3 failed downloads so far, and I think my fourth try is going to fail too. I will have to give up trying to download v2.94 until they fix this problem or my account will be locked.
You are welcome. As for imagers actually the only one that you need is the "disk utility" is already included in OSX; can take both file based and sector based backups (it depends if a partition can be locked or not) and works fine with HFS+, FAT, EXFAT and NTFS. Add also IFW/IFL in the mix and you are completly covered. Panagiotis
Re: Added new IFW Notify system tray utility. How does this work? Does it need enabling? If so, then how? I can't see it when doing a backup.
When you install IFW you can select to include it and whether to run it automatically. If it's installed and not running, just start it and it goes in the tray. Right-click for settings.
I deleted some backups, but they are still showing in IFW Notify. How do I refresh the IFW Notify list?
I've performed quite a few restores (using a string of imaging apps) of UEFI Win8.1 systems to new, empty HDs. Most imaging apps are easy to use but perhaps the easiest app to use is IFW in Simple Operations Mode. No browsing to a backup file is needed. You don't even have to select the new HD/SSD. You are presented with 3 screens... The first asks whether you want to Backup, Restore or Validate. Obviously you select Restore. The second shows a list of your backup images. Most likely you will select the most recent image. The third asks you to click Start. All 4 partitions are restored to the new drive and Win8.1 boots.