Yeah, well not surprising! There aren't too many of us who own the COOLER MASTER II GINORMOUS TOWER Probably the biggest tower ever created - min 13 INTERNAL drives, 2 external hot-swap bays, but a TON of USB 3 & 2 ports ! And I usually have pretty close to ONLY 2-3 Drive letters FREE at any given time (and that;s not counting the people who I know use it for RAID systems and connect multiple ADDITIONAL RAID systems to it!!! So, for clarification, fdisk /dev/sdr should "reconstruct" the Partition? Is it expected to leave the file system (NTFS) intact? Is it expected to RETAIN all the current files that should be there? - OR should I sill be prepared to have to perform a file recovery process (that will HOPEFULLY retain ALL the PROPER NAME! ?) Honestly, at this point, I'm both physically & mentally exhausted over this. As long as I can get at least MOST of the data back - in PRPER form, not all jumbled or misnamed! - I will be satisfied! In the future, I KNOW I would not hesitate to PAY for a LIFETIME MEMBERSHIP for ANY software that could 100% guarantee the PREVENTION of this ever occurring again! Just simply SO illogical to me :-( --- DS
I understand the exhaustion, but this is the fourth time I wrote the same things fdisk does (rougly) what diskpart does. It accepts commands. p to print the actual status, n to create a new partition, d to delete a partition and so on... if you create a new partition that matches the original AND the underlying filesystem is intact (or recoverable by a windows checkdisk) your files will be the same as they were a file recovery isn't a mutually exclusive thing with a partition recovery, a sane partition table in place can help the file recovery if checkdisk is unable to fix the thing by itself. there are no shortcuts here, just use Drivepool to have selected folders or whole drives duplicated.
I will have to look into DrivePool then. However, that's still involves a GREAT DEAL of increase in cable and power codes - not sure about how everything is configured,but WILL look into it. Ok. I'd DEAD tired now, and have classes in ~2hrs :`( Thank you very much for you patience and mentoring. That speaks a LOT to your character --- DS
Not necessarily increased cable mess. Obviously redundancy involves more space needed, but drivepool is not stupid as a RAID 1 You can group a bunch of drives as one (or more) big virtual drives called "pools", then you can select the folders you care more and set the redundancy level for them. It's duty of DP to place them conveniently around the pool and being sure a file is duplicated (or triplicated or...) on different drives (even cloud ones). Drives (of any size and connection) can be added and removed to a pool at will (and even w/o shutting down the machine), and all of this retaining the standard NTFS filesystem, and keeping the drives readable even on 20 Y/O machines, running NT3.51, w/o the SW installed. Just a plain, simple, brilliant, modern replacement for old school RAIDs that are unflexible, often incompatible, sometimes dangerous.
Anyone remember the ORIGINAL Norton Disk Drive? Or better yet, the VERY old NIBBLER? I liked how they gave a nice graphical interface of what was happening with every sector of your drive vs the software now, that basically leaves you in the dark. ---DS
Wow a lot of progress has happened since my last post, I truly hope you get as much data back as possibly and thanks acer-5100 for your informative info to help DeathStalker77 out. Never heard of drivepool will have to check it out.
That is what makes this site SO great! Everyone is willing to help anyone out in any way they can --- DS
I have also run a couple of surface tests on the drive (StableBit Scanner, Victoria, & RS Partition Recovery) and they identify a VAST majority of the sectors as BAD. Now this just seems unlikely with such a new drive, but I do not know of any way to be able to check if the issue is with the controller - therefore the correct data is not getting passed back & forth, as I have found other references to this happening with external drives. --- DS
Yes the mos common scenarios are One or few bad sectors, it just happens A bunch of clustered bad sectors, it happens if you hit the drivers when it was running and the head touched the surface for a moment A bunch of bad sectors spread randomly across the surface, some bearing are worn, the motor is vibrating, in short the drive reached the EOL And none of the above seem applicable to your case. That said, for obvious reasons, my personal experience (and general experience) is limited on recent drives with metadata on SSD/flash memory, I guess that if something goes wrong there, some new odd behavior may be observed. Likely not just metadata but also some calibration data may be stored there... So all I can say is that if the disk was mine I would open it in zero time as I value my data more than the value of the HDD, but I can't suggest to do the same to everyone. That's a personal decision
Again I haven't seen as well, but I haven't played with that much broken recent HDDs. That's why the USB controller board broken makes sense, but also why the loss of metadata/calibration data makes sense as well. It's still a lottery, no matter how much brainstorming and educated guesses we can do
I guess that someone who already has (at least) 17 drives connected has no problem to find a spare sata connection...
Technically, I usually have 22-23 running at any given time, leaving a couple spare to transfer data to/from :-D Not only do I have the 2 HotSwap bays, the system has over half-a-dozen USB 3x ports and as many USB2 ports - in addition to a powered external USB Hub :-D --- DS
FWIW, I found a rather lengthy (yes, longer than this one! :-D ) thread on SevenForums with the EXACT same issues. So here's a screenshot, and it matches that thread, but no one ever got a resolution :-( --- DS
Well, the moral of the story is: NEVER EVER have a single storage of your data. For years anything of value to me is always stored in at least 2 places (usually it means a master drive & identical backup drive) Yes, it makes data storage twice as expensive, but never lost a bit of it