I have been having a similar problem. It involves almost any drive formatted in exFat in a USB3 Drive dock. Everytime I plug in the drive, I get the read only problem. Sometimes I run chkdsk on it and it fixes it quickly, sometimes it take s HOURS to work. Even some NTFS drives have this problem. I have been very careful to dismount the drives first or, failing that, to shut down the computer before removing the drives. Same problem. A MAC formatted drives workes fine and a 750 GB NTSF Drive works fine. It seems to be exFAT drives or any drive that is 1tb or larger.
dndobson:exFAT should not be used and was not designed for formatting hard drives. It is only recommended in flash memory storage and other external devices only.
Serophis: To remove the Dirty bit, start an Elevated Command Prompt. Lets assume the drive letter is F: In the Command Prompt now type fsutil dirty query F: (or whatever the drive letter is) You should get Drive Letter F: is Dirty (or not) this removes the Dirty bit, now run chkdsk /R from the drive letters Prompt and it should fix it up.
If this solved your problem, please mark this thread solved in the Thread Tools at the top.
This happens with 1TB and Higher Hard Drives (NTFS and ExFat) that I connect to an Asus G74S via the USB3 cable and running in a Thermaltake SATA 6GB Drive Dock (Windows 7 Professional, SP1.)) At startup, the drives are read only - every time. (This does not happen with 750GB Drives or a Mac Formatted 1TB drive.)
I can run chkdsk /f on the drive and it will find errors and fix them (but the process takes hours!) and then the drive will work fine until I shut down the computer. On startup, the same drive is now read only and I have to run chkdsk again to fix it.
I have tried Safely Removing Hardware, shutting down, and on start up, the drives are read only again and need to be fixed. I have started up with the drive in the dock and powered on and turning it on after startup with the same results. I put the computer to in sleep mode once and it started up the next morning and the drive was OK. So that's something.
If I connect a damaged drive to another computer (desktop via SATA 3Gb Dock using SATA Cable) it shows the same error and can often be fixed via chkdsk in a few minutes or less (though not always.) After that the drive can be removed and returned with no problems on that desktop, so it's definitely something about the laptop or usb3 or the drive dock. Also, if I fix the drive on the other computer, it will work fine on the laptop until removal or shutdown.
I have read hundreds of posts here and elsewhere and tried the suggestions (chkdsk and diskpart) and nothing permanently fixes the drives on this laptop.
If I connect a damaged drive to another computer (desktop via SATA 3Gb Dock using SATA Cable) it shows the same error and can often be fixed via chkdsk in a few minutes or less (though not always.) After that the drive can be removed and returned with no problems on that desktop, so it's definitely something about the laptop or usb3 or the drive dock. Also, if I fix the drive on the other computer, it will work fine on the laptop until removal or shutdown.
I have used exFat successfully on external Hard Drives in order to work across PC and Mac systems. I have never had this problem before with them.
However, the problem I am having with the exFat I also have with 1TB NTFS drives.
I can fix the problem with chkdsk /f and /r for so long as the laptop remains on (The fix takes 4 hours for 1TB.) But if I shutdown the laptop, then on start up the drive is read only again. NTSF drives included. I put the computer to sleep once with the 1TB exFat in the doc (which I left on) and on start up the next morning the drive was OK. Also, on different Desktop computer, the drives, once fixed, remain so until they go back to the laptop where they will work until they are removed or the computer is shutdown.
You left out the make and model of the drive but at this point since its happening on "other" computers as well I would run the manufacture diagnostics ie WD or Seagate to "test" the drive it sounds like a drive issue or is it possible the "enclosure" cant handle larger capacity drives ?
It happens on WD and Seagate drives. It does NOT happen on other computers, just the one (Laptop/USB3/DriveDock.) The thought that it could be the enclosure has crossed my mind and I will test it. Thanks.
Thermaltake BlacX 5G (USB3 port)
Fresco Logic xHCI (USB3) Controller FL1000 Series (latest drivers installed)
Seagate 1TB Barracuda 7200.12 (just the drive in front of me.)
What I meant to say is that the disks that are converted to read only on the laptop set up will still be read only on the desktop - BUT, after repair on the desktop, they do not revert to read only on start up on the Desktop. In other words, the desktop set up does not cause the problem. Hope that is more clear. Thank you for your questions.
According to the specs the dock supports all drive sizes so I am going to say the issue is possibly with the USB3 controller. have you tried it using the standard USB2 ports ? same issue ?
Not yet. I'll try that and get back.
Much later as I need to work now that the drive is up and running.
Another device I tried that worked intermittently (BlackMagic Ultrastudio SDI) called for the Renesas controllers, so perhaps this laptop's chipset is the problem.
I am new to this forum, but I have only created only one thread. The other one I merely responded to and then it was closed and new one was created by someone other than me. I didn't realize it was mine. So thank you for merging them and I will be sure not to start duplicate threads myself.
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Forum
4.7M posts
957.9K members
Since 2002
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!