Disks unavailable after update

[ogbbv]

It shows 3 events in the NTFS. Sorry for norwegian language in there. It basically says that windows can not save content for the file. I will try to run checkdisk again maybe.

[ogbbv]

Chkdsk is finding no problems with the drives

[Support]

How about running the command "sfc /scannow"?

[Support]

And since these drives work in Safe mode but not Normal mode, it is probably because of a program or service that normally loads, but is prevented from loading in Safe Mode. You may use Msconfig to narrow down the problem. See the following link for reference. The article was written for XP but the principle also applies to Win10.
https://support.microsoft.com/en-us/hel ... -configura

[ogbbv]

Not sure what to check when doing msconfig. I tried diagnostic start but then my user profile did not show up. What I did last time when this happened was deleting the cache tasks. This was when I went from 2.7.0 to 3.0.0 I think it was. Now that trick did not work. Is there anything I can do from the PrimoCache user interface to make the disks read normal again? I can make a task, but it shows wrong free space.
And after testing safemode again I can enter the disks and the folders are there but it I can not open files, and it show wrong free space there too.

[ogbbv]

Hey just to add to this topic I am asking at the windows forum too if they have any tips. I am sure this got triggered by the PrimoCache update but I think at the core it might be some Bitlocker related stuff going on too. So I will bother them a bit now too. Thank so far in trying to resolve this issue.

[Support]

Is there any other computer to which you can connect these disks in problem?

[Jaga]

Sidenote:

Not to derail the conversation, but this last most recent Windows 10 update managed to mangle my Boot drive which was the only volume Primocache was caching. I don't think Primo was directly at fault, but the Operating System would no longer boot. At first Windows complained about the MFT being corrupt, but after fixing that all attempts at startup repair (including System Restore) failed to fix the problem. I've spent the last 3 days trying to get the entire volume backed up to a NAS, then zeroing the SSD before rebuilding Windows.

@Support - you *might* want to look a little deeper into what the recent W10 update included and how it affected disks/volumes. There may be circumstances where the update did things that Primo didn't like. I don't hold Primocache at fault though - it was time for a rebuild anyway. And I have a better backup scheme in place as a result.

It sounds like whatever happened to the MFT on my drive could have happened to yours as well ogbbv, making the files inaccessible.

[Support]

@Jaga, thanks for your information! We raised the priority of this issue to high and will do a deeper checking.

[Jaga]

@Jaga, thanks for your information! We raised the priority of this issue to high and will do a deeper checking.

Sounds good. As follow-up information, the system seems to be running smoothly after a clean W10 (Pro) install to a GPT volume that's properly aligned (and no Intel RST). The problem may be related to what happens on the update to an existing install. I regret not being able to offer any crash dumps, since there weren't any produced on the boot attempts - it never got that far.

Hopefully ogbbv can get those files off the Cloud and recover.