IFL boot disk fails

[P19]

After burning an IFL boot disk to CDRW with the included utility, I now see the boot process hanging when trying to boot a PC from it. It reaches the following point and goes no further:

md: Waiting for all devices to be available before autodetect
md: If you don't use raid use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Insert root floppy and press ENTER

When I then press ENTER, it goes into kernel panic

[Bob Coleman]

All I can tell you, which probably isn't any help, is that, in my experience, it should neither request a floppy nor a press of ENTER.

[mjnelson99]

Bob, I agree neither should happen on bootup

Is there a USB stick available to use to create a new boot device?
At least you can just re-record if it doesn't work. Most newer computers
can boot from a USB device unless you get involved with uefi and secure
boot.

On my laptop, I can boot from SD card using a card reader and not from
the reader built into the computer.
Weird??

Also recommend using makedisk.exe to create boot media. Not sure how the
CD was created.

The only change I remember using is to put in the install code so I
don't have a problem using either IFL or IFD later on.
Mary

On 5/25/2014 1:15 PM, Bob Coleman wrote:
> All I can tell you, which probably isn't any help, is that, in

my experience, it should neither request a floppy nor a press of ENTER.
>
>

[Bob Coleman]

mjnelson99 wrote:

> Is there a USB stick available to use to create a new boot device?
> At least you can just re-record if it doesn't work.

True, but I can also re-record a CDRW.

[mjnelson99]

I suggested a different way because it is not working now.
Mary

On 5/25/2014 1:58 PM, Bob Coleman wrote:
> mjnelson99 wrote:
>
>> Is there a USB stick available to use to create a new boot device?
>> At least you can just re-record if it doesn't work.
>
> True, but I can also re-record a CDRW.
>
>

[Brian K]

mjnelson99 wrote:

> On my laptop, I can boot from SD card using a card reader and not from
> the reader built into the computer.
> Weird??
>

Same here.

[P19]

Bob Coleman wrote:
> All I can tell you, which probably isn't any help, is that, in my
> experience, it should neither request a floppy nor a press of ENTER.

Indeed, it has never happened to me before either. I tried remaking the CD from Terabyte MakeDisk utility, but it did exactly the same thing. I was wondering whether the "iflnet.iso" file has a hash file here on the website for me to compare with for integrity, but I can see no such thing. It would help to know whether I have the real McCoy.

[TeraByte Support(TP)]

P19 wrote:
> After burning an IFL boot disk to CDRW with the included utility, I now see
> the boot process hanging when trying to boot a PC from it. It reaches the
> following point and goes no further:
>
> md: Waiting for all devices to be available before autodetect
> md: If you don't use raid use raid=noautodetect
> md: Autodetecting RAID arrays.
> md: Scanned 0 and added 0 devices.
> md: autorun ...
> md: ... autorun DONE.
> VFS: Insert root floppy and press ENTER
>
> When I then press ENTER, it goes into kernel panic

I'm not familiar with this failure mode, but one thing to try would be to use the boot parameter they are suggesting in the 2nd line you quoted above to see if that gets you around it. You can do that by stopping at the initial boot screen, and entering the following at the "boot:" prompt:

boot: 1 raid=noautodetect

There's a 5 second timeout at that screen, but as soon as you type one character within 5 seconds, that cancels the time out.

Note that the above assumes that you are booting a traditional BIOS-based system. If you're booting a UEFI system, you can accomplish the same thing by pressing 'e' at the initial Grub menu, and then insert the same boot parameter after the "/vmlinuz" item on the "linux" line like this:

linux /vmlinuz raid=noautodetect <remainder of the existing line>

Then without doing anything else, press F10 to continue booting.

Also, what was the last IFL version that you used that did not have this problem on that system? IOW, I assume you're using 2.89 now, so was 2.88 OK?

[P19]

> "... I assume you're using 2.89 now, so was 2.88 OK?"

Yes, correct on both counts. I use a regular BIOS boot, not UEFI, and I frequently make use of IFL CD for backing up my primary PC and for working with the several VMs on it, religiously. Normally I would have kept the previous version around until verifying the new one worked perfectly. I have never had an issue until now, but I broke the pattern and, well, this will be the last time I ever again do so. Where can I now get version 2.88 so that I am not without one that works until we have figured out what's going on? Thanks.

[TeraByte Support(TP)]

P19 wrote:
> > "... I assume you're using 2.89 now, so was 2.88 OK?"
>
> Yes, correct on both counts. I use a regular BIOS boot, not UEFI, and I frequently
> make use of IFL CD for backing up my primary PC and for working with the several VMs
> on it, religiously. Normally I would have kept the previous version around until
> verifying the new one worked perfectly. I have never had an issue until now, but I
> broke the pattern and, well, this will be the last time I ever again do so. Where can
> I now get version 2.88 so that I am not without one that works until we have figured
> out what's going on? Thanks.

Ok, please send an email to TeraByte Support (support@terabyteunlimited.com)