similar to: chain.c32 booting windows off a second disk?

Hi, I'm new to the list. I've replaced grub by extlinux to multi boot my system. Now, I can't manage to boot one of my systems. I have 5 hard drives, 3 of them being part of a raid0 array, and one of them being here for backup purposes (can be removed). So the total 'logical' drives number is 2. First drive: - primary partition holding a rescue Windows XP system (ntfs) -

Hi! Can extlinux boot Linux kernel from the second drive? I want to leave Windows XP on the first IDE drive and put Linux to the first partition (ext2/ext3) on the second IDE drive. I am allowed to change MBR on the first drive. Will the following configuration work? /dev/hda1 - Windows /dev/hdb1 - Linux root (/, /boot, ...) /dev/hda - extlinux in MBR /boot/vmlinuz extlinux /boot

I'd like to use chain.c32 to allow the computer boot from HARDDISK if needed. If I use isolinux and boot from CD, the following works OK: chain.c32 hd0 But if I boot from USB Flash Key, it sometimes work and sometimes it doesn't and I have to use chain.c32 hd1 (it seems BIOS assigns hd0 to the flash key sometimes, so the real harddisk is hd1 in that case). Is there any way to tell

Hi all! Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing the installation, I added a second disk. But when trying to boot from it, I get the following error: --------------------------------------------------------------------- root (hd1,0) Error 21: Selected disk does not exist --------------------------------------------------------------------- The two disks are

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing the installation, I added a second disk. But when trying to boot from it, I get the following error: - --------------------------------------------------------------------- root (hd1,0) Error 21: Selected disk does not exist -

Hi again, I'm still blocked with chain.c32. Does it allow drive swapping like Grub or not? If not, how to boot a Windows system that is located on hd1 1 (instead of regular hd0 1)? Can't find any clue/doc on chain.c32. Thanks

Hi, My problem is I have a particular system which has Linux (LFS) and Windows XP on one drive and Windows 10 on a second drive. I use extlinux to boot my systems and all three systems boot as expected, however in use I have found unsatisfactory interactions between the Windows XP and the Windows 10 systems. My question is: Is it possible on booting one of the Windows systems to hide

On Tue, Oct 20, 2015 at 1:08 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hello, >> >> We are experiencing a strange behaviour on an embedded system (i386 PC board). >> >> The structure of our disk is the following one : >> - A 2GB fat16 partition with DOS and syslinux >> - A 100GB Ext4 partition with Extlinux an several linux images

I wrote a new module "whichsys.c32" which detemines which command to execute, based on the Syslinux bootloader variant. In the near future it should/can be replaced by a lua script. But for people who want small binaries: whichsys.c32 is +/- eighty times smaller than lua.c32, atm. Usage: whichsys.c32 [-iso- command] [-pxe- command] [-sys- command] Examples: whichsys.c32 -iso-

doing that grub-install /dev/sda will give me the "corresponding BIOS device" error. But now I fixed it by doing a manual grub install. first boot with cd1 and type linux rescue at the prompt when you're at the linux prompt after detecting and mounting the partitions, do a "chroot /mnt/sysimage" then # grub --batch #grub> root (hd0,0) Filesystem type is ext2fs,

Author: szhou Repository: /hg/zfs-crypto/gate Revision: c95d7672f710aa2a4b16724397ded8d464b123bd Log message: 6295108 When installing to second disk, grub defaults to hd0 instead of hd1 6322231 bootadm generates incorrect menu when boot partition and root are on separate disks 6322723 boot-file setting in bootenv.rc is not respected in snv_21 and later builds 6331385 adding nexus driver does not

On Thu, Feb 17, 2005 at 16:09:50 -0800, Mikey Sklar wrote > > I use 8MB DOS images with pxelinux to load firmware. Which platform > would you like them for (I have many). I just saw your post and I would definitely be interested in an 8 MB DOS images to work with pxelinux. I have tried the method described in http://people.cs.uchicago.edu/~gmurali/gui/downloads.html but I keep getting

Hello, We are experiencing a strange behaviour on an embedded system (i386 PC board). The structure of our disk is the following one : - A 2GB fat16 partition with DOS and syslinux - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram - A swap partition The system boot on syslinux to choose among Dos and Linux boot using chain. When Linux is chosen, syslinux chains to

On Wed, Aug 5, 2015 at 11:11 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: > On 8/5/2015 1:00 PM, Chris Murphy wrote: >> >> On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com> >> wrote: >>> >>> How would I go about pointing it at the partition? >>> >>> What I am currently doing is this: >>> device

> Hello, > > We are experiencing a strange behaviour on an embedded system (i386 PC board). > > The structure of our disk is the following one : > - A 2GB fat16 partition with DOS and syslinux > - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram > - A swap partition > > The system boot on syslinux to choose among Dos and Linux boot using

Hello, I have two disks sda and sdb. One of the was broken so I have changed the broken disk with a working one. I started the server in rescue mode, and created the partional table, and added all the partitions to the software raid. *I have added the partitions to the RAID, and reboot.* # mdadm /dev/md0 --add /dev/sdb1 # mdadm /dev/md1 --add /dev/sdb2 # mdadm /dev/md2 --add /dev/sdb3 # mdadm

On 8/5/2015 12:34 PM, Chris Murphy wrote: > On Wed, Aug 5, 2015 at 9:12 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> I am trying to upgrade my system from 500GB drives to 1TB. > I'm going to guess that there are no IDE drives that have 4096 byte > physical sectors, but it's worth confirming you don't have such a > drive because the current partition

This adds (basic) support for GRUB stage2 image files. Loading a stage2 image will probably give you a GRUB prompt, with GRUB's "root" set at "(hd0)" (ie, entire first disk). Maybe the "root" will differ in less common setups. (One can of course select another disk and/or partition with GRUB's "root" command.) This has only been tested with version

Dear All: I am having trouble trying to dual-boot VMware and Linux, and I tried everything I could come up with. The situation is that /dev/sda is fully used by VMware and /dev/sdb is used by Linux. VMware uses Syslinux, so I thought this would be simple... However, it is not. The bootable FAT partition is too smal to have kernels in it. As a fallback I tried to chain-load GRUB, but that did not

On 8/5/2015 1:00 PM, Chris Murphy wrote: > On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> How would I go about pointing it at the partition? >> >> What I am currently doing is this: >> device (hd0) /dev/hdg >> root (hd0,0) >> setup (hd0) > > setup (hd1,0) > > It's hd1 if your device map is correct and