8062 and 8064 Fail to mount /dev/nvme0n1p1
-
Please see the debug upload task below. It may be something silly, but I am unable to upload my non-sysprepped Windows 10 Surface pro 4 image with the following error:
The next step states it could not mount /dev/nvme0n1p1 to /bcdstore.
Thanks!
-
As far as I know Surface Pro 4 is by default bitlocker encrypted, can FOG handle that?
-
@Quazz I’m pretty sure I’ve read here about people getting them going.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman I think it was the other way around in the sense I think my recommendation in one post was to create the reference image in MDT and then deploy to surface pro 4. If I remember at the time the OP was having a similar issue of not being able to upload from the tablet itself.
[edit] as things go I can’t seem to find that thread. But the OP will need to disable secure boot in the firmware. I might think that a bitlocker encrypted disk would cause fog some imaging issues since it wouldn’t be able to understand the disk format.
-
@george1421 I think I got it. It wasn’t a problem with FOG at all. You are correct, I wanted to upload a non-sysprepped image as a fail safe just in case I screwed anything up during sysprep. I got pretty deep in the matrix trying to look at partitions and such. Now I don’t know much about that kind of stuff, but gdisk found overlapping partitions and I deleted the second. I booted into windows and it did a quick checkdisk and successfully booted. I rebooted a few times to check the stability and it seems good. I was able to upload after that. I did debug again just in case and it barked at me for a few partition things, but went through. BTW secure boot is disabled.
-
@fry_p It would be inconvenient to test, but I’d be interested to see if it works in redeployment as well.
-
@Quazz Not inconvenient at all, I’m already deploying that image to other Surface Pro 4’s! They seem to be working. I’ll let you know if any fail. It’s weird that I had to do what I did because I started from scratch the exact same way I did for any other win 10 image.
-
Just guessing but this one can be solved?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott said in 8062 and 8064 Fail to mount /dev/nvme0n1p1:
Just guessing but this one can be solved?
Sorry, yes it can be solved. Nothing to do with FOG i think. I borked partitions somehow is all.
Like open source community computing? Why not do it for a good cause?
Use your computer/server for humanitarian projects when it is idle!
https://join.worldcommunitygrid.org?recruiterId=1026912 -
@fry_p You didn’t do anything wrong. Thanks for at least keeping us posted.
