Sponsored Content
Full Discussion: Solved: Disk Unable to Boot
Operating Systems Solaris Solved: Disk Unable to Boot Post 302869121 by DukeNuke2 on Tuesday 29th of October 2013 04:22:23 PM
Old 10-29-2013
Quote:
Originally Posted by br1an
I did not know that was a tape drive command.
it's always bad to just use commands and not know what they are doing...
 

9 More Discussions You Might Find Interesting

1. Solaris

unable to boot from disk1

I had installed solaris 10 on 440 on disk 0. I had done ufsrestore on disk1 from tape and then rebooted Rebooting with command: boot disk1 Boot device: /pci@1f,700000/scsi@2/disk@1,0 File and args: SunOS Release 5.10 Version Generic_118833-24 64-bit Copyright 1983-2006 Sun Microsystems,... (3 Replies)
Discussion started by: vr76413
3 Replies

2. Solaris

vxvm root disk booting problem - solved with boot -a. How?

Hi All, We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear: WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies

3. Red Hat

Unable to boot Fedora 10

Hello, I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning. But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies

4. Hardware

[Solved] Boot Lockup After Drive Swap

Hey All, Im using Fedora 2.6 (which is cannot be changed for compatibility reasons). I cloned a drive from a different server and when i added this drive to a new box, during startup it hangs on "Configuring Kernel Parameters:" Is there any way to bypass this process and still boot... (0 Replies)
Discussion started by: robfwauk
0 Replies

5. Fedora

[Solved] Unable to start Matlab program

hello everyone, I have Matlab installed on Fedora 16. I tried running it by simply typing on terminal: $ matlabBut it returned the follwoing error: --- can anyone suggest a solution? cheers, peter ---------- Post updated at 10:57 PM ---------- Previous update was at 10:54 PM ----------... (1 Reply)
Discussion started by: peter_071
1 Replies

6. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

Hi, Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot. vxplex -g rootdg dis var-02 vxplex -g rootdg dis swapvol-02 vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies

7. Solaris

How to specify local boot up disk in CD boot Grub?

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

8. Solaris

Use 'dd' to copy boot disk to larger target disk

Hi, I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ... (2 Replies)
Discussion started by: sparcman
2 Replies

9. Red Hat

Unable to boot up after P2V

Hi, I just P2V an old machine running Redhat 5.5 on a physical server. After P2V was completed, when boot up it got an error. Please refer to the attachment for the error. Please assist. Thanks. (2 Replies)
Discussion started by: freshmeat
2 Replies
mt(1)								   User Commands							     mt(1)

NAME
mt - magnetic tape control SYNOPSIS
mt [-f tapename] command... [count] DESCRIPTION
The mt utility sends commands to a magnetic tape drive. If -f tapename is not specified, the environment variable TAPE is used. If TAPE does not exist, mt uses the device /dev/rmt/0n. OPTIONS
The following option is supported: -f tapename Specifies the raw tape device. OPERANDS
The following operands are supported: count The number of times that the requested operation is to be performed. By default, mt performs command once. Multiple opera- tions of command may be performed by specifying count. command Available commands that can be sent to a magnetic tape drive. Only as many characters as are required to uniquely identify a command need be specified. eof Writes count EOF marks at the current position on the tape. weof fsf Forward spaces over count EOF marks. The tape is positioned on the first block of the file. fsr Forward spaces count records. bsf Back spaces over count EOF marks. The tape is positioned on the beginning-of-tape side of the EOF mark. bsr Back spaces count records. nbsf Back spaces count files. The tape is positioned on the first block of the file. This is equivalent to count+1 bsf's followed by one fsf. asf Specifies absolute space to count file number. This is equivalent to a rewind followed by a fsf count. If count is specified with any of the following commands, the count is ignored and the command is performed only once. eom Spaces to the end of recorded media on the tape. This is useful for appending files onto previously written tapes. rewind Rewinds the tape. offline Rewinds the tape and, if appropriate, takes the drive unit off-line by unloading the tape. rewoffl status Prints status information about the tape unit. retension Rewinds the cartridge tape completely, then winds it forward to the end of the reel and back to beginning- of-tape to smooth out tape tension. reserve Allows the tape drive to remain reserved after closing the device. The drive must then be explicitly released. release Re-establishes the default behavior of releasing at close. forcereserve Breaks the reservation of the tape drive held by another host and then reserves the tape drive. This com- mand can be executed only with super-user privileges. erase Erases the entire tape. Caution: Some tape drives have option settings where only portions of the tape may be erased. Be sure to select the correct setting to erase the whole tape. Erasing a tape may take a long time depending on the device and/or tape. Refer to the device specific manual for time details. config Reads the drives current configuration from the driver and displays it in st.conf format. See st(7D) for definition of fields and there meanings. EXIT STATUS
0 All operations were successful. 1 Command was unrecognized or mt was unable to open the specified tape drive. 2 An operation failed. FILES
/dev/rmt/* magnetic tape interface ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
tar(1), tcopy(1), ar.h(3HEAD), environ(4), attributes(5), mtio( 7I), st(7D) BUGS
Not all devices support all options. Some options are hardware-dependent. Refer to the corresponding device manual page. mt is architecture sensitive. Heterogeneous operation (that is, SPARC to x86 or the reverse) is not supported. SunOS 5.10 1 Sep 2004 mt(1)
All times are GMT -4. The time now is 08:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy