You are not logged in.
I sort of borked my grub by messing with menu.lst while grub-gfx was installing itself...and I'm looking at the instructions for reinstalling Grub and I don't understand this command:
mount -t sysfs sys /mnt/sys
What does that do? It didn't work for me...
Last edited by ShadowKyogre (2009-04-17 22:34:18)
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
http://wiki.archlinux.org/index.php/Reinstalling_GRUB
It mounts/creates your sys? The stuff thats usually under /sys.
I think you can also just do the mount partitions and grub steps from the installer (as long as you dont format the partitions). Dont take my word for it though, i would follow the link above if you dont want to risk your data.
Last edited by Chrysalis (2009-04-17 16:35:47)
Offline
Ah...I tried doing that step and it said there's an error.
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
What exactly do you mean, "It didn't work for [you]"? An error message would be helpful. (For example, for all I know, it might be that you don't have a directory under /mnt named 'sys' and simply need to create that directory before issuing the command.)
Anyway, as Chrysalis said, the command simply mounts the sys filesystem (the virtual filesystem that, as far as I understand, is used to export hardware/device information from the kernel to userspace) under the /mnt/sys directory. The command defines the file system type as 'sysfs' (that's what the "-t sysfs" part of the command does) and mounts sys under /mnt/sys.
Offline
It said there was no mount point...
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
Before you issue the command, type:
mkdir -p /mnt/sys
Offline
Ah. Apparently when that error message was created, I mounted my /boot first...
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
The order in which you mount things shouldn't really matter (at least as long as you mount the appropriate things before you chroot).
Offline
Well, I mounted the /boot partition as /mnt @ the time the error occured. I can't seem to remember if sda3 was / or sda1 was /boot or vice versa...I don't know how to see partitions and their sizes from the command line.
Last edited by ShadowKyogre (2009-04-17 17:13:42)
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
fdisk -l will list the partitions and their respective sizes (albeit in blocks rather than MB). To view the partitions on your sda with their respective sizes in MB, you could type:
cfdisk /dev/sda
When you're viewing the partitions in cfdisk, be careful not to make any unintended changes.
Anyway, issue the mkdir command I gave you, if you still get the mount point error after mounting your root partition correctly, and then follow the instructions exactly as listed on the page Chrysalis linked to (which I assume you were following already).
Last edited by RedSocrates (2009-04-17 17:22:00)
Offline
Ah, okay. I can tell which ones will be my appropriate partitions by size since /boot is the smallest, swap is 1/5 of /, and my /home is the largest.
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
Just a reminder that if everything works out for you, you should go ahead and mark this thread as [SOLVED]. Good luck.
Offline
Solved! 8D
The problem was not GRUB itself, but the device string...apparently /dev/sda1 is not the same as what I have now.
Last edited by ShadowKyogre (2009-04-17 22:36:26)
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline