Byte For Byte errors now with Solid State Drive

User discussion and information resource forum for Image products.

Byte For Byte errors now with Solid State Drive

Postby timg11 » Tue Oct 04, 2011 5:43 am

I upgraded the C: Drive on my system to a 60G SSD. Nothing else changed. There were formerly two mechanical drives. One was partitioned C: and D:. After copying C: to the SSD, I deleted it and expanded D: to fill the whole drive. I've been using IFW for several years on this system with no problems.
Now whenever the byte-for-byte verify runs, I get a failure within the first few seconds of the verification. According to the log, the failure is at a different sector each time.
I tried changing PHYLOCK to RAM only, but still got the error.
Thinking the destination drive might be failing, I tried changing the image destination from the D: drive to the E: drive, but I still get the error.
I suppose the SSD could be bad, but the system runs perfectly otherwise.

This is with IFW 2.66 on Windows 7.

Any suggestions?
timg11
 
Posts: 159
Joined: Sun Oct 02, 2011 9:31 am

Re: Byte For Byte errors now with Solid State Drive

Postby TeraByte Support(PP) » Tue Oct 04, 2011 9:31 am

Is TRIM enabled?

Previously posted by TeraByte Support in NG:
-----
Phylock isn't going to catch TRIM requests, just writes. So if you have something using TRIM then it goes back to read that area and it's now zeros where it wasn't before. so you'd have to use normal validation or disable TRIM while backing up.
-----

You could also use IFL/IFD to create the backup outside of Windows.
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1100
Joined: Thu Aug 11, 2011 5:51 pm

Re: Byte For Byte errors now with Solid State Drive

Postby timg11 » Tue Oct 04, 2011 12:46 pm

Interesting - I thought IFW only imaged the used blocks, and TRIM wouldn't affect a used block.
Since I run IFW unattended as a scheduled job from a CMD file, I guess I need a command to temporarily disable TRIM before I run IFW.

Some searching leads me to this: http://www.windows7home.net/windows-7-enable-trim-ahci/

It seems to indicate that the command
"fsutil behavior set disabledeletenotify 1" will disable TRIM and the command
"fsutil behavior set disabledeletenotify 0" will enable TRIM

Does that seem like the right approach?
timg11
 
Posts: 159
Joined: Sun Oct 02, 2011 9:31 am

Re: Byte For Byte errors now with Solid State Drive

Postby TeraByte Support » Tue Oct 04, 2011 4:25 pm

Yes, you could set that up in your batch command, otherwise you'd have to
use normal validation (things are changing while backing up).

"timg11" wrote in message news:430@public.image...

Interesting - I thought IFW only imaged the used blocks, and TRIM wouldn't
affect a used block.
Since I run IFW unattended as a scheduled job from a CMD file, I guess I
need a command to temporarily disable TRIM before I run IFW.

Some searching leads me to this: href="http://www.windows7home.net/windows-7-enable-trim-ahci/">http://www.windows7home.net/windows-7-enable-trim-ahci/

It seems to indicate that the command
"fsutil behavior set disabledeletenotify 1" will disable TRIM and
the command
"fsutil behavior set disabledeletenotify 0" will enable TRIM

Does that seem like the right approach?

TeraByte Support
 
Posts: 2313
Joined: Thu May 05, 2011 3:37 pm


Return to Image for DOS/Linux/Windows