I didn’t know which forum was the best place for this so I put it here.
Can someone walk me through the process of creating a bootable thumb drive from an .iso? This .iso creates an installation disk for Project Trident which is a desktop variant of Bsd. The website doesn’t mention using the .iso to create a thumb drive. Is this an issue? The reason I want to use a thumb drive is that my dvd seems to have quit working properly.
I have had trouble in the past creating bootable thumb drives because the they wouldn’t boot up after writing and restoring them to a normal blank read and write mode for every day use again afterward has been extremely difficult so I would appreciate being taught to erase the files and restore the drive to normal read write mode too.
So, as root user (not your user) umount /dev/sdd1 if you want to put the image on this device, but I would get rid of the partitions as well and set as a gpt disk (since the output shows this iso is a gpt rather than dos)
CAUTION The following will delete all data off the 64GB patriot device…
wipefs -a /dev/sdd1
wipefs -a /dev/sdd
dd if=<your.iso> of=/dev/sdd
Since we wiped all the info with wipefs, need to go back in with gdisk to set as gpt type disk rather than dos type.
Are you saying that I need to type “gdisk /dev/sdd” into a root console and hit enter and that will bring me back to a prompt and then I simply need to type “w” and hit enter which will bring me back to a prompt and then I need to type just a “y” and hit enter to set the thumb drive as gpt or are you saying that I need to place the gdisk /dev/sdd before th “w” and “y” each time or do you mean something else entirely?
The “gdisk” with “w” is intended to fix a broken “gpt” partition table. But, in my opinion, that should be done after the “dd” (copying the iso) rather than before.
Most linux distros are using traditional BIOS partitioning for an iso intended for writing to a USB. That’s because gpt partitioning causes problems. Part of the “gpt” partition table (the secondary copy) is written to the end of the disk. But the people preparing the iso do not know what size USB disk you will use. So that’s likely to always finish up as a broken gpt table.
Ok. Well it didn’t work. It came up with a loader version, indicated bios drive letter assignments, some other information that I could not decipher and halted.
At least it started to work.
Dolphin gives this error when I try to access the drive:
An error occurred while accessing ‘INSTALLER’, the system responded: The requested operation has failed: Error mounting /dev/sdd2 at /run/media/scott/INSTALLER: wrong fs type, bad option, bad superblock on /dev/sdd2, missing codepage or helper program, or other error
Could the errors fdisk -l revealed be the cause?
What I wanted to know before was is the command to restore to dos specifically “dos”? Is there anything else like that “w” command I should do?
What I said to do with “gdisk” will remove the “gpt” structures. But then you need to put dos structures back there. You can do that with “fdisk”, then create a single partition with “fdisk”. Maybe then format as FAT or NTFS with “mkfs”, or plug into a Windows box and format there.
I’m not sure what your first question means. When you say uefi do you refer to the iso or my hardware. My hardware is older bios based.
To answer your second question:
gdisk -l Trident-19.04-U1-x64-20190515.iso
GPT fdisk (gdisk) version 1.0.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the ‘c’ and ‘e’ options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don’t match. You should repair the disk!
Main header: OK
Backup header: ERROR
Main partition table: OK
Backup partition table: ERROR
Partition table scan:
BSD: not present
APM: not present
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
Disk Trident-19.04-U1-x64-20190515.iso: 7139452 sectors, 3.4 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): FA3DF87D-7740-11E9-8F66-AC1F6B626660
Partition table holds up to 4 entries
Main partition table begins at sector 2 and ends at sector 2
First usable sector is 3, last usable sector is 7139449
Partitions will be aligned on 1-sector boundaries
Total free space is 7137817 sectors (3.4 GiB)
Number Start (sector) End (sector) Size Code Name
1 80 1679 800.0 KiB EF00
2 3 32 15.0 KiB A501
Third question: No I did not. Strictly speaking I don’t know exactly how to do that.
I think at this point I would prefer to have a healthy file to begin with rather than one that I had to depend on my ability to repair. This one looks pretty ****** up.