Joined 15 years ago
Truth forces you to confront your own shortcomings - its an opportunity for self-improvement.
If I miss a deadline I could makeup some baloney and lay the blame elsewhere or I can face my own inadequacy and tell the truth.
Its painful to admit I am behind.... but pain is a growth stimulus - it forces me to deal with the shortcoming. Its easier to lie, tell them what they want to hear - but you miss out on the chance for your own self improvement.
Embrace the pain - its growth. What happens when you lift weights? Sore muscles leads to growing bigger muscles. Swing a hammer for a week, leads to blisters leads to growing calluses.
4tb external drives are something an end-user consumer would shop for based on price.
While a 4tb bare internal is shopped for by techies building systems.
Failure of external drives has mostly to do with their handling.
They get bumped around while runnning.
People trip over the cords and knock them over.
They stack them like pancakes and they overheat. They block the fans and cause overheating.
Many enclosures are designed to look stylish - but don't cool well.
Heads fly at nanometers over the surface - they dont tolerate bumps well.
The drives we recover from external enclosures appear to be the same as bare drives that we recover.
They called them flippy disks...
SSDs are fast - but you better back them up. When an SSD fails its usually complete and without warning.
Spinning drives will often give you some warning signs, clicking, slowing down, bad sector errors etc.
Spinning disks can be rebuilt with new heads or platter swapped into a new body.
With SSDs you cant just remove the NAND chips and recover the data either. SSDs use dynamic wear leveling to shuffle pages of blocks around - in other words - block 0 is not at block 0 -it could be anywhere... and if the internal map is lost - good luck.
The data in the NAND chips is also encrypted... they do this to ensure that erased sectors are actually erased. Because of the wear-leveling routine spies could possibly recover data from unused sectors - the encryption makes this impossible.
And for extra fun - intel likes to epoxy the chips to the board - just to be sure they don't fall off....
I compare them to a hover-car, with wheels you can get a flat and still make it off the freeway... but with the hover-car your just a sitting duck...
Whats likely to happen in this case is this: The first blocks of the disk contain the superblock, labels-descriptors and other filesystem metadata. Most of which will be sitting in cache. The damaged overwritten area at 0mb won't be noticed for some time - like next time the volume is mounted. The filesystem will eventually notice the damage and go into some recovery mode or halt to protect itself. Zfs has lots of redundancy so the beginning volume labels could be rebuilt.
One benefit of zfs will be that you can tell which recovered files are good or bad.
If the problem is caused by the controller wrapping at 2tb then I wouldn't expect zfs to figure it out until later when it tries to read files back and finds damage.
Lets say zfs writes a file at 2tb but due to wrapping its actually written to 0 tb. Then zfs reads the file at 2tb to verify that is good. But the file appears to be fine because its really reading it again at 0tb. At some point zfs will detect a problem but I don't see how it can catch the problem instantly.
Customer had an external usb/firewire box with a 3tb drive. At 2tb the writes 'wrapped' back to block 0. Its a mac filesystem. Everything worked great until he wrote past 2tb. At that point it overwrote the beginning of the mac volume. The next time he connected the drive the mac thought that it was a new raw drive and told him that he needed to initialize the drive.
This is the second time he did this - the first time he didn't reinitialize it and we got it all back.
Unfortunately this time they initialized the drive. This zeroed out all the metadata, catalogs, maps etc - much bigger mess.
So some bridge controllers cannot handle drives larger than 2tb. 2tb is the last sector that you can address with a 4 byte disk address. So for sectors 0-0xffffffff .....works fine. The next sector is 0x100000000 - 5 bytes, it only sees the lower 4 bytes 0x00000000 and starts overwriting the beginning of the drive.
NTFS filesystems are more recoverable in this situation because their master file table starts 6 million sectors out on the drive so you would have to write alot more data before you start losing all your filenames and folder structures and pointers to the data.
The public thinks everyone else is going to ride the train and free the highway up for them... what a waste.
Some doctors graduated from med school with $100ks in loans. So they immediately filed for bankruptcy and cleared the debt. After a few years of work they were back in the bucks and debt-free.
The loan industry had congress write some new laws (was it 2008 ish?). The package clamped down on debt-collectors calling at all hours. It also eliminated clearing college loans with BK.
The loan industry celebrated - nothing like sure bet! Indentured servitude - Yahoo! They started giving away loans like candy.
Then the schools noticed all the free-flowing money and joined the party.
Currently students earn grades A-F. From now on we should have a 'basic grade', all students will be given a 'D' - a basic passing grade. You get your 'D' even if you don't even go to class. and since don't go to school well we might as well just give them the diplomas too...
I would like to see the idealistic college students and professors apply this concept to their real world and see how it works out...
The idiocy of this becomes obvious in this context.
You might want to look at this... http://hardforum.com/showthread.php?t=1285254
btw, I am currently working on recovering an 8 bay drobopro thats in a reboot loop...
