I have a 4gb and a 8gb flash drive. Both are formatted. I have the newest version of Freenas. I m using the suggested win32disck imager and it says the .img file was successfully burned to the flash drive although when i boot the computer windows starts and i have the BIOS set to boot from USB hard drive. When i look at the "properties" of the flash drive after installing the .img file the flash drive is empty with nothing on it. Any assistance is greatly appreciated.
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum has become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
Trouble getting .img on flash drive
- Thread starter stuart
- Start date
- Status
D
dlavigne
Guest
Alternately, you may have to erase the stick first using a utility such as Active@ KillDisk. Then run win32diskimager.
Knowltey
Patron
- Joined
- Jul 21, 2013
- Messages
- 430
dlavigne's method is the method that I use as well. I make sure that the USB stick in question is completley blank by running Activ@ KillDisk on the USB drive and then I use win32DiskImager to place the .xz onto the USB drive.
Is this a machine that was made by Dell. Some of their BIOSes have the ability of completely removing devices from the bott sequence, but you may not realize that is what's going on. On the Optiplex that I use as an offsite if there is no number next to the entry, no matter it's position in the list it will not boot. Try seeing if this is the case. If it's not perhaps try disconnected the hard drive that you have Windows installed on and see if it will boot for you.
Yes, that is actually expected behaviour if you are viewing the drive's properties in Windows. The partitions that FreeNAS makes on the USB stick when installed to the drive are not recognizeable by Windows so you simply will not see them and you will only see the space on the drive that was not taken up by a FreeNAS partition.
Is this a machine that was made by Dell. Some of their BIOSes have the ability of completely removing devices from the bott sequence, but you may not realize that is what's going on. On the Optiplex that I use as an offsite if there is no number next to the entry, no matter it's position in the list it will not boot. Try seeing if this is the case. If it's not perhaps try disconnected the hard drive that you have Windows installed on and see if it will boot for you.
Yes, that is actually expected behaviour if you are viewing the drive's properties in Windows. The partitions that FreeNAS makes on the USB stick when installed to the drive are not recognizeable by Windows so you simply will not see them and you will only see the space on the drive that was not taken up by a FreeNAS partition.
- Status
