05-15-2008
I was thinking of using mkboot and lifcp...
But I got a better idea...
Try to get your DDS on the other WS and try to make an ignite tape with make_recovery command, you can then boot from that tape on your bad WS...
But unfortunately without support CD to see the state of your disk, I dont know to what point this makes sence... perhaps its worth the try...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Could somone please tell me what happened when I reboot my computer, it take too long to pass the part it said "starting sendmail"
I only changed the server name and when I reboot the server, all of the services are running except when it got to :
starting sendmail
it take toooo long to... (1 Reply)
Discussion started by: lapnguyen
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
1st HDD is loaded with Windows 2000 Professional and I have installed Red Hat ES 3.0 on second HDD(80GB). After linux installation failed to load windows and boot stucks with displaying only L How to fix this issue
Thanks in advance for your valuable answer.
Regards,
Bachegowda (1 Reply)
Discussion started by: bache_gowda
1 Replies
3. HP-UX
Hi,all:
I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed !
It says : Client MAC Address: 00 18 FE 28 91 82 .....-
PXE-E16: Valid PXE offer not received.
Load of Core LAN Gb A failed: Not Found
I use the nettl command to trace the UDP... (0 Replies)
Discussion started by: bluepluto
0 Replies
4. Solaris
I had logged into Server via ALOM and was placed into runlevel 5 other than 3 which is default.
I did a svcadm delete boot-archive, and was promptly placed in runlevel 3.
Now, I am unable to do a telnet or login into the server through any other service.
bash-3.00# svcs -a
svcs -a
STATE ... (3 Replies)
Discussion started by: praveenr
3 Replies
5. Solaris
Machine: x86
OS : Dualboot Solaris and RHEL5 -Solaris 10 in first fdisk partition.
RHEL5 - /boot in partition2
/ in partition3
swap in 1st... (1 Reply)
Discussion started by: saagar
1 Replies
6. Red Hat
Hi,
I have a laptop with two os running in it, Windows XP & RHEL5. Accidentally, we have deleted the windows entry in grub.conf file. Later we connected the hard disk of laptop to another system & deleted the linux partitions from the disk management tool of windows.
Now the issue is, the... (7 Replies)
Discussion started by: Amol21
7 Replies
7. Solaris
Hi all
i have an issue
when i change auto-boot?=false and reboot it
again it is going to auto-boot?=true
can any one tell that
what should i do for auto-boot?=false for permanently
thank you in advance (11 Replies)
Discussion started by: wkbn86
11 Replies
8. Solaris
Hi all,
please i need your help urgently
I am faced to a serious boot disks issue on an Sun Fire E2900.
The system run with two disque in zpool .
The operating system is Solaris 10 (ZFS)
The first time the issue occured, i got the error below on the two disks:
Apr 7 08:04:33... (0 Replies)
Discussion started by: saki_jumeau
0 Replies
9. Solaris
In the server room at my new job, there is a V100 with a problem. When power is turned on, the machine goes to the lom prompt. Entering poweron yields an endless supply of this message with no way to break out of it.
**********************************************
PSTATE=0000000000000015... (3 Replies)
Discussion started by: chilinski
3 Replies
10. SCO
Hi,
I am using SCO OpenServer 5
During boot I get this message:
PANIC: HTFS: Bad directory ino 2 (offset 0) on HTFS dev hd (1/42)
Cannot dump 8095 pages to dumpdev hd (1/41): Space for only 0 pages
Dump not completed
How can I fix this? I have no boot/root floppy.
If it is a "disk... (8 Replies)
Discussion started by: nubian_sundance
8 Replies
MT(1) General Commands Manual MT(1)
NAME
mt - magnetic tape control
SYNOPSIS
mt [-f device] [count]
DESCRIPTION
Mt is a user interface to the magnetic tape commands described in mtio(4). It allows one to space a tape forwards or backwards, write end
of file markers, etc.
With the -f option a tape device can be named, otherwise the environment variable TAPE is used if set, otherwise the default device
/dev/nrst4 is assumed. Standard input is used if the tape name is a dash (-). The count argument is used to tell how many blocks or files
to space or how many file markers to write. It may be a C-style decimal, octal or hexadecimal constant, by default "1".
Command is the action to perform, it may be one of the following, or any unambiguous prefix (like st for status):
eof, weof Write count end-of-file markers.
fsf Forward space count file markers.
fsr Forward space count records. (The size of a record depends on the tape, and may even be variable, depending on the size of
the writes.)
bsf Backwards space count files. The count may be zero to backspace to the start of the current file. (A tape device need not
support backwards movement, or may be very slow doing it. Rewinding and forward spacing may be better.)
bsr Backwards space count records. The tape is positioned after the last block of the previous file if you hit a filemark when
spacing backwards. The block count is set to -1 to indicate that the driver has no idea where it is on the previous file.
eom Forward space to the end of media.
rewind Rewind the tape.
offline, rewoffl
Rewind and take offline. This may cause some drives to eject the tape.
status Shows the status of the drive, the sense key of the last SCSI error, current file number, current record number, residual
count if the last command that encountered end-of-file, and the current block size.
retension Removes tape tension by winding and rewinding the tape completely.
erase Erases the tape completely and rewinds it.
density Sets the density code to read or write the tape to count. Density codes supported depend on the drive. This command need
not be used if the drive senses the proper density on read and can only write one density.
blksize, blocksize
Sets the block size used to read or write the tape to count. This command may be used to select a fixed block size for a
variable block size tape. This will speed up I/O for small block sizes. Use a zero count to use variable sized blocks
again.
ENVIRONMENT
TAPE Tape drive to use if set.
FILES
/dev/nrst4 Default tape device.
SEE ALSO
mtio(4), st(4).
AUTHOR
Kees J. Bot (kjb@cs.vu.nl)
MT(1)