Prev: Adaptec SAS controller and HP LTO-4 1760
Next: Hardware or software problem?
From: ChrisS on 21 Jan 2010 12:30
BugID: 6901327

I just ran into this problem on my T5220 server. Thought I'd post it
here in case someone looks here first.

Creation of a hardware raid via raidctl with s10u8 fails to create a
valid VTOC. Therefore is not possible to create a disk label on the
newly created volume.

http://bugs.opensolaris.org/bugdatabase/view_bug.do;jsessionid=4e171df1f1d726d644c43cbba5f9?bug_id=6901327

Work around:
Two options. Option 2 will take less time(but is it supported).
1) Format the volume while booted to the s10u8 miniroot. Formatting
will take several hours depending on the volume size and the number of
verification passes(two is the default). To shorten the format process
the format->analyze-setup can be adjusted to a single pass.
2) Create the raid volume from a miniroot prior to s10u8. Then boot
from s10u8 to install Solaris.

From: ChrisS on 21 Jan 2010 12:42
Maybe it's in the format command?!

I noticed when running format with s10u7 it properly set partition
(slice)'s 0 and 1. Where as on the s10u8 format it left them zero'd
out. Though I suppose if the raidctl command "yacked" up the RAID,
then format would fail too. That's pretty deep stuff though.

Anyways, Solaris 10 update 7 did the trick. It properly formated the
RAID 1 on the T5220 server.

 | 
Pages: 1
Prev: Adaptec SAS controller and HP LTO-4 1760
Next: Hardware or software problem?