similar to: Do I need LILO or Grub for pxelinux network booting

I am having a problem where my newly cloned system (created using pxelinux) boots up with the filesystem mounted read-only. It is then impossible to log in. This is what I have done so far: I boot the server using pxelinux. Then there is a script in the ramdisk that is be used to create the filesystem (ext2), mount everything up, get a tar file containing all files from an identical system,

Hello all! I would like to know if is possible to use LILO as the boot loader instead of the default GRUB. My question comes because I tried to run lilo command but the message "command not found" appear. It sounds like my only boot loader option in CentOS is GRUB ??. I found lilo.conf.anaconda, but not the lilo command. From already thanks. Regards, Juan P. Espino

I just adore the install. Esp. of GRUB. Does *anyone* who works on GRUB actually work in the real world, and not only on brand new machines? I just had happen at work what happened last fall on my home system: then, I had /dev/hda, and was trying a clean install on a new SATA drive; right now, I'm installing on a replacement disk on a server that has no CD/DVD drive from a USB key. My

Hello list, I have a question concerning the possibility of booting one of two Windows systems installed on two partitions. In case with one Windows system and one Linux system, I can chainload grub or windows loader, and this is OK. But in case with two Windows systems, when I installed second system, the installer added multi boot loader(I think it's called bootmgr), and then I can't

Hello again, I'm always not able to boot-up my CF-FileSystem. (It works with a 2.4.x Kernel!) See: http://syslinux.zytor.com/archives/2006-June/006942.html I dont't understand, why the kernel can't mount the root-fs on exit of "linuxrc". Before finising "linuxrc" I can work on it, start a "bash"-shell, do all sorts of linux-cmds on the root-fs...

I have a pxelinux I'm working with and I want the default option to be to boot off the local mbr. According to the docs, if I specify localboot 0, it should return to the BIOS and continue to the next device. When I do this, though, the pxe agent exists (PXE-M0F), but the BIOS never continues on. Is this a BIOS issue? If so, has anyone else figured out a way to work around it? * Philip

Hi all I'm guessing this is a little off topic but here goes... We use PXELINUX and kickstart to automate our RHEL deployments and updates. Recently we started using PXELINUX/memdisk and an MS-DOS image to update the workstation BIOS'es. After selecting <F12> (network boot) and picking the update BIOS option, the BIOS is flashed, BIOS configuration made standard and then the

I'm still having conceptual trouble with this one. I have two PATA and two SATA disks in my home system. When the system comes up, these are, espectively, /dev/hda, /dev/hdb, /dev/sda and /dev/sdb. I have the boot order of the drives in the boot PROM set to boot from /dev/sda (hard drive 2), then /dev/hda (hd 0), and usually that works fine. /dev/sda is properly set up with the MBR and

hi, i ve grub in the mbr of my usb stick and now i am not longer able to use the syslinux bootmanager. i tried to delete grub from mbr with: dd if=/dev/null of=/dev/sda bs=512 count=1 but nothing changed grub is still in the mbr hope somebody can help me thx so long

Are there any tools for working with and moving or copying the MBR? My machine has 2 PATA drives (hda & hdb) and 2 SATA drives (sda & sdb). The MBR is on hda, but I would like (eventually or sooner) to boot from sda because it is two years newer, faster and, hopefully, more reliable. Even if I don't change that, I'd like a backup MBR on sda in case hda fails (hdb has gone sour a

greetings, i just know i have read several times on this list and in other places that on a RAID5 array that the MBR should be placed on the /boot partition. is this truly correct and if so, why? my experiences of putting the MBR on the /boot partition are contrary to that it will even work and boot that way... comments please? regards, - rh -- Robert Hanson Abba Communications

With Centos3, fedora1/2 I have been able to put /boot on a RAID1 partition and have it boot normally. Unlike earlier versions that used lilo as the default boot loader, these did not make the 2nd drive bootable but at least I was fairly confident that if the first drive failed I could use the install CD in rescue mode to fix up the 2nd one and go on. However, Centos4 won't boot at all with

Hi, I do seem to have a slight problem with upgrading two of our machines to CentOS (from SuSE, but that doesn't really matter). Both systems are IBM x-Series 360 with a ServeRaid controller for the "internal" hard disks an a QLogic QLA2200 fibre channel controller for an external stack of disks. On SuSE (kernel 2.4.26) the ServeRaid is controller 0 (resulting in the internal Raid

Windows uses several sectors in the _partition_ for booting. Windows only uses sector 0 of the Disk (the MBR), and does not use any other sectors. Other boot managers and copy protection software (the stuff that comes with TurboTax this year uses track 0, evil...) For FAT16 filesystems, only the first sector is used. For FAT32, there are 32 sectors that are reserved by the FS, and I've come

> It's source code looks like a BIOS MBR program which shall search > the "active" partition in GPT rather than in the MBR partition table. > See comments about "EBIOS" detection and "CHS" addresses in > https://github.com/geneC/syslinux/blob/master/mbr/gptmbr.S > > "Active" partitn would be the one which has bit 2 set in the

For reasons I won't get into, I need to use grub (not grub4dos, super grub, or any other variant) as multiboot loader on a USB thumb drive, but I also need some of the partitions to contain bootable content from syslinux-based ISOs. All of these syslinux partitions must be logical rather than primary partitions and they will not be the first partition on the drive. Porting the syslinux

Hi, > In theory, the geometry assumed in the MBR should > match the one assumed by the BIOS. To be exacting: The geometry assuming part of the MBR is the partition table, not the executable MBR code. Of course it would be nice if C/H/S was not such a brain damaged concept which has two semi-secret parameters. The geometry parameters are not recorded anywhere in the MBR. One can sometimes

> The wiki I think should at the very first direct you to the correct > 'variant' for what media you are installing to (extlinux for me). As it > is, on the web all the variants are often referred to generically as > 'syslinux', and it's not till latter that you realize that you must find > the correct variant. It would also be nice (tho probably much work),

Greetings: I'm upgrading a fileserver running 3.4 (upgrade to a larger disk). I backed up the data from the "old" disk and slapped in a newer, larger disk and installed Centos-3.4. No problems. Now, there are some files on the "old" disk that I forgot to move to the back-up disk, so I'd like to mount the "old" disk as /dev/hdd and reboot the system and

Hi, I have a raid 1 setup where /boot and the rest lies inside the md0 container. /dev/sda1 md0 has /boot /dev/sda2 md0 has swap /dev/sda3 md0 has / SCSI card is an ADAPTEC AIC79xx Grub as the bootloader Centos 4.1 as the OS version Two 70gb SCSI disks The server was working fine. Then a power outage. checked the board,disk,ram,etc. All fine. Now when I try to boot the server does not even reach