![]() ![]() Why I blame the initramfs read from the USB (That is, if someone thinks your computer is not to blame, they would have to blame the specific version of Linux :).Ĥ. "incompatibility" between your computer and this version of Linux. ![]() a problem in the ISO image you wrote to it.This could be useful to confirm some sort of problem writing to your USB.įor completeness, the full list of possibilities is :. You could try to verify the USB data, on the same system that you wrote the USB. The initramfs read from your USB is (probably) damagedįrom the evidence so far, it looks like the initramfs read from your USB is damaged. Make sure you do not switch back to a graphical login before you have finished! For some information about logging in on a text console, see here. I think the simplest way is to log in on a text console and run your commands from there. It can be very hard to know how to disable auto-mount temporarily :-(. So this would require an alternative method which disables the auto-mount of your graphical login. In principle you might want to go further, and test the USB keeps its data correctly after it is removed and loses power. This command could show IO errors, or differences, if the problem is that your USB stick needs replacing. where sdb is the name of your USB device, and the. Then you can run # cmp Fedora-Workstation-Live-28.iso /dev/sdb This step is required, to make sure that cmp won't just be reading back from caches in system RAM. Then, you will be able to run echo 3 | sudo tee /proc/sys/vm/drop_caches. Then remember you should run sync, to make sure the data is finished writing. Remember to take great care and don't wipe your internal hard drive :). So you want to run dd to write the data, and then cmp command to verify the USB data, without re-plugging the USB (or rebooting) in between.įirst run your dd command. This is likely to happen if you ever plugged it in again to a Linux system after writing it! (Or successfully boot the Fedora Live USB?) You have to be careful with it! I believe cmp might also show differences if you ever allowed the written USB to be mounted on a Linux system :-(. Very sadly, there are some difficulties that will return useless results, so I need to explain these. In principle this could be a simple cmp command. I think it is only willing to write Ubuntu ISOs, not Fedora ones.Ģ. Ubuntu's "Startup Disk Creator" did not work at all for me. I don't know an easy way to install Fedora Media Writer on your Ubuntu OS :-(. At least the version of Fedora Media Writer I have, does automatically re-check the written data after writing it to the USB. The official Fedora install instructions "default" to Fedora Media Writer. ![]() But it doesn't seem to re-check the written data. GNOME Disks can be used to write a USB (the Fedora install instructions tell you how). Unfortunately I couldn't think of any easier method. Please re-check the data manually using cmp, by following the exact instructions in the next section. Therefore, please use a USB writing method that re-checks the written data.ĭd on its own, does not re-check the written data. You are having boot problems that look very much like bad data on the USB. Please use a method of writing to the USB which re-checks the written data.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |