01-12-2010
At the boot prompt enter the following:
boot: hd(41)unix
You can boot SCO off either drive with this option. Most Linux come with a bootloader program so that you can select which drive/partition to boot from; so it will likely take over if you install Linux on one of the drives.
You can also boot a dos/windows(98) partition by entering "dos" at the boot prompt, or NT/2000/XP by entering "os2" at the prompt.
This User Gave Thanks to jgt For This Post:
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hey !
I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range.
According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies
2. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
3. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
4. Solaris
Help needed please! I see the following scsi errors during boot up. The server eventually boots up successfully. Please let me now how to fix these errors:
Executing last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_117350-62 64-bit
Copyright 1983-2003 Sun... (4 Replies)
Discussion started by: pingmeback
4 Replies
5. SCO
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies
6. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
7. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
8. Hardware
I have a server with a scsi raid controller (for hard drives) and a scsi controller (for tape drive and cd-rom). I am trying to boot from the cd-rom but can't. During boot up, bootable media is detected in the cd-rom but the system will not boot from it. BIOS for the raid controller installs but... (1 Reply)
Discussion started by: powwm
1 Replies
9. Solaris
Hi Solaris 10 Experts,
I am wondering what is the correct syntax to edit in Grub when trying to specify the local ZFS boot disk while booting up from a Solaris 10 x86 64bits DVD installation disk. In other word, I try to boot up from local disk without removing the Solaris installation disk... (0 Replies)
Discussion started by: gjackson123
0 Replies
LEARN ABOUT DEBIAN
tapeinfo
TAPEINFO(1) General Commands Manual TAPEINFO(1)
NAME
tapeinfo - report SCSI tape device info
SYNOPSIS
tapeinfo -f <scsi-generic-device>
DESCRIPTION
The tapeinfo command reads various information from SCSI tape drives that is not generally available via most vendors' tape drivers. It
issues raw commands directly to the tape drive, using either the operating system's SCSI generic device ( e.g. /dev/sg0 on Linux,
/dev/pass0 on FreeBSD) or the raw SCSI I/O ioctl on a tape device on some operating systems.
One good time to use 'tapeinfo' is immediately after a tape i/o operation has failed. On tape drives that support HP's 'tapealert' API,
'tapeinfo' will report a more exact description of what went wrong.
Do be aware that 'tapeinfo' is not a substitute for your operating system's own 'mt' or similar tape driver control program. It is intended
to supplement, not replace, programs like 'mt' that access your operating system's tape driver in order to report or set information.
OPTIONS
The first argument, given following -f , is the SCSI generic device corresponding to your tape drive. Consult your operating system's doc-
umentation for more information (for example, under Linux these are generally start at /dev/sg0 under FreeBSD these start at /dev/pass0).
Under FreeBSD, 'camcontrol devlist' will tell you what SCSI devices you have, along with which 'pass' device controls them. Under Linux,
"cat /proc/scsi/scsi" will tell you what SCSI devices you have.
BUGS AND LIMITATIONS
This program has only been tested on Linux with a limited number of tape drives (HP DDS4, Seagate AIT).
AVAILABILITY
tapeinfo is currently being maintained by Robert Nelson <robertnelson@users.sourceforge.net> as part of the 'mtx' suite of programs. The
'mtx' home page is http://mtx.sourceforge.net and the actual code is currently available there and via SVN from http://source-
forge.net/projects/mtx.
SEE ALSO
mt(1),mtx(1),scsitape(1),scsieject(1),loaderinfo(1)
TAPEINFO1.0 TAPEINFO(1)