LinuxQuestions.org - Issues with DIsk

- Solaris / OpenSolaris (https://www.linuxquestions.org/questions/solaris-opensolaris-20/)

- - Issues with DIsk (https://www.linuxquestions.org/questions/solaris-opensolaris-20/issues-with-disk-681165/)

Issues with DIsk

I've got a T5220 and I'm having issues with the disk, I've inherited this issue so I'm not exactly clear on the entire series of events. I believe the server was jumpstarted then they found an issue and SUN replaced the main board. Anyway when attempting a jumpstart it hangs, if I boot off of the cdrom I can see the following:
# raidctl -l
RAID Volume RAID RAID Disk
Volume Type Status Disk Status
------------------------------------------------------
c1t130d0 IM OK c1t1d0 OK
c1t0d0 OK
# format
Searching for disks...done
No disks found!

Not sure why raidctl is showing disks and format isn't, The disks were at a MISSING state earlier and I did a boot cdrom -s -r and a raidctl -l (for some reason just raidctl wasn't seeing it) to get them back to an OK state. I've tried various raidctl -d commands but I must not have syntax right or something.
I get the following:
# raidctl -d c1t130d0
Not a volume 'c1t130d0'
#

I even physically removed the drive and re-inserted it and see a message about the disk being removed.

I'm thinking I either have an issue between the raid configuration and the new mainboard or a hardware issue still. I believe the volume is usually c0t0d0 instead of c1t130d0 so that's another strange piece.

I guess my question is how do I get format to see my disks? Or how do I clear the raidctl configuration (hoping this allows me to see disk)?

Thanks

In case anyone wonders, I downloaded the new 10/08 Solaris disk and booted off it into single user mode. I was then able to run raidctl -d c1t130d0 and delete the volume. Rebooted just for fun and then when I ran format I saw both disks. I was then able to mirror them and have them visible in format.

Still having some wierdness when I attempt to jumpstart the server. I'm thinking there has been a change like a newer revision of the T5220 main board or something. I believe the jumpstart server is using a version that is about 6 months or so old (should support the T5220 according to sunsolve and I have other T5220s that were jumpstarted).
I get the following messages when I am attempting to run 'boot net - install'

Code:

clntbtcp_call: xdr encode args failed

clntbtcp_call:xdr encode args failed

clntbtcp_call: xdr encode args filed

clntbtcp_call: xdr encode args failed

clntbtcp_cal: xdr encode args failed

clntbtcp_call: xdr encode arg failed

clntbtcp_call: xdr encode args failed

clntbtcpcall: xdr encode args failed

clntbtcp_call: xdr encode rgs failed

clntbtcp_call: xdr encode args failed

clntbtcp_call: xdr encode args failed

I was messing around and had the 10/08 DVD in and did a boot cdrom - install and it looks like it pulled the info (disk layout, finish scripts, etc) from the jumpstart server but is using the media from the DVD for install. (Didn't know you could do this) I originally thought it would just send me through the normal solaris install. Then I could flash the firmware or do whatever I needed with an OS.

Anyway if anyone has any ideas what the lntbtcp_call: xdr encode arg failed means maybe they can enlighten me.

Thanks