Sponsored Content
Full Discussion: Solved: Disk Unable to Boot
Operating Systems Solaris Solved: Disk Unable to Boot Post 302869071 by br1an on Tuesday 29th of October 2013 03:08:04 PM
Old 10-29-2013
I was actually trying to unencapsulate the disk from Vertias volume manager.
I was following this guide lines here
http://www.symantec.com/business/sup...&id=TECH157465
When I encountered an error here
Code:
# mt -f /dev/rmt/on stat
/dev/rmt/on: No such file or directory

but I proceded in removing the entries in /etc/system and vfstab.

Code:
# cat release
                      Solaris 9 9/05 HW s9s_u9wos_06b SPARC
           Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                           Assembled 25 September 2006

# prtvtoc  /dev/dsk/c1t0d0s0
* /dev/dsk/c1t0d0s0 partition map
*
* Dimensions:
*     512 bytes/sector
*     424 sectors/track
*      24 tracks/cylinder
*   10176 sectors/cylinder
*   14089 cylinders
*   14087 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector
*   143349312 18446744073566202304 18446744073709551615
*    73277376 18446744073689067328  52793087
*    93761664  49567296 143328959
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      2    00   32776896  20016192  52793087
       1      3    01          0  32776896  32776895
       2      5    00          0 143349312 143349311
       3      4    00   52793088  20484288  73277375
       4     15    01  143328960     20352 143349311
       5      0    00   73277376  20484288  93761663
       6      0    00   52793088  20484288  73277375
       7     14    01          0 143349312 143349311

# prtvtoc /dev/dsk/c1t1d0s0
* /dev/dsk/c1t1d0s0 partition map
*
* Dimensions:
*     512 bytes/sector
*     424 sectors/track
*      24 tracks/cylinder
*   10176 sectors/cylinder
*   14089 cylinders
*   14087 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector
*    32797248 18446744073676774720     20351
*   143349312 18446744073598999552  32797247
*    93782016  49567296 143349311
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      2    00   32797248  20016192  52813439
       1      3    01      20352  32776896  32797247
       2      5    01          0 143349312 143349311
       4     15    01          0     20352     20351
       5      0    00   73297728  20484288  93782015
       6      0    00   52813440  20484288  73297727
       7     14    01      20352 143328960 143349311

 

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
prtvtoc(1M)                                               System Administration Commands                                               prtvtoc(1M)

NAME
prtvtoc - report information about a disk geometry and partitioning SYNOPSIS
prtvtoc [-fhs] [-t vfstab] [-m mnttab] device DESCRIPTION
The prtvtoc command allows the contents of the label to be viewed. The command can be used only by the super-user. The device name can be the file name of a raw device in the form of /dev/rdsk/c?t?d?s2 or can be the file name of a block device in the form of /dev/dsk/c?t?d?s2. OPTIONS
The following options are supported: -f Report on the disk free space, including the starting block address of the free space, number of blocks, and unused parti- tions. -h Omit the headers from the normal output. -m mnttab Use mnttab as the list of mounted filesystems, in place of /etc/mnttab. -s Omit all headers but the column header from the normal output. -t vfstab Use vfstab as the list of filesystem defaults, in place of /etc/vfstab. EXAMPLES
Example 1: Using the prtvtoc Command The following example uses the prtvtoc command on a 424-megabyte hard disk: example# prtvtoc /dev/rdsk/c0t3d0s2 * /dev/rdsk/c0t3d0s2 partition map * * Dimension: * 512 bytes/sector * 80 sectors/track * 9 tracks/cylinder * 720 sectors/cylinder * 2500 cylinders * 1151 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 0 76320 76319 / 1 3 01 76320 132480 208799 2 5 00 0 828720 828719 5 6 00 208800 131760 340559 /opt 6 4 00 340560 447120 787679 /usr 7 8 00 787680 41040 828719 /export/home example# The data in the Tag column above indicates the type of partition, as follows: Name Number UNASSIGNED 0x00 BOOT 0x01 ROOT 0x02 SWAP 0x03 USR 0x04 BACKUP 0x05 STAND 0x06 VAR 0x07 HOME 0x08 ALTSCTR 0x09 CACHE 0x0a RESERVED 0x0b The data in the Flags column above indicates how the partition is to be mounted, as follows: Name Number MOUNTABLE, READ AND WRITE 0x00 NOT MOUNTABLE 0x01 MOUNTABLE, READ ONLY 0x10 Example 2: Using the prtvtoc Command with the -f Option The following example uses the prtvtoc command with the -f option on a 424-megabyte hard disk: example# prtvtoc -f /dev/rdsk/c0t3d0s2 FREE_START=0 FREE_SIZE=0 FREE_COUNT=0 FREE_PART=34 Example 3: Using the prtvtoc Command on a Disk Over One Terabyte The following example uses uses the prtvtoc command on a disk over one terabyte:. example# prtvtoc /dev/rdsk/c1t1d0s2 * /dev/rdsk/c1t1d0s2 partition map * * Dimensions: * 512 bytes/sector * 3187630080 sectors * 3187630013 accessible sectors * * Flags: * 1: unmountable * 10: read-only * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 34 262144 262177 1 3 01 262178 262144 524321 6 4 00 524322 3187089340 3187613661 8 11 00 3187613662 16384 318763004 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
devinfo(1M), fmthard(1M), format(1M), mount(1M), attributes(5) WARNINGS
The mount command does not check the "not mountable" bit. SunOS 5.10 25 Jul 2002 prtvtoc(1M)
All times are GMT -4. The time now is 06:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy