HP Stream 11 wont upload
I have tried to upload a windows 10 image twice to the FOG Server. In both attempts, FOG gets hung up at “Saving oringinal partition table”
I am using an HP usb ethernet adapter to image with the has_usb_nic=1 argument. Could that be the issue?
I am running Trunk 7410.
@Quazz I can FTP into my fog server. I don’t think that is the issue. However, I rebooted the server and am trying the upload again.
@cojohnson Failing to update the database is generally an FTP issue, check the wiki on how to troubleshoot it.
I wrote changes the booted the machine to the network to capture the image. It went through partclone successfully. Now it is failing to update the database! What should I do now?
Thanks for your help!
@cojohnson Simply write the changes with
I think that’s the issue, it’s using an SSD with eMMC memory.
Might have to call in the devs on this one perhaps.
You can try fixparts /dev/mmcblk0 though
For future reference, all devices are listed in /dev, so regardless of your devices name it will be there.
For reference that is a memory storage device. That should be referenced by /dev/mmcblk0 that represents the “hard drive” of the system.
Since you are on the trunk version (but somewhat behind the current release) the FOG trunk versions understand the memory storage devices, where FOG 1.2.0 stable will not. So you should be in good shape once you get past this point.
Here is the listing. How do i find the location of mmcblk0?
Sorry the upside down picture was a bit confusing to me.
How about running this command
This will show the storage devices attached to this computer. You should see something like this.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT fd0 2:0 1 4K 0 disk sda 8:0 0 20G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 19.5G 0 part ├─centos-root 253:0 0 17.5G 0 lvm / └─centos-swap 253:1 0 2G 0 lvm [SWAP] sr0 11:0 1 4G 0 rom
Your stream may have a memory storage device not showing up as a hard drive (/dev/sdX)
The previous image showed a listing of all directories in the /dev/ directory.
There is no sda directory!
Is there any other possible directories?
Not sure where you are headed with this, but typically you would setup a debug capture or debug deploy to this target system (don’t worry because it won’t deploy or capture immediately if you remember to check the option or debug when you schedule a task). Then pxe boot the target computer. After a minute it should drop you to a command prompt. From there you might issue the
fixparts /dev/sdaWhich tells fixparts to look at the first hard drive for errors. Fixparts runs against disks not folders/directories
Alright! I did that!
I do not know what directory i need to fixparts.
@cojohnson Please search the forums for
fixpartsand see if that helps in your case.