I tried to boot from my 6.0 USB key, no joy. Updated it to 6.2. Still no
joy: it gets started, I do the disk layout, it formats the drives, and
then fails, saying that it can't find "image# 1". Over in the log,
I see a
lot of it not finding any drive at all, yet all the h/d drives and sda2,
which is what the USB key is, and where the linux partition is, are
mounted.
Guys, any idea what "image# 1" is, or what configuration file is
telling
it to look in a wrong place?
Thanks in advance.
mark
> I tried to boot from my 6.0 USB key, no joy. Updated it to > 6.2. Still no joy: it gets started, I do the disk layout, it formats > the drives, and then fails, saying that it can't find "image# 1".Can you tell us how you're making the bootable USB key? e.g. the source .iso file[s] and all commands used.
From: "m.roth at 5-cent.us" <m.roth at 5-cent.us>> I tried to boot from my 6.0 USB key, no joy. Updated it to 6.2. Still no > joy: it gets started, I do the disk layout, it formats the drives, and > then fails, saying that it can't find "image# 1".Works fine here... On some PCs/servers the key is sdb... syslinux.cfg: append initrd=initrd.img ks=hd:sda2:/ks.cfg repo=hd:sda2:/centos ks.cfg: harddrive --partition=sda2 --dir=/centos /centos contains images/install.img and the DVDs ISOs... JD
Again, I *HATE* dnsorbs.... This was bounced, which makes twice today. <snip> more text, add a few more words, we'll see if this makes it. John R Pierce wrote:> On 01/09/12 12:05 PM, m.roth at 5-cent.us wrote: >> John R Pierce wrote: >>> > On 01/09/12 11:11 AM,m.roth at 5-cent.us wrote: >>>> >> They are? I dunno - ours are labelled where they're intended tobe mounted, like / or /boot>>> > >>> > don't plug one of those into a different system for repair oryou'll have all kinda grief. $HOSTNAME_root would be the sane way to do>>> it... >>> > >> I'm trying to figure out why I'd plug one into a different system forrepair. Either the drive's bad, or I'm re-embodying a server that died, but left good drives. If it's going bad, the*only* thing I'm going to do is plug it into a hot-swap bay (just about all of ours have those, love them) to recover some data, then wipe it.> > exactly. and if you put that drive in a hotswap bay of another system > that is using the same label, thats a potential for a big mess. same<snip> Why? If I shove it into another system, I'm *not* rebooting using it, just putting it into a spare bay; then I'll mount /dev/sd<whatever> /mnt. No problem. But this thread's gotten way OT: *does* anyone have any idea what the .img file is that the running o/s from install.img is looking for, after the partitioning, when it's ready to install? mark
> But this thread's gotten way OT: *does* anyone have any > idea what the .img file is that the running o/s from install.img > is looking for, after the partitioning, when it's ready to install?Possibly, but without the info I previously requested, I won't be trying to reproduce the problem. e.g. the source file[s] and command[s] used to make your bootable USB stick.
On Tuesday, January 10, 2012 17:53 [UTC -5], Darr247 spake thusly:> I did not see that synopsis in your original post (and I'm not sure I > could figure out what commands you used by that). > The only 2 replies to this thread I saw in digest 84 issue 9 were to > John Doe. > > Anyway, this is what I have in my notes, though I see you've marked > this as solved... > > mostly assuming sdb as the USB device. > > From blank USB stick to bootable install: > > yum install livecd-tools syslinux > dd if=/dev/zero of=/dev/sdb bs=512 count=1000 > parted /dev/sdb mklabel msdos > parted /dev/sdb mkpartfs p ext2 0% 100% > tune2fs -m0 /dev/sdb1Oh, and sometimes the tune2fs command isn't needed. If I recall, it's needed only if the stick has never been formatted.> parted /dev/sdb toggle 1 boot > umount /dev/sdb1 > livecd-iso-to-disk <path to>/DVD.iso /dev/sdb1 > > mkdir /mnt/iso > mount -o loop <path to>/DVD.iso /mnt/iso > mkdir media<usb stick>/images > cp /mnt/iso/images/install.img media<usb stick>images > cp <path to>/DVD.iso /media/<usb stick>/ > > TEST: > qemu -m 512 /dev/sdb > > > I guess I should add > yum install qemu > to my notes, as I don't think that's installed by default. > > But using livecd-iso-to-disk makes it NOT ask for the image file > location during the install. Try it. > > Personally, I think they should've named it bootable-iso-tools, but > everyone's probably used to the livecd-tools name by now.
On Tuesday, January 10, 2012 17:53 [UTC -5], Darr247 spake thusly:> I did not see that synopsis in your original post (and I'm not sure I > could figure out what commands you used by that). > The only 2 replies to this thread I saw in digest 84 issue 9 were to > John Doe. > > Anyway, this is what I have in my notes, though I see you've marked > this as solved... > > mostly assuming sdb as the USB device. > > From blank USB stick to bootable install: > > yum install livecd-tools syslinux > dd if=/dev/zero of=/dev/sdb bs=512 count=1000 > parted /dev/sdb mklabel msdos > parted /dev/sdb mkpartfs p ext2 0% 100% > tune2fs -m0 /dev/sdb1Oh, and sometimes the tune2fs command isn't needed. If I recall, it's needed only if the stick has never been formatted.> parted /dev/sdb toggle 1 boot > umount /dev/sdb1 > livecd-iso-to-disk <path to>/DVD.iso /dev/sdb1 > > mkdir /mnt/iso > mount -o loop <path to>/DVD.iso /mnt/iso > mkdir media<usb stick>/images > cp /mnt/iso/images/install.img media<usb stick>images > cp <path to>/DVD.iso /media/<usb stick>/ > > TEST: > qemu -m 512 /dev/sdb > > > I guess I should add > yum install qemu > to my notes, as I don't think that's installed by default. > > But using livecd-iso-to-disk makes it NOT ask for the image file > location during the install. Try it. > > Personally, I think they should've named it bootable-iso-tools, but > everyone's probably used to the livecd-tools name by now.