C Drive Error
Alix Stocking
We have business standard (2TB per user) with 16 TB pooled storage (8 users). Keep running into this error migrating data from the server to google drive. The error shows "There is not enough space on Google Drive. You need an additional xx.xGB to copy these files" Google Drive, Space free 369GB, total size 933 GB.
All of the answers / suggestions I keep finding, refer to buying more storage, or deleting files. Obviously, there is plenty of space (also have made sure the trash is empty, so no issue there) It seems like it is hitting a 1 Tb limit roughly, but no idea how to resolve this.
The solution from support is that your upload limit is the free space on the drive where the Local cached files directory is located. So if there is 250GB free on the drive that is your maximum upload at one time.
Uploading eats up that free space, so right now I show less than 1Gb free on my google drive desktop (We have 16TB of data available, and drive is only showing about 750GB used (Not sure how long the data stays in the cache, but once it is freed up, I am assuming I can upload more, but it has been several hours since I uploaded all the data, and the cache is full)
Our network goes over few VLANs. I figured that when I try to connect to a network drive that on the same VLAN as my computer - there is no problem. But, when I try to connect to a drive that on a different VLAN I get this error: "Cannot access B:\" (B is one of my network drives letter). It doesn't matter if i try to connect with the full network path (not the drive letter).
Disconnect your network drive from your system and restart it. After restarting the system try to reconfigure the network drive and assign the B: drive and try once. Hope the problem will resolve. Some time external drive and network drive will create an issue if any temp files are blocked.
Anyways, if your disk happens to be ExFAT, and you remember improperly removing the disk the last time you used it, chances are, fsck is holding it hostage (metaphorically, of course). fsck is trying to repair the disk, but it will stall forever, so you want to launch Disk Utility, and the Terminal. Try to mount the disk, and switch to Terminal and write sudo pkill -f fsck. The disk will mount in read-only mode, and from there, you can repair it with First Aid in Disk Utility. This won't work for non-ExFat drives, as macOS manages them differently.
This happened for me on a Big Sur MacOS, clicking the 'First Aid' option in Disk Utility kept giving me this same error. What ended up working for me was restarting my laptop, then continuously trying 'First Aid' until one time it suddenly didn't give me the error, and after waiting about 20minutes the drive mounted properly. I don't think I did anything differently other than trying over and over again.
This still isn't working for me. I don't understand what this "and the Terminal" means. When I try to mount my drive, the error that is the title of the forum comes up and it appears I am at a dead end. I tried to repair the drive, and it seemed to do something (with a bunch of green check marks) saying it was fixed, but it still won't open or be recognized by my finder or desktop. If anyone is able to walk me through this, I would be very appreciative.
This time, though, even after running First Aid in Disk Utility, the drive is still registering as Read-Only, which I'm not sure how to fix! Anyone have any suggestions or have experience with this? The drive does have about 1.5 TB of data on it, and it hasn't completely backed up to my cloud storage yet, so ideally not anything that requires reformatting (fingers crossed)
The quickest way to sort out problematic exfat drives I've found is to mount them in a windows environment (either in a virtual machine or on actual windows computer) and repair them from there. Disk first aid takes a loooong time on larger drives.
Thankyou @jkrosado and @calif94577. It worked out but without hitting the enter button, magic! Also the exfat formatted LA CIE 5GB drive worked on BigSur before then after upgrading to Monterrey it didn't show up.
I tried that command on the Terminal, the 'First Aid' option on Disk Utility said everything was OK and then same Could not mount drive error, I restarted , tried it few times, same error. Dont ask me why but what worked was Logging Out my Mac user and logging again with the same user, super weird. There's defo some bug on Monterey and the external drives / Time Capsule Mac application...
Hi everyone! I have followed the steps and Disk Utility is running first AID. I have got a SEAGATE 2TB ExFat formatted...but first AID is running "Checking file system hierarchy." and it has done so for 24 hours...is that normal for a 2TB? I am tempted to quit it....
Hi there, My external HDD (LaCie Rugged 4 TB, MacOS Extended (Journaled) formatted) doesn't show up on the desktop. It is visible in Disk Utility but I can't repair it. The system returns com.apple.DiskManagement.disenter error 49244..
Checking file system and repairing if necessary and if possible.Volume is already unmounted.Performing fsck_hfs -fy -x /dev/rdisk6s2Executing fsck_hfs (version hfs-583.100.10).Checking Journaled HFS Plus volume.Invalid B-tree node sizeThe volume could not be verified completely.File system check exit code is 8.Restoring the original state found as unmounted.File system verify or repair failed. : (-69845)
I had an Eset free trial for 30 days and after about 2 weeks later I decided to stop using eset so i decided to uninstall eset. However to my stupidness for some reason i tried to uninstall eset manually by removing all (conceivable) files in C:\Program Files\ , Appdata\ , etc.. Instead of just uninstalling it using the setup SMH.
Shortly thereafter, I realised I was not able to open my encrypted drive. Then I reinstalled Eset and tried to open my encrypted drive however, it gave me an error with the title "Error authenticating or mounting encrypted virtual drive". Eventhough my license was certainly valid, i was getting an error and could not open my encrypted drive.
Since then my license has expired and i still cannot access my drive and the exact error page I'm getting now (which is shown in the screenshot above, it's the screenshot of the error i'm getting now) after that my license has been expired presumably differs from the error page i was getting when my license was still valid.
As for the issue reported by BowForMe with a trial license, I'd like to check ESI logs prior to asking Secure Data developers about next steps. A trial license can be activated after uninstalling and reinstalling ESSP.
If you delete this directory and the files within, then the encryption key is no longer available and your encrypted USB cannot be decrypted or accessed. Re-installing ESSP and enabling Secure Data will generate a new keystore file, which will NOT work for anything encrypted with a different key.
If we're lucky, and you still have the directories and files you deleted in the Recycle Bin, then you should be able to restore them and access your USB stick! If not, perhaps you have a Windows backup that you can restore where the DESlock+ directory and files are intact and can be restored to regain access to your USB.
Also, I will buy and start using an ESET subcription again in the future. Since, in the meanwhile, i figured it's actually one of the best, if not the best anti virus out there. With a noteworthy good support
Could you kindly provide us with additional information about this concept?
If I uninstall ESSP, is it possible to lose definitely the access to the encrypted file (due to the lost and/or regeneration of keystore file)??
Based on what I've read on this page ( -eset-secure-data-faq), it should be guaranteed to preserve access to the file even after having uninstalled ESSP (or after its complete re-installation).. is it right or no?
What is the scope of keystore file (.dat) located in the DESlock+ folder (C:\Users\USERNAME\AppData\Local\DESlock+)?
How they have to be managed/archived?
Is it advisable to have a "secure backup" of this file?
The same file is used/required also for USB drive or only by Volume drive?
--
(NOTE: Actually I discovered 2 distinct .dat files within this folder.. respectively "premium.dat" and "premkey.dat": which is the correct one in your opinion?)
"What happens to my encrypted data if I have to uninstall my ESET product or there is a problem with the product?Your encrypted files are stored separately from ESET program files. Uninstallation or errors in your ESET program will not affect your files. If you have to uninstall ESET Smart Security Premium, you can access your encrypted data after reinstallation by double-clicking the file and typing in your password."
"Common computer sense" here would be to back up the C:\Users\USERNAME\AppData\Local\DESlock+\ directory to external media. In an event where the OS resident HDD crashed. Windows had to be completely reinstalled, etc., the directory could be restored afterwards.
c80f0f1006