dual boot headache <SOLVED>

jdmeaux1952 · posted: 2014-02-19 02:39

On my JUNKBOX, I have antiX 13.2 installed on the hard drive (as sda1), using about 29 Gb of a 40 Gb drive. Earlier this morning, I was messing with Mepis-14, and decided to install that on the rest of my hard drive as sda2.(I had only gotten about 3 hours of sleep before that with this stupid cold.) I THINK I may have run Grub on MBR instead of Root(??). Since then all the computer does is start GRUB then goes to MEMTEST. Yup! A cold reboot shows Grub loading up then MEMTEST. That is all it does. __{{emoticon}}__

What I was trying to do was to get Grub to show both antiX 13.2 AND MEPIS-14 as choses so I could work back and forth between them. Since I am very ignorant (actually can't remember s**t most of the time) about Grub, where would I start to look at between the two OS's to make adjustments to this effect? Right now I have to use a LIVE cd to get into the system, but really have no idea where to start searching at to make adjustments. __{{emoticon}}__ I stopped using the machine about the fifth time I rebooted after this error so I wouldn't screw it up too much.

rokytnji · posted: 2014-02-19 03:00

Reinstall grub with AntiX live to mbr of drive. Reinstall grub for MX14 to root folder instead of mbr.
Chainload MX14 through AntiX grub legacy.

Google search chainload AntiX rokytnji and my grub posts should show up in google search.
I am not in my shop right now to show how I use grub4dos and chainload my MX14 install with
a MacPup 529 frugal install. If you wait till tomorrow. I'll post my menu here later.

Sorry. Best I can do for ya tonight.

jdmeaux1952 · posted: 2014-02-19 03:10

Thanks roky. Any little bit will help. I'll do what I can tonight. And then get some sleep I hope. I've had about 8 hours total over the last 8 days from this chest / head cold.

dolphin_oracle · 19 Feb 2014, 03:28 #4 2014-02-19 03:28

On my MX install, I think antix shows up as Debian, maybe under"advanced" options. I didn't do that on my main lappy, but I think the netbook worked like that.

Eino · posted: 2014-02-19 12:12

jdmeaux1952 wrote:On my JUNKBOX, I have antiX 13.2 installed on the hard drive (as sda1), using about 29 Gb of a 40 Gb drive. Earlier this morning, I was messing with Mepis-14, and decided to install that on the rest of my hard drive as sda2] I may have run Grub on MBR instead of Root(??).
.

I think the issue comes in using sda2 as an install partition. sda2 is reserved for the swap partition used by the systems installed. If your system has low memory resources it may be a real issue.
Running Grub on the MBR is right it usually updates correctly.
Here is a correct dual boot install shown in GParted.
Now you need to use gpared to rebuild your swap partition, then make a partition for your secondary install.
During your secondary install running Grub to MBR may correct things, If not you will need to edit the menu.1st. so you can boot your primary install.
If will notice I'm booted in sda3 my secondary install, so in gparted the mount point of sda1 shows media.

jdmeaux1952 · posted: 2014-02-19 17:15

As I said before, I used 29 Gb of hd0 as sda1, leaving the rest as unallocated (sda2). My USB drive 6Gb was being used as 1.25Gb for Linux swap and the 4.75Bg as sdb1. This setup originally was giving me the fastest (quickest) access to my drives, and although not super fast, the system was purring along. My swap never got over 40Mb regardless of what I was installing or trying to do. Yes, I was using dolphin's videos as guides to tinker with the system. At least I was smart enough to use the USB drive sdb1 for my Downloads, Wallpaper, and Avatars, so if I reinstall antiX and M-14 on sda, I still have my stuff.

I had been tinkering with M-14 on a LIVE cd, and then decided to install it on the unallocated portion of my drive. Installation went forward well, but when I got to the Grub install, I believe I DID install grub on the MBR. Upon rebooting, the JUNKBOX begins to load Grub, but what I can't figure is why it goes directly into MEMTEST, with no other choices. __{{emoticon}}__ I rebooted with the same thing happening. __{{emoticon}}__

What I want to do is to set Grub up to load and allow me to choose between antiX 13.2 AND M-14 plus the MEMTEST. But now it only automatically goes into MEMTEST. Here's my basic questions. (1) - Should I include a swap file on the hd0, using 29 Gb for antiX, 10 Gb for M-14, and 1 Gb swap? (2) - Where should I be looking to edit the grub file? In antix or in M-14?

Eino · posted: 2014-02-19 17:38

OK I misunderstood your post, I thought you named sda2 as your install partition.

rokytnji · posted: 2014-02-19 17:41

Not reading your latest post because I am in a hurry/(busy)

Code: Select all

# menu.lst produced by grub4dosconfig-v1.7.2
color white/blue black/cyan white/black cyan/black
timeout 10
default 0

# Frugal installed Puppy

title Macpup 529 (sdb1/macpup529frugal)
  find --set-root --ignore-floppies --ignore-cd /macpup529frugal/initrd.gz
  kernel /macpup529frugal/vmlinuz   psubdir=macpup529frugal pmedia=atahd pfix=fsck
  initrd /macpup529frugal/initrd.gz

title Macpup 529 (sdb1/macpup529frugal) RAM mode\nBoot up Puppy without pupsave
  find --set-root --ignore-floppies --ignore-cd /macpup529frugal/initrd.gz
  kernel /macpup529frugal/vmlinuz   psubdir=macpup529frugal pmedia=atahd pfix=ram,fsck
  initrd /macpup529frugal/initrd.gz

# Full installed Linux

title MX12 Beta1 (sdb2)
rootnoverify (hd1,1)
chainloader +1

# Boot from Partition Boot Sector
# additionals
title Bootup from HDD\nBootup from the master boot record of the hard disk drive
  map (hd1) (hd0)
  map (hd0) (hd1)
  map --hook
  chainloader (hd0)+1

title Find Grub2\nBoot up grub2 if installed
  find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
  kernel /boot/grub/core.img

title Grub4Dos commandline\n(for experts only)
  commandline

title Reboot computer
  reboot

title Halt computer
  halt

grub4dos menu.lst is pretty much like default grub in AntiX. So it is easier to deal with for me than grub 2.

To be honest. I know AntiX has a Mepis Assistent for repairinjg grub and user and that was why I suggested repairing grub with a AntiX live session. The assistent is in the menu or control center somewhere. I am a bit in a rush so I can't remember presently or am on mu AntiX box anyhows. I am on my MX14 beta2 to post this reply.

My pic for how my Puppy/Mx14 install looks

Code: Select all

Disk /dev/sda: 160 GB, 160039272960 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System 
/dev/sda1               1       18096   145356088   83  Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sda2           18096       19458    10940265   83  Linux
Warning: Partition 2 does not end on cylinder boundary.

Disk /dev/sdb: 40 GB, 40015987200 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System 
/dev/sdb1   *           1        1167     9373896   83  Linux
/dev/sdb2            1168        4723    28555537   83  Linux
/dev/sdb3            4724        4865     1132582   82  Linux swap

My installs are on /dev/sdb because it is only a 40gig drive. My /dev/sda is storage because it is 160gig drive. This iBM M41 is kinda a equivelant of your junkbox. I have had this thing for ages and it just won't die on me yet so I keep it upgraded.

male · posted: 2014-02-19 18:25

connect the USB HDD to
they start the computer with the Live CD antiX or MX14
they open a terminal and become root
enter the following commands

Code: Select all

 mount /dev/sda2 /mnt
 mount --bind /dev/ /mnt/dev
 mount --bind /proc/ /mnt/proc
 mount --bind /sys/ /mnt/sys
 mount --bind /dev/pts /mnt/dev/pts
 mount --bind /run/ /mnt/run         
 chroot /mnt /bin/bash
 grub-install /dev/sda
exit
exit

reboot

installs the Grub to the MBR of sda.

dolphin_oracle · posted: 2014-02-19 19:12

if you used the mx installer to install grub, then you've got two issues. MX uses Grub 2 which is harder (in my opinion) to edit.

but the config file will be in the mx partition.

jdmeaux1952 · posted: 2014-02-19 19:48

@dolphin - thanks. From what I have read elsewhere, I do have a problem dealing with 2 GRUBS (and I'm not even hungry.) It appears that the Grub 2 from MX-14 crashed somewhere (either a bad sector or a bad write), leaving only the MEMTEST available. I'll start looking there to see what I can figure out.

@male -- Danke. I'll try and see if this works.

@roky -- I'll try it your way first with antiX LIVE cd. Hey, I'm trying to learn something here. I can do a shovel and a panhead. But linux is a relearning experience.

male · posted: 2014-02-19 19:50

@ dolphin
sorry, that's irrelevant.
then

male wrote:

Code: Select all

...
chroot /mnt /bin/bash
grub-mkdevicemap
update-grub
grub-install /dev/sda
..

Disadvantage, the USB HDD must always be connected.

(the config files it should not edit)

It is therefore better MX14 reinstall and losing sight create the swap with on sda.

dolphin_oracle · posted: 2014-02-19 20:32

depending on which beta you were playing with, you might be able to use grub customizer to save a new grub.cfg and reinstall to the mbr, although I bet the new grub.cfg might be all you need.

that said, grub2 is confusing to me at the moment. I'm sure I'll get used to it, but its black-magic at the moment.

jdmeaux1952 · posted: 2014-02-20 02:08

dolphin_oracle wrote:depending on which beta you were playing with, ,,,at said, grub2 is confusing to me at the moment. I'm sure I'll get used to it, but its black-magic at the moment.

I have installed MX-14 Beta2 BEFORE the deltas. I was going to add in the deltas after I got it installed for a dual boot. But then this headache. I'm getting ready to go play on the JUNKBOX in a few to correct the grub config.

jdmeaux1952 · posted: 2014-02-21 10:16

Well, solved this one. As I had said, the harddrive had been partitioned into 3 parts; sda1 for my antiX, sda2 for MX-14, and I added a third partition (sda3) as a swap-file. If I simply turned on the JUNKBOX as you normally would, grub started but went into MEMTEST. __{{emoticon}}__ Now my problem was to figure how to get grub to act as a dual-boot menu for antiX 13.2 and MX-14.

Roky gave me advise on Google searching

chainload AntiX rokytnji

. The very first result as a link back to this forum on editing menu.lst (post29136.html) where anti told them to make an addition. I edited my menu.lst on sda1 (antiX partition), adding reference to MX-14.

timeout 5
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title antiX at sda1, kernel 3.7.10-antix.5-486-smp
root (hd0,0)
kernel /boot/vmlinuz-3.7.10-antix.5-486-smp root=/dev/sda1 quiet
initrd /boot/initrd.img-3.7.10-antix.5-486-smp
boot

title MX-14 Beta2 at sda2
root (hd0,1)
chainloader +1

As you can see, I simply added reference to my MX-14 partition sda2, I rebooted the JUNKBOX and now grub gave me a choice between antiX 13.2 and MX-14. However, something else was wrong because selecting MX-14 brought me to MEMTEST. __{{emoticon}}__ __{{emoticon}}__

I re-installed MX-14 with the grub loader now set to / root. Now everything works like it should. Apparently something happened to my original installation of MX-14 (which I had set grub to MBR). And now it works. __{{emoticon}}__ __{{emoticon}}__

IT'S ALIVE Thanks everyone for the suggestions and help.