Sponsored Content
Full Discussion: big disk solaris 2.6
Operating Systems Solaris big disk solaris 2.6 Post 302210145 by incredible on Monday 30th of June 2008 07:14:54 AM
Old 06-30-2008
solution is to boot the disk using another server using a Solaris 9 cd/dvd to single user mode. check the disk size from format utility and partition the 60G as required. label the disk and re-verify. bring the disk over to ur ultra 10 workstation and boot up to single user first. disk size will be shown correctly.
 

8 More Discussions You Might Find Interesting

1. Solaris

Big UH-OH "Bad magic number in disk label"

I tried rebooting my Sun server just a few minutes ago and I got the following at boot: -- Sun Fire 280R (UltraSPARC-III+) , No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx Ethernet address... (6 Replies)
Discussion started by: deckard
6 Replies

2. Solaris

LaCie Big Disk configuration on SUN 280R

hi , i am trying to configure LaCie Big Disk on solaris 9 running on a 280R server . i am trying to use the USB prot to connect to the external disk . please i need help on this as i have no clue on how and from where to start . thanks for ur help . cheers (0 Replies)
Discussion started by: ppass
0 Replies

3. Solaris

Disk Mirror in Solaris 9 via Solaris Volume Manager

Hello, I am trying to do mirror in solaris 9. I have total 0-7 disks 4 5 6 7 0 1 2 3 Drive 0 and Drive 4 = Boot Drives Need to Mirror following drives. Drive 1 and Drive 5 = Need to mirror Drive 1 was mounted on: /prod1, /prod2, /prod3, /prod4, /prod5. Then i... (3 Replies)
Discussion started by: deal732
3 Replies

4. UNIX for Dummies Questions & Answers

How to trace the big files causing high disk usage

Hi All, One very urgent issue and I need your help. I have two V490 servers installed with Sun Solaris 10. I have traced out that the disk usage is running out of space for both the servers. Currently the /dev/md/dsk/d10 device is 91% in one server and another is 56% and it is increasing... (1 Reply)
Discussion started by: ailnilanjan
1 Replies

5. UNIX for Dummies Questions & Answers

How big is too big a config.log file?

I have a 5000 line config.log file with several "maybe" errors. Any reccomendations on finding solvable problems? (2 Replies)
Discussion started by: NeedLotsofHelp
2 Replies

6. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

7. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% / ... (0 Replies)
Discussion started by: fretagi
0 Replies

8. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Discussion started by: fretagi
4 Replies
installboot(1M) 														   installboot(1M)

NAME
installboot - install bootblocks in a disk partition SYNOPSIS
installboot bootblk raw-disk-device The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition. The ufs boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be found using the -i option of uname(1). The installboot utility is a SPARC only program. It is not supported on the architecture. users should use installgrub(1M) instead. bootblk The name of the bootblock code. raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is read- able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive. Example 1: Installing UFS Boot Block To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use: example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s0 /usr/platform/platform-name/lib/fs/ufs directory where ufs boot objects reside. /platform/platform-name/ufsboot second level program to boot from a disk or CD See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5) WARNINGS
The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device. 11 Apr 2005 installboot(1M)
All times are GMT -4. The time now is 05:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy