I'm having an issue with a bootable USB I made. So this is an ongoing project that I have been working on for a while now. Basically, I installed red hat 7 onto a usb so that the usb is essentially the OS. I then issued the following commands to try to capture this "live USB" into a .raw.gz file for redistribution:
if=/dev/sda bs=10000 count=500000 status=progress | gzip > newredhat.raw.gz
the above task captures the first 5gb of the bootable USB and stores it into an image called newredhat.raw.gz as a compressed .raw file. The process is working as it should, except for one thing. I then issue the following command in order to put this custom image onto another USB which has been formatted fat32 and is 100% clean:
zcat newredhat.raw.gz > /dev/sdc
After the extraction/write is done, The new USB boots as it should, however it boots into emergency mode. I have been looking for hours about what the reasoning behind this could be but seeing as this is arguably a very unique scenario there is not much about it. I tried vi /etc/fstab and it tells me that /etc/fstab does not exist and creates a new file to edit. I also looked at the journal and the only thing coming back is "failed to mount sysroot". The idea behind this whole project is that it could be a simple extract - go clone for my Linux based USB's and servers. Whats really odd is that This exact method worked for openSUSE. Is it something to do with the way that Red hat creates its architecture upon install? If this is the case is there any work around? Thanks in advance for all of the help!