Re: Booting from HP SAN
Then you guys explain to me this.... here is the Fdisk of the Intall from the one computer that your install works on (not using the debian method)
This doesn't work on the HPs
Now, the way I partition the HPs to make them work.
This works.... and My boot is 2GIG incase I need to play, but under HPs limit.
Now, is it the LVM or is it the way the bootloader is install? With the debian install, the bootloader in on the MBR. what are you doing? Either way, there are two pieces that will not allow a pc to see the boot. One is the partition and the other is how the bootloader is install. Either case, we need the control over the install to work with the BIOSes of these PCs... End of story here...
All my HPs have been removed from the LUN and have their own drives to which they couldn't boot without me using the debian method. Think you need to relook at how their install functions and use that approch with the partitioning and GRUB install. I don't really care about the graphics of the install, I more interested in functionality.
Then you guys explain to me this.... here is the Fdisk of the Intall from the one computer that your install works on (not using the debian method)
Code:
Disk c0d0: 119.9 GB, 119998218240 bytes
255 heads, 32 sectors/track, 28722 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
c0d0p1 * 1 129 524288 83 Linux
Partition 1 does not end on cylinder boundary.
c0d0p2 129 28722 116661440 8e Linux LVMNow, the way I partition the HPs to make them work.
Code:
Disk c0d0: 119.9 GB, 119998218240 bytes
255 heads, 63 sectors/track, 14588 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0009e5a9
Device Boot Start End Blocks Id System
c0d0p1 * 1 243 1951866 83 Linux
c0d0p2 244 729 3903795 82 Linux swap / Solaris
c0d0p3 730 14588 111322417+ 83 LinuxNow, is it the LVM or is it the way the bootloader is install? With the debian install, the bootloader in on the MBR. what are you doing? Either way, there are two pieces that will not allow a pc to see the boot. One is the partition and the other is how the bootloader is install. Either case, we need the control over the install to work with the BIOSes of these PCs... End of story here...
All my HPs have been removed from the LUN and have their own drives to which they couldn't boot without me using the debian method. Think you need to relook at how their install functions and use that approch with the partitioning and GRUB install. I don't really care about the graphics of the install, I more interested in functionality.
