Fedora Emergency Mode - Help Parsing the Journal File Please
For some reason, my new Fedora install has started booting into emergency mode. I have a log and am hoping it will tell me why.
I obtained the file by running "journalctl > journal.txt" on the command line. It's a 56MB text file. Yep, that's 58720256 bytes. If you consider that one character equals one byte, more or less, you understand why I'm asking for assistance. I've uploaded it here: journal.txt I can't get it to upload on LQ as an attachment. I haven't read the fine print, but I think it's too large. I'm not asking anyone to go through with a fine-tooth comb. Just peruse, and if anything stands out tell me. Or, give me an idea what to search for. Note: If you are on Windows, do not open in Notepad. It will freeze your Notepad if you start playing reindeer games with the content. Also, it looks like crap. Notepad++ swallowed the whole chunk of data with no complaining. If you're on Linux, I'll assume you know what you're doing. Thanks for any help, Doug |
Quote:
Pretty obvious what's filling the log - and no need to post it all. Do you have /mnt/usb in fstab ?. Try commenting it out and rebooting. Systemd can get pretty anal about errors at startup. |
syg00,
Yes, I did look. I missed that particular bit of info, or my Windows-user brain saw line after line of text and threw a BSOD. That being said, I'll be looking at my /etc/fstab when I gett home this afternoon. Thank you, Doug |
All times are GMT -5. The time now is 01:34 AM. |