- This topic has 4 replies, 4 voices, and was last updated Jan 29-1:13 pm by hughtmccullough.
-
Posts
-
hughtmccullough
I am new to antiX but thought I would try it after having been through Debian 6,7,8,9 and 10.
I made an antiX 21 live USB stick using live-USB-maker and this seemed to work fine. I then tried to install antiX on my hard disk. I had a free partition on sda6 (Ext4) and installed to this.
I have Grub on the MBR and this is set up from another OS (LXLE). I would like to keep using this as I spent some time formatting it the way I like it. So, during the install I opted not to install Grub (as I already had it). In LXLE I updated grub and os-prober found the antiX distribution. It is now in the Grub menu. However when I select it during boot I get the error messages:
“no such device: [ID string]
hd1 cannot get C/H/S values
you need to load the kernel first”
There is only one hard disk (actually an SSD). In device.map, the SSD is hd0; hd1 is the USB stick (which isn’t connected any more).
It seems that the boot process needs something from the USB stick.
Did I do something wrong in the boot install process?
Do I need to install again and, if so, what do I do differently during the process? Is there something I can change without going that far?
Brian Masinick
It is important to know – and view – the boot loader lines that point to antiX and verify that they actually point to the correct current location of the installed image, and it’s probably a good idea to examine the partitions and make sure that the contents are installed where you intend them to be installed.
Look in the boot loader directory (if grub, look in /boot/grub and also in /boot/efi if the installation is based on a system with a UEFI boot configuration.
The contents of whatever you find should give you a clear idea of what happened; if you don’t know, share with us and we may be able to provide additional guidance.
--
Brian Masinick
christophe
If you choose to reinstall, you might want to install the boot loader to the root partition. I believe it’s called “pbr” in the installer. Then the LXLE grub should chainload to it (after you do the update grub thing again).
This has always worked for me on legacy bios.- This reply was modified 1 year, 3 months ago by christophe.
confirmed antiX frugaler, since 2019
Anonymous
Normally with only one hard disk Grub does not need
devicemap.Start LXLE.
First check where in both installations (LXLE and antiX21) this file is present. It is called (/boot/grub/device.map)It should be sufficient to delete it and then in LXLE
run update-grub. The USB stick must NOT be plugged in!
If the deleting doesn’t work, you have to execute BEFORE update-grub
grub-mkdevicemap --no-floppy
run.The way suggested here by @christophe of an installation of grub into the PBR of antiX is practical and my preferred way. It is like an extra security of a bootable system if there are problems with the main bootloader.
Write if you want to, it’s only a few commands in the chroot.Thanks for all the replies. Even though I didn’t actually do everything that any of you said, the information has still been very helpful to me.
I’ve spent a bit of time working on this since my initial post but most of that was correcting a mistake I made along the way which was eventually corrected by resetting the boot flag on sda1.
Then I installed grub in the MBR from another Debian OS that resides on a different partition and everything worked.
Then I went back and installed grub from LXLE and again everything worked.
Perhaps the grub set up from LXLE had become corrupted so that initially it didn’t set itself up correctly for antiX. I had only performed an update-grub at that stage, rather than re-installing it. I feel a bit foolish that it was so simple in the end.
When I was investigating, the grub.cfg file that you pointed me to looked perfect. So, perhaps I’ll never know exactly what had gone wrong. Then again, hopefully I won’t need to.
Thanks for your time and help.
- You must be logged in to reply to this topic.
