Post by howarddavidp on Jan 18, 2013 12:56:22 GMT 7
Hello,
With my new console added, I wanted to be able to see GRUB and make changes, if needed. I am thinking about going with a DUAL DOM, have a SLAVE on the IDE channel boot to something else. I would still be able to boot into THECUS Linux if needed, but I have seen cables that support 2 x 44pin IDE devices.
SO, here is the process:
#1 - Get to console access, via SSH or the console if you have it.
#2 - mkdir /raid0/data/boot (makes a mount point for the boot part)
#3 - mount /dev/hda1 /raid0/data/boot (the entire DOM is hda, the 1st part is hda1)
#4 - vi /raid0/data/boot/boot/grub/menu.lst
My file looked like: (change the timeout to 10, it is set to 1 by default)
#boot=/dev/hda
default=0
timeout=10
serial --unit=1
title Normal
root(hd0,1)
setlogo N5200p
setbto 200
kernel (hd0,1)/bz5200v1 ro root=/dev/ram0 ramdisk=61440
initrd (hd0,1)/n5200fs.gz
With my new console added, I wanted to be able to see GRUB and make changes, if needed. I am thinking about going with a DUAL DOM, have a SLAVE on the IDE channel boot to something else. I would still be able to boot into THECUS Linux if needed, but I have seen cables that support 2 x 44pin IDE devices.
SO, here is the process:
#1 - Get to console access, via SSH or the console if you have it.
#2 - mkdir /raid0/data/boot (makes a mount point for the boot part)
#3 - mount /dev/hda1 /raid0/data/boot (the entire DOM is hda, the 1st part is hda1)
#4 - vi /raid0/data/boot/boot/grub/menu.lst
My file looked like: (change the timeout to 10, it is set to 1 by default)
#boot=/dev/hda
default=0
timeout=10
serial --unit=1
title Normal
root(hd0,1)
setlogo N5200p
setbto 200
kernel (hd0,1)/bz5200v1 ro root=/dev/ram0 ramdisk=61440
initrd (hd0,1)/n5200fs.gz