OK, I had some success and hope maybe some slight changes are done to the next antiX to make it easier.
After seeing errors like:
grub error 15: file not found
and trying to install grub2 which was very simple with a nice gui front end to install the MBR it gave me:
Code: Select all
/usr/sbin/grub-probe: error: /live/aufs is not a block device.
Auto-detection of a filesystem of /live/aufs failed.
Try with --recheck
device node not found
It looks like antiX-M8.5 has the tool I needed under the Applications/Other menu called
MEPIS System Assistant. It is such a primary tool for those who want to install grub either don't have it or want to dual boot windows. It would be nice if that was added to AntiX13.2. The problem seems that the repair grub tool (antix-system.sh) doesn't add the *stage* files needed for grub to install to the MBR. It is basically as easy as just copying /usr/lib/grub/i386-pc/* to /boot/grub on the running linux root partition (not the sda1,sda2 since it's done automatically after you do this step. Note I'm only testing the 386 and not 64 bit. Their might be a different folder for this) It's so nice to read a bit about grub. Some real cool articles on 'tab-completion' for finding files and devices. Anyhow my first suggestion for the next version of antiX is either:
-fixing antix-system.sh (or creating a new grub installer script) so that it copies /usr/lib/grub/i386-pc/* to /boot/grub
-adding it to a separate menu more clear like installing grub or something more intuitive.
Since this antix-system.sh is already in control-centre it could use a rewording:
-rewording 'Configure system' in control centre to something like 'Config Sys & Disk)
and
It's probably important too mentioning it in the frugal instructions I noted in the previous post.
The overall conclusion to get grub installed had 2 steps involved. I ran this a few times in VirtualBox to test it(.
1) Running AntiX-M8.5's tool MEPIS System Assistant ignoring the popup msystem error"Sorry, creating the menu.lst failed. Root filesystem may be faulty. (antiX-system.sh didn't work)
2) Running the following code afterwards
Code: Select all
sudo grub
grub> root (hd0,1)
grub> setup (hd0)
Which basically means
1) Start grub command prompt
2) root (hd0,1) means I'll be using my 2nd partition sda2 to install linux
3) setup (hd0) installs to MBR of first physical drive (sda) where it looks in this partition under /boot/grub for the *stage* files and menu.lst
[Anyone new to grub. They mention many times the convention for naming drives is different in grub and not /sda1 /sda2 etc.]
So basically after that I could do my antiX copying to the partition. In my case it was from /live/boot-dev/antix to /media/sda2/antiX-base and added a new section to the bottom with the slight change to the /media/sda2/boot/grub/menu.lst as so:
Code: Select all
title My antiX frugal hdd install
root (hd0,1)
kernel /antiX-base/vmlinuz quiet bdev=sda2 bdir=antiX-base antiX=LMX nomodeset persist
initrd /antiX-base/initrd.gz
I hope this helps someone else.
Note. Running Rox as root, you can't edit text files (it looses file associates)