![]() I’m certainly not sure but I think the original dd is what did it in as eluded to by nightromantic above. So, after messing with this drive all day with no success I threw it in the woodstove like throwing the One Ring into Mt Doom from which it was forged! It’s $8 - screw it! There are no partitions on this disk to show. See the System Event Log for more information.ĭiskPart successfully converted the selected disk to MBR format. It would seem to be getting somewhere but ulimately fail like:ĭiskPart has encountered an error: The system cannot find the file specified. So I’m nuts with this thing now and I saw some other pages on using the Windows “diskpart” utility. But it failed ‘out of space’ at 967 MB again! ![]() Then I put the fashdrive in the F29 laptop to try the dd command on it. I think there was one large win32 partition I was able to write to with notepad: I de-elected quick format and it seemed to work. As it started it was showing 7gb total capacity (yea). Goto fileman > rightclick Computer > select Manage > select “Disk Management” on left > new window - select flash - rightclick > New Simple Volume wizard Then I saw in tutorial at:Į/how-to/windows-was-unable-to-complete-the-format.php It started but soon stopped saying that it could not format the drive. Right off the fm said it needed to format the drive. I had installed the win7 from the DVD the other day, so I stuck the flashdrive in there. I have heard of such things but never exerienced it. Hahahaha so that flash is messed up now I guess. Number Start End Size Type File system Flags Sector size (logical/physical): 512B/512B My thinking was that the drive is just memory that needs to be blanked out and rewritten and these tools should do that right? Sso I did these with gparted: ~/build> sudo dd bs=4M if=windows7_DVD.iso of=/dev/sda1 conv=fdatasyncĭd: error writing ‘/dev/sda1’: No space left on deviceĩ66553600 bytes (967 MB, 922 MiB) copied, 49.399 s, 19.6 MB/sĭoes that mean that the original dd is still there and can’t be touched for some reason? So I tried the to dd the iso again but with line above: Windows7_DVD.iso: ISO 9660 CD-ROM filesystem data ‘GRMCULF(X)REO_EN-RU_DVD’ (bootable) So they both say this and are the same size: Running “file” on the original iso file shows is an ISO 9660 after all. Now that I know it is not a BIOS setup problem, I will try to look for other Windows tool that could make a working USB stick and come back here if I have any further update.įor the record: what DIDN'T work before, was with rufus (version 2.11) and Win32DiskImager (version 0.9.5) running on Windows 10.Didn’t want to leave a dead end thread here so:Īpparently I was mistaken. I know this could be a pain, but it's the best bet right now. So, for anyone else having issues, if you don't have access to a Linux box, maybe the way to go is to download a live Linux distro and boot it for creating the USB stick. I can confirm the dd'ed sticks boot on the box I wanted without any BIOS configuration change (already installed it and it's working perfectly! ), and also booted on my laptop, so they should most surely boot on any system. Creating the USB sticks by following the steps from Getting started on Linux worked like a charm for both 16.7 and 17.1 images. I had no other computer at hand than the target box and a windows machine, but now I brought my Linux laptop from the office and tested this all again. My fall-back option is to use the ISO image and burn a DVD, but I'm trying to avoid that. The second image (dd2.png) show the fdisk info after successfully (?) writing to the USB. I've attached two images, the first one (dd1.png) show the fdisk info before the dd script and the result of the dd script. ![]() I'm new to FreeBSD and new to OPNsense, and I'm trying to migrate from ipfire to OPNsense. I also tried using rufus-2.11 but with same bad result. I've also tried using different USB media but with same bad result. If I do the same with ipfire-2.19.x86_64-full-core102.iso it works fine and my test PC boots into the ipfire installer.įrom what I think I learned, it seems the ipfire ISO is "hacked" to work with USBs, but the OPNsense ISO is not (only works with CD/DVDs) so I'm only trying to use your IMG files. My environment: Windows 10 Pro, with Ubuntu 16.04.1 running on VirtualBox 5.1.10 I used bs=1M because another thread with similar issue said changing that value from 16k could help. It writes successfully to the USB thumb drive, but it's not recognized as bootable media when I plug it into my test PC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |