Pro/Forums - View Single Post - Snap M4100 failde after battery replacement

Mauro · 12-01-2010, 06:15 AM

OK...it was what I expected to hear.

At this point - except Douglas as ultimate beach - I'm trying to rebuild the array imaging each drive with DDRescue cmd on Linux live system and then using them with Raid Reconstructor to see how much fles could be recovered and - more important - if it's possible. But...because two of the drives return I/O error due to bad sectors, what I want to know is what could be happen attaching them USB to a Win 7 machine for using Seagate Tools to check if they are repaired.

I've read that attaching a Snap hd to Win system cause loss of all data: in theory, USB work less in background than a system disk because of no request until he his invoked to act. It's really possible to loss data simply at the "new hw found" option by Windows ?

Again, many thank for support.
Cheers
Mauro

12-01-2010, 06:15 AM	#19
Mauro Cooling Neophyte Join Date: Nov 2010 Location: Italy Posts: 11	Re: Snap M4100 failde after battery replacement OK...it was what I expected to hear. At this point - except Douglas as ultimate beach - I'm trying to rebuild the array imaging each drive with DDRescue cmd on Linux live system and then using them with Raid Reconstructor to see how much fles could be recovered and - more important - if it's possible. But...because two of the drives return I/O error due to bad sectors, what I want to know is what could be happen attaching them USB to a Win 7 machine for using Seagate Tools to check if they are repaired. I've read that attaching a Snap hd to Win system cause loss of all data: in theory, USB work less in background than a system disk because of no request until he his invoked to act. It's really possible to loss data simply at the "new hw found" option by Windows ? Again, many thank for support. Cheers Mauro