Unable to boot into MX-14 [SOLVED]

rmcellig · posted: 2014-12-09 15:24

I was messing around with a partition on my HD. Now when I go to boot up my laptop into MX-14 (SDA6), it hangs on startup. I'm now in my Antix partition and noticed that the initrd.img file cannot be located from the shortcut. What should I do?

dolphin_oracle · posted: 2014-12-09 15:39

where does the boot freeze?

which boot loader controls. the grub-legacy in antiX or the grub2 in MX?

post the menu.lst for grub-legacy/antiX or grub.cfg for grub2/MX (whichever controls your bootup) and run the following command:

blkid

and post the results.

did you add the symlinks for initrd.img and vmlinuz? the symlinks don't exist on my mx system. i would check the properties for the symlink and make sure the target still exists.

rmcellig · posted: 2014-12-09 16:14

I created the Grub menu using grub4dos in puppylinux after booting from the puppy linux CD. Should I create a new Grub menu? If so how exactly do I go about doing this. I always use Grub Customizer.

Code: Select all

$ sudo blkid
/dev/sda2: UUID="3b601691-7cec-49e2-9e69-522fd203e468" TYPE="swap" 
/dev/sda3: LABEL="cb11" UUID="58d5ea6f-9d72-4ccc-81ae-aee1db164ffa" TYPE="ext4" 
/dev/sda4: LABEL="manjaroxfcedv6" UUID="afcfd8d5-acd0-4858-b983-bd1927bb7c76" TYPE="ext4" 
/dev/sda5: LABEL="puppy6" UUID="26fb4550-64e7-497d-b7f6-35bc30460550" TYPE="ext4" 
/dev/sda6: UUID="da9b99a9-39cd-487d-bf8f-ac670251127a" TYPE="ext4" 
/dev/sda7: UUID="45adab81-41d7-4a43-b70b-1a6497ab623a" TYPE="ext4" 
/dev/sda8: UUID="3d2cba3f-cf44-4179-a735-c34f302ac4ab" TYPE="ext4" LABEL="drive" 
/dev/sdb1: LABEL="mainserver" UUID="ed4c39cc-4501-40b1-a07b-ce2b82c2cd0e" TYPE="ext4" 
/dev/sdc1: UUID="439CFABD39028E38" TYPE="ntfs" 
randy@antiX13:~

dolphin_oracle · posted: 2014-12-09 16:21

roky is the grub4dos guru around here. but I would hazard a guess that the symlinks for initrd.img and vmlinuz are pointing to the wrong targets. either that, or when you changed around partitions, the /dev/sdaX designations are wrong. the antiX and mx bootloaders specify boot partition by UUID, which is unique to each partition. /dev/sdX designations are subject to change, especially if you've created or moved partitions.

uuid do change on format, so that is something to look for as well. I would check the symlinks first to see if they are pointed at the right files. Then check whatever grub4dos uses to specify the boot entries to make sure that file is pointed to the correct partition.

rmcellig · posted: 2014-12-09 16:25

I used grub4dos because I was caught in a pinch and needed a way to boot back up. Once I can get into MX-14, I will use Grub-customizer to overwrite the menu created by Grub4Dos.

Where would I find the menu.lst file that was created by Grub4Dos. When I created it, it was saved in sda, and not any particular partition.

rmcellig · posted: 2014-12-09 17:04

I'm back in business. Dolphin_oracle, your suspicions were right. I found a boot repair CD I have and recreated the Grub menu. I'm now back into MX-14. Looks good! __{{emoticon}}__