Removing a disk from SUN Fire V440 running Solaris 8


Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
Operating Systems Solaris Removing a disk from SUN Fire V440 running Solaris 8
# 1  
Wrench Removing a disk from SUN Fire V440 running Solaris 8

Hi,

I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.

Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an identical new disk?

Thanks a lot.
# 2  
Yes that is safe, unless it is the boot disk.
And then there is manual work:
eventually a label is to be installed, the new disk needs to be partitioned, eventually a boot block needs to be installed, a metadb needs to be installed, and each partition needs to be synced.
Please give output of metastat and metadb!
This User Gave Thanks to MadeInGermany For This Post:
# 3  
First of all make sure that you have backed up the data for the disk you are replacing. Then replace the disk. Partition it. Create the metadb. Mirror it. Resync it. Fill the disk with earlier data. Also make the entries in /etc/vfstab.
This User Gave Thanks to RAHUL RATHORE For This Post:
# 4  
Quote:
Originally Posted by MadeInGermany
Yes that is safe, unless it is the boot disk.
And then there is manual work:
eventually a label is to be installed, the new disk needs to be partitioned, eventually a boot block needs to be installed, a metadb needs to be installed, and each partition needs to be synced.
Please give output of metastat and metadb!
Hi, this is not the boot disk, so I guess there is no need for boot block.
Thanks for the information you provided.

---------- Post updated at 08:55 PM ---------- Previous update was at 08:51 PM ----------

Quote:
Originally Posted by RAHUL RATHORE
First of all make sure that you have backed up the data for the disk you are replacing. Then replace the disk. Partition it. Create the metadb. Mirror it. Resync it. Fill the disk with earlier data. Also make the entries in /etc/vfstab.
Hi, this disk does not appear in the "format" command output and it was a member of a mirror. So the backup is not possible and not necessary I think.

Thanks for the information.
# 5  
Quote:
Originally Posted by MadeInGermany
Yes that is safe, unless it is the boot disk.
And then there is manual work:
eventually a label is to be installed, the new disk needs to be partitioned, eventually a boot block needs to be installed, a metadb needs to be installed, and each partition needs to be synced.
Please give output of metastat and metadb!
Hi, attached is the output of metastat and metadb commands.
# 6  
If the broken disk is hot-swappable, you can pull it online.
But shut down critical services (e.g. a database).

Insert the new disk. Wait a minute for detection and spin-up.

Run format, in order to verify that the disk can be accessed.
Eventually write a label to it (any suggested label works).
Copy the partition table from the other disk,
either in format or with the command
Code:
prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t2d0s2

They must look identical:
Code:
prtvtoc -h /dev/rdsk/c1t0d0s2
prtvtoc -h /dev/rdsk/c1t2d0s2

Create new copies of the state database:
Code:
metadb
metadb -d c1t2d0s7
metadb
metadb -a -c 3 c1t2d0s7
metadb

Sync the first partition; metastat suggests a command that must be slightly modified:
Code:
metastat d0
metareplace -e d0 c1t2d0s0

Check the progress
Code:
metastat d0

Wait until d0 is 100% = Okay.

Repeat with the other partitions.

Last edited by MadeInGermany; 09-04-2014 at 07:22 PM..
This User Gave Thanks to MadeInGermany For This Post:
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #658
Difficulty: Medium
The FreeDOS project began on 26 June 1994, when Microsoft announced it would no longer sell or support MS-DOS.
True or False?

10 More Discussions You Might Find Interesting

1. Solaris

Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)

Hi, I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error: WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1): SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies

2. Solaris

Sun-Fire V440 boot disk issue

Hi, I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken. Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies

3. Solaris

Sun Fire v440 Over heat Problem.

Dear Team, I need some expert advice to my problem. We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies

4. Solaris

Firmware password Solaris Sun Fire v440

Hi: I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies

5. Solaris

ALOM wont work when KVM connected to Sun Fire V440 server

Hi, I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection. ... (0 Replies)
Discussion started by: jimmy54321
0 Replies

6. Solaris

error messages in Sun Fire V440

Hello, I am seeing error messages in V440 (OS = solaris 8). I have copied here : The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day.. I... (5 Replies)
Discussion started by: upengan78
5 Replies

7. Solaris

Sun Fire v440 hardware problem (can't get ok>)

First of all it's shut down 60 second after power on and write on console : SC Alert: Correct SCC not replaced - shutting managed system down! This is cured by moving out battery from ALOM card. Now server start to loop during the testing. That's on the console: >@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies

8. Solaris

Sun Fire v440 keeps shutting down

Hello, I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies

9. Solaris

Weird behavior on a Sun Fire V120 running solaris 10.

All, After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex... (2 Replies)
Discussion started by: jsandova
2 Replies

10. Solaris

Sun Fire V440 and Patch 109147-39

Got an curious issue. I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on. The patch modified mainly the linker libraries and commands. ... (2 Replies)
Discussion started by: BOFH
2 Replies

Featured Tech Videos