Rescue mode "No Linux Partitions" - how to create an fstab file in this case?
 

hi,

i'm currently playing around on a centos7 virtual machine and i've installed trouble-maker. one of the modules that i drew deleted the fstab file. i rebooted to simulate the actual problem and booted into rescue mode. working my way through the prompts i got to the message that usually says it will mount the system under /mnt/sysimage except for i received the "no linux partitions found" message. after hitting ok, i couldn't run chroot which i was going to use to create the new fstab file. since i couldn't do this, what alternative options would i have to create the fstab file at this point?

thanks in advance!

fstab is automatically created by the system under normal booting/loading process, so you don't have to create the *fstab* which is normally the static information concerning the file systems available. However if you want to create a new fstab you can get a sample and guide here.

Also under a running linux system you can read the manuals by these terminal commandsHope that helps. Good luck.

m.m

Nope.
Installers may create it, but not normal re-boot.

As for the OP, you presumably did this to learn. What effort have you made other than relying on sysimage ?. What tools do you have available, what resources - particularly system layout ?.
Did you attempt to set up the chroot yourself ?.
What does sosreport have in it ?.

ah yea i forgot, that's something taken for granted by the user.
thank you for reminding: it was/is installers that created.
anyway i have posted him a guide for creating a new one.

thanks for the quick replies. yes, i'm doing this to learn. having fun with the trouble-maker program. other than sysimage, i tried things i googled via grub2. sosreport, system layout...looks like i've got a lot of learning to do. never even heard of sosreport up this point, lol.

If you got a sosreport generated it will have a good deal of diagnostic info - mainly in the first third or so. But no fstab if it is deleted.
For that you'll have to manually chroot into your system by the looks of it - handy knowledge to have BTW.