Main > Linux
32/64bit Groovy Arcade Linux LiveCD/Install
kevinp:
Can you post an fdisk -l on what this should look like.. been trying to get grub MBR on for hours with no luck
bitbytebit:
--- Quote from: kevinp on March 14, 2011, 11:48:43 pm ---Can you post an fdisk -l on what this should look like.. been trying to get grub MBR on for hours with no luck
--- End quote ---
Basically something like this, creating a swap partition (new partition, change to type 82) of 1 gig or double your RAM.
creating the rest as a normal Linux partition, making sure to set it as bootable
installing to that partition, then choosing it (/dev/sda2) in the MBR menu (MBR menu should suggest the right one actually).
So you'll basically just have everything as the / drive using /dev/sda2, and /dev/sda1 as swap space (won't need a home or data/roms drive). Of course the home/data/roms drives just have more /dev/sda3 and on using the same model as /dev/sda2 below but are not flagged as bootable.
--- Code: ---
Device Boot Start End Blocks Id System
/dev/sda1 1 14 112423+ 82 Linux swap / Solaris
/dev/sda2 * 15 276 2104515 83 Linux
--- End code ---
Hopefully that helps, might be the bootable flag? I need to look at how the arch linux installer did the automatic setup, and try to get that functional in gasetup. Hopefully will have time this week to do that.
kevinp:
Ok, I was going through each menu choice but I didn't realize that the extra partitions were not required...
I followed the instructions and now have
error: unknown filesystem.
grub rescue>
--- Quote from: bitbytebit on March 15, 2011, 07:40:37 am ---
--- Quote from: kevinp on March 14, 2011, 11:48:43 pm ---Can you post an fdisk -l on what this should look like.. been trying to get grub MBR on for hours with no luck
--- End quote ---
Basically something like this, creating a swap partition (new partition, change to type 82) of 1 gig or double your RAM.
creating the rest as a normal Linux partition, making sure to set it as bootable
installing to that partition, then choosing it (/dev/sda2) in the MBR menu (MBR menu should suggest the right one actually).
So you'll basically just have everything as the / drive using /dev/sda2, and /dev/sda1 as swap space (won't need a home or data/roms drive). Of course the home/data/roms drives just have more /dev/sda3 and on using the same model as /dev/sda2 below but are not flagged as bootable.
--- Code: ---
Device Boot Start End Blocks Id System
/dev/sda1 1 14 112423+ 82 Linux swap / Solaris
/dev/sda2 * 15 276 2104515 83 Linux
--- End code ---
Hopefully that helps, might be the bootable flag? I need to look at how the arch linux installer did the automatic setup, and try to get that functional in gasetup. Hopefully will have time this week to do that.
--- End quote ---
bitbytebit:
http://www.supergrubdisk.org/
Try that, it might be a quick fix to grub for now. I need to look into things more, one check also before rebooting after install would be to check and send me the contents of /groovyarcade/boot/grub.conf (where the install mounts the / partition) and possibly of 'fdisk -l' too.
I think that disk claims to fix grub installations, it's worth a shot until I can figure out more, and possibly would see what is going on pretty quickly if your able to get those two fdisk and grub.conf output/file information.
This link seems like the right one for what we need...
http://www.supergrubdisk.org/super-grub-disk/
kevinp:
Hi,
My partition table looks exactly like yours including the bootable flag set. GRUB seems to install without any complaint, yet I still get the same error.
Maybe I'll revisit this in a few versions but its waaay too complicated just to get booting for me. Looks like back to Windows for now.
Thanks
--- Quote from: bitbytebit on March 15, 2011, 05:25:26 pm ---http://www.supergrubdisk.org/
Try that, it might be a quick fix to grub for now. I need to look into things more, one check also before rebooting after install would be to check and send me the contents of /groovyarcade/boot/grub.conf (where the install mounts the / partition) and possibly of 'fdisk -l' too.
I think that disk claims to fix grub installations, it's worth a shot until I can figure out more, and possibly would see what is going on pretty quickly if your able to get those two fdisk and grub.conf output/file information.
This link seems like the right one for what we need...
http://www.supergrubdisk.org/super-grub-disk/
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version