On 20.09.2013 14:28, Mark Haney wrote:
> I didn't actually edit the log. I had to enter it manually. I only get emergency mode on that netbook which doesn’t let me copy over the sosreport.txt file to any device.
>
> As far as the drive goes, I know it's fine. The problem isn't the drive, it's got to be the drivers or something stupid with grub. It will NOT mount by UUID. Period. I get this:
>
> Warning: /dev/disk/by-uuid/34307864-a1db-46e5-9815-d4c7c0698de35 does not exist
>
> I get this with EACH of the linux partitions it's trying to mount. Let me make this clear. I had this issue back with F16/17 and could boot by specifying the device the old way, /dev/sda5 etc. I can mount the drive partitions from a LIVECD of any linux distro. What I want to know is what do I need to do to make GRUB2 work? So far, I'm not at all impressed with GRUB2. It's beyond ridiculous to have to edit a half-dozen files to change how a system boots. I am considering trying to get it to boot by Label, but the directions to do so are just asinine.
>
Don't top-post, s'il vous plaît.
OK, to clarify whether this is a bootloader's problem, you should try
with the EXTLINUX bootloader.
/boot/extlinux/extlinux.conf:
ui menu.c32
menu title The EXTLINUX bootloader
timeout 100
label Fedora (3.11.1-200.fc19.x86_64) 19 (Schrödinger’s Cat)
kernel /vmlinuz-3.11.1-200.fc19.x86_64
append root=$(grep -w / /etc/fstab | awk '{print $1}') ro rd.dm=0
rd.luks=0 rd.lvm=0 rd.md=0
initrd /initramfs-3.11.1-200.fc19.x86_64.img
$ su -c "yum install syslinux-extlinux"
$ less /usr/share/doc/syslinux-$(rpm -qi syslinux | grep Version | awk
'{print $3}')/extlinux.txt
poma
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
