Skip to contentSkip to conversation

Booting from tape

parisc-linux Ulrich Strelow 6 participants 6 messages Sep 28, 1999

lore
Share & tools
lore
#0 lore raw

I know that this is extremely low priority but...

I have tried to boot the linux kernel from a SCSI DDS tape (copied via dd if=Image of=/dev/rmt/0m bs=512). The same kernel (cvs tree from today) boots sucessfully via rbootd on my 715/33. Here is the console log:

(c) Copyright Hewlett-Packard Company,
1991, 1992
Portions of this code are (c) Copyright Samsung Electronics Co., Ltd, 91, 92

PDC ROM rev. 1.4
IODC ROM rev. 1.2
48 MB of memory have been configured.

Selecting a system to boot.
To stop selection process, press and hold the ESCAPE key.

Selection process stopped.

Searching for Potential Boot Devices.
To terminate search, press and hold the ESCAPE key.

Device Selection Device Path Device
Type
----------------------------------------------------------------------------

P0 scsi.6.0 HP
C3324A
P1 scsi.3.0 HP
C2490AM
P2 scsi.0.0 HP
HP35480A

b)    Boot from specified device
s)    Search for bootable devices
a)    Enter Boot Administration mode
x)    Exit and continue boot sequence
?)    Help

Select from menu: b p2

Trying scsi.0.0
Boot path initialized.
Attempting to load IPL.

Failed I/O operation with scsi.0.0
ENTRY_IO status = -10

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00004F04 000000FF FF0009BF 00000000 800100DC 00000000 0025F000 00000400
98080000 00000000 00008C60 00000000 000000FF 00000000 00000000 00000000

Searching for Potential Boot Devices.

Should this work or is this a current limitation ?

Ulrich

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

#1 lore raw

Am Tue, 28 Sep 1999 schrieb Ulrich Strelow:

Quoted 65 lines

I know that this is extremely low priority but...

I have tried to boot the linux kernel from a SCSI DDS tape (copied via dd if=Image of=/dev/rmt/0m bs=512). The same kernel (cvs tree from today) boots sucessfully via rbootd on my 715/33. Here is the console log:

(c) Copyright Hewlett-Packard Company,
1991, 1992
Portions of this code are (c) Copyright Samsung Electronics Co., Ltd, 91, 92

PDC ROM rev. 1.4
IODC ROM rev. 1.2
48 MB of memory have been configured.

Selecting a system to boot.
To stop selection process, press and hold the ESCAPE key.

Selection process stopped.

Searching for Potential Boot Devices.
To terminate search, press and hold the ESCAPE key.

Device Selection Device Path Device
Type
----------------------------------------------------------------------------

P0 scsi.6.0 HP
C3324A
P1 scsi.3.0 HP
C2490AM
P2 scsi.0.0 HP
HP35480A

b)    Boot from specified device
s)    Search for bootable devices
a)    Enter Boot Administration mode
x)    Exit and continue boot sequence
?)    Help

Select from menu: b p2

Trying scsi.0.0
Boot path initialized.
Attempting to load IPL.

Failed I/O operation with scsi.0.0
ENTRY_IO status = -10

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00004F04 000000FF FF0009BF 00000000 800100DC 00000000 0025F000 00000400
98080000 00000000 00008C60 00000000 000000FF 00000000 00000000 00000000

Quoted 3 lines

Searching for Potential Boot Devices.

Should this work or is this a current limitation ?

It should work and it did it already in the past. I think the bootloader is currently not in the best condition since we aren�t able to boot via hpux-bootloader too anymore.
(This is one of the problems which will be adressed in the very near future...)

Helge.

Quoted 11 lines

Ulrich

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

---------------------------------------------------------------------------
To unsubscribe: send e-mail to [email protected] with `unsubscribe' as the subject.

#2 lore raw
In reply to Ulrich Strelow
Quoted 7 lines · Ulrich Strelow

I know that this is extremely low priority but...

I have tried to boot the linux kernel from a SCSI DDS tape (copied via dd if=Image of=/dev/rmt/0m bs=512). The same kernel (cvs tree from today) boots sucessfully via rbootd on my 715/33. Here is the console log:

...

Quoted 9 lines

Select from menu: b p2

Trying scsi.0.0
Boot path initialized.
Attempting to load IPL.

Failed I/O operation with scsi.0.0
ENTRY_IO status = -10

Quoted 8 lines

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00004F04 000000FF FF0009BF 00000000 800100DC 00000000 0025F000 00000400
98080000 00000000 00008C60 00000000 000000FF 00000000 00000000 00000000

I believe this is a problem with either how the tape was created or talking to the tape drive. Does anyone know where to find what the -10 status means?

Another difference when booting from tape (vs disk), is how the tape is "made". One *must* specify 2k block size. It doesn't matter for disk devices. Eg:

dd if=Image of=/dev/rmt/0m bs=2k

I don't know if Image is intentionally padded to a 2k block size. One might check that too.

grant

Grant Grundler
Communications Infrastructure Computer Operations
+1.408.447.7253

#3 lore raw

| > Attempting to load IPL.
| > 
| > Failed I/O operation with scsi.0.0
| > ENTRY_IO status = -10
| > 
| > 00000000 00000000 00000000 00000000 00000000 00000000
| > 00000000 00000000
| > 00000000 00000000 00000000 00000000 00000000 00000000
| > 00000000 00000000
| > 00004F04 000000FF FF0009BF 00000000 800100DC 00000000
| > 0025F000 00000400
| > 98080000 00000000 00008C60 00000000 000000FF 00000000
| > 00000000 00000000
| 
| I believe this is a problem with either how the tape was created
| or talking to the tape drive. Does anyone know where to find what
| the -10 status means?
#4 lore raw
Quoted 37 lines · Kirk Bresniker
| > Attempting to load IPL.
| >
| > Failed I/O operation with scsi.0.0
| > ENTRY_IO status = -10
| >
| > 00000000 00000000 00000000 00000000 00000000 00000000
| > 00000000 00000000
| > 00000000 00000000 00000000 00000000 00000000 00000000
| > 00000000 00000000
| > 00004F04 000000FF FF0009BF 00000000 800100DC 00000000
| > 0025F000 00000400
| > 98080000 00000000 00008C60 00000000 000000FF 00000000
| > 00000000 00000000
|
| I believe this is a problem with either how the tape was created
| or talking to the tape drive. Does anyone know where to find what
| the -10 status means?
Quoted 1 line

From the firmware comments:

/* RETURNS:
/*

/*   3   :  EOF Encountered ( Sequential Device only)
/*   2   :  Recoverable error
/*   1   : Inexact I/O Transfer
/*   0   : OK
/*   -2  : Non Existant Option.
/*   -3  : Cannot complete call without error
/*   -4  : Unrecoverable Hardware Error
/*   -6  : Illegal Device Address
/*   -7  : Non Existant Device
/*   -8  : Module/Device not ready
/*   -10 : Invalid Argument ( Invalid SCSI ID or LUN )
/*   -12 : Unsupported Record Size
/*   -14 : Illegal Device block Size
Quoted 1 line

KMB

And for future reference to save Kirk from having to look at his source code...

The IO ACD is at

http://dtf.external.hp.com/dtf/swdev/pdf/iodc.pdf

The Entry_IO errors are on page 42 of the PDC (document p. 3-40).

-Frank Rowand

#5 lore raw
In reply to Grant Grundler
Quoted 31 lines · Grant Grundler
Quoted 7 lines · Ulrich Strelow

I know that this is extremely low priority but...

I have tried to boot the linux kernel from a SCSI DDS tape (copied via dd if=Image of=/dev/rmt/0m bs=512). The same kernel (cvs tree from today) boots sucessfully via rbootd on my 715/33. Here is the console log:

...

Quoted 9 lines

Select from menu: b p2

Trying scsi.0.0
Boot path initialized.
Attempting to load IPL.

Failed I/O operation with scsi.0.0
ENTRY_IO status = -10

Quoted 8 lines

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00004F04 000000FF FF0009BF 00000000 800100DC 00000000 0025F000 00000400
98080000 00000000 00008C60 00000000 000000FF 00000000 00000000 00000000

I believe this is a problem with either how the tape was created or talking to the tape drive. Does anyone know where to find what the -10 status means?

Quoted 5 lines

Another difference when booting from tape (vs disk), is how the tape is "made". One *must* specify 2k block size. It doesn't matter for disk devices. Eg:

dd if=Image of=/dev/rmt/0m bs=2k

If I remember correctly the utah sources mkboot program has a comment that says the file should be an odd number of 1k blocks. It has a -t option for making tape files.

Tom

Signature · 6 lines
=============================+===========================
Tom Javen                    |   Innotrac Diagnostics Oy
email [email protected]  |   Finland
gsm   +358-40-5860532        |   phone +358-2-2410025
                             |   fax   +358-2-2410024
=============================+===========================