Hy,
I want to do the HDInstall to a SD Card wich is inserted in a eeePC901 SD-Card Slot. When I boot up from an USB-Stick with the grml Live-Image and choose HDInstall all seems to be Ok. But after reboot grml always failed to load (no OS found). I also tryed to install the bootmanager into partition /dev/sdd1 and MBR of /dev/sdd but no effekt. The internal SSD I do not want to have edited with the bootmanager. If I look on the SD-Card there seem to be all files. Is there a way that this could run?
best regards Henrik
I have noticed that grml2hd (I use it to put grml onto a usb key) sets up grub (I know grub so I always chose to install it over lilo) to boot from the second hard drive. i.e. (hd1,0) (that is likely where it was was when the live version was run) But when you want to boot it, the hardware has detected it first and put it in the first position (hd0,0). If this is the case for you, you will have to muck about in the boot manager to resolve the problem.
2009/7/24 wonderer wonderer4711@gmx.de
Hy,
I want to do the HDInstall to a SD Card wich is inserted in a eeePC901 SD-Card Slot. When I boot up from an USB-Stick with the grml Live-Image and choose HDInstall all seems to be Ok. But after reboot grml always failed to load (no OS found). I also tryed to install the bootmanager into partition /dev/sdd1 and MBR of /dev/sdd but no effekt. The internal SSD I do not want to have edited with the bootmanager. If I look on the SD-Card there seem to be all files. Is there a way that this could run?
best regards Henrik _______________________________________________ Grml mailing list - Grml@mur.at http://lists.mur.at/mailman/listinfo/grml join #grml on irc.freenode.org grml-devel-blog: http://grml.supersized.org/
On Fri, 24 Jul 2009 16:41:21 -0400, Sean Kennedy wrote:
I have noticed that grml2hd (I use it to put grml onto a usb key) sets up grub (I know grub so I always chose to install it over lilo) to boot from the second hard drive. i.e. (hd1,0) (that is likely where it was was when the live version was run) But when you want to boot it, the hardware has detected it first and put it in the first position (hd0,0). If this is the case for you, you will have to muck about in the boot manager to resolve the problem.
If it is the case, then the best solution is
Boot by UUID or disk label http://xpt.sourceforge.net/techdocs/nix/disk/boot/boot03- LinuxSpecificBooting/ar01s03.html
I.e.,
Stable root device (AKA UUID) http://michael-prokop.at/blog/2006/08/11/stable-root-device-aka-uuid/
HTH
participants (3)
-
Sean Kennedy -
T o n g -
wonderer