Login or Register to Ask a Question and Join Our Community


Solaris

Setting up bootblock on RAID 0 SVM

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Setting up bootblock on RAID 0 SVM
# 1  
Old 08-16-2010
Setting up bootblock on RAID 0 SVM
Hi All!

I'm running Solaris 10 and SPARC and using

Let me give a bit of background before asking my question:

I have created a RAID 0 (stripe) on 2 disks, I have the OS running on a third disk and I have now performed a ufsdump / ufsrestore from my third disk to the RAID 0 disks (/dev/md/dsk/d10)

From what I understand, ufsrestore does NOT carry over bootblock data and this is fine and dandy on a single drive, but when I try to add the bootblock to the RAID 0 I get the following:

# /usr/sbin/installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/md/dsk/d10
/dev/md/dsk/d10: Not a character device


I know I still need to run metaroot but that is for mounting the disk AFTER I boot the system (is this the correct logic?)

If anyone could point me in the right direction it would be greatly appreciated; I searched the forums and google but I can't seem to find anything for a RAID 0

I noticed with a RAID 1, you are to setup the bootblock BEFORE you setup RAID 1, but how do you setup RAID 0 with a bootblock?

Thanks so much everyone!
# 2  
Old 08-16-2010
you need to install the bootblock on character device which should be
Quote:
/dev/md/rdsk/d10
And you need to run the metaroot before booting the system, and need to place the entry for metadevice for root in /etc/vfstab file and /etc/system
# 3  
Old 08-16-2010
You need to run it on the /dev/md/rdsk/d10 device.
# 4  
Old 08-16-2010
Thanks a bunch!
That was a simple fix Smilie I should've thought to try that ><

I was hoping I could get assistance with the metaroot cmd

When I run metaroot, I get the following error

Code:
# metaroot -n d10
metaroot: Stripe d10 has more than 1 slice

Here is some info on my RAID 0 setup

Here's the partition table of one of the disks
Code:
Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm     413 - 14075       66.30GB    (13663/0/0) 139034688
  1       swap    wu       0 -   412        2.00GB    (413/0/0)     4202688
  2     backup    wm       0 - 14086       68.35GB    (14087/0/0) 143349312
  3 unassigned    wm       0                0         (0/0/0)             0
  4 unassigned    wm       0                0         (0/0/0)             0
  5 unassigned    wm   14076 - 14086       54.66MB    (11/0/0)       111936
  6 unassigned    wm       0                0         (0/0/0)             0
  7 unassigned    wm       0                0         (0/0/0)             0

# metastat
d10: Concat/Stripe
    Size: 278069376 blocks (132 GB)
    Stripe 0: (interlace: 32 blocks)
        Device     Start Block  Dbase   Reloc
        c0t0d0s0          0     No      Yes
        c0t2d0s0          0     No      Yes

Device Relocation Information:
Device   Reloc  Device ID
c0t0d0   Yes    id1,sd@SFUJITSU_MAW3073NCSUN72G_000633B0G4UE____DAN0P680G4UE
c0t2d0   Yes    id1,sd@SFUJITSU_MAW3073NCSUN72G_000626B0F330____DAN0P660F330

# prtvtoc /dev/md/dsk/d10
* /dev/md/dsk/d10 partition map
*
* Dimensions:
*     512 bytes/sector
*     424 sectors/track
*      24 tracks/cylinder
*   10176 sectors/cylinder
*   27327 cylinders
*   27327 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector
*           0     10176     10175
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      0    00      10176 278069376 278079551

Any ideas?
Last edited by Scott; 08-16-2010 at 05:32 PM.. Reason: Code tags, please...
# 5  
Old 08-16-2010
You cannot boot from a software implemented Raid 0, because the bootblock has to be read before the operating system and all md-drivers are loaded. metaroot's error message says it all:

Code:
Stripe d10 has more than 1 slice

# 6  
Old 08-16-2010
Thanks hergp

I found this URL on sun docs for anyone out there having the same issue

2. Metadevices (Solstice DiskSuite 4.2.1 Reference Guide) - Sun Microsystems

There are three kinds of simple metadevices: concatenated metadevices, striped metadevices, and concatenated striped metadevices

You can use a simple metadevice containing multiple slices for any file system except the following:
  • Root (/)
  • /usr
  • swap
  • /var
  • /opt
  • Any file system accessed during an operating system upgrade or installation

hergp can you help me understand why a RAID 1 works as opposed to a RAID 0?

---------- Post updated at 04:06 PM ---------- Previous update was at 03:27 PM ----------

Can anyone provide any insight?

I understand that you cannot use metaroot to edit the /etc/system and /etc/vfstab if your stripe spans more than 1 slice

but doesn't a 2-way or 3-way RAID 1 setup span more than 1 slice?

I only have enough drives to test a 1-way RAID 1 which works

---------- Post updated at 04:30 PM ---------- Previous update was at 04:06 PM ----------

I've done some more reading and I gave some more thought to how metaroot works in a RAID 1 setup (mirror)

When setting up a mirror, you setup metaroot on a single slice BEFORE attaching the first submirror

When setting up a striped metadevice (RAID 0), you HAVE to setup the metadevice across at least 2 slices which then prevents metaroot from working (as it will only work on a single slice)

Does this theory make sense?
# 7  
Old 08-17-2010
Keepcase,

in a raid 1 (no matter how many disks you have in it), every subdisk (diskslice) is identical to the others and to the raidset itself. Therefore every subdisk in a raid 1 has the full information of the filesystem built on top of the raidset. As long as you do not update the filesystem (mount it read/write), you can use a subdisk instead of the raidset without messing things up.

What happens when the system boots (from a ufs root filesystem) is this:
The OBP reads the bootblock from one of the disks (the details are configured in the OBP), then the bootblock loads a secondary bootloader called ufsboot, which loads the kernel and essential drivers. Later, when the kernel has enough information to understand mirrored disks, it switches from using the subdisk to the mirrored logical volume for the root filesystem.

When the root filesystem is scattered over more than one disk, all this is not possible (at least as long as OBP has no builtin means to understand logical volumes).

I hope, this helps to shed some light on the boot process with logical volumes.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

RAID Configuration for IBM Serveraid-7k SCSI RAID Controller

Hello, I want to delete a RAID configuration an old server has. Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton? I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies

2. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies

3. AIX

SCSI PCI - X RAID Controller card RAID 5 AIX Disks disappeared

Hello, I have a scsi pci x raid controller card on which I had created a disk array of 3 disks when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk ) suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies

4. Linux

Help Setting up Linux Raid Server

I just built a home computer with 3TB hard drives I wanted to set up in a RAID 5 and load Ubuntu server onto it. The first thing I did was set up the drives in a RAID 5 using just the motherboard chipset software to do it, so a 'hardware' RAID basically. I installed Windows first to see if... (2 Replies)
Discussion started by: lorewap3
2 Replies

5. Solaris

Installing Solaris 8 bootblock without Solaris Install CD

Hello everyone, Background: I'm having an issue with booting a clone of hard drive with Solaris 8 installation. For cloning process I have used g4l, running under click'n'clone option. As far as I know the actual operation ran behind g4l's interface was dd, though I do not have any information... (12 Replies)
Discussion started by: johnny994
12 Replies

6. Solaris

What is mirror and sub mirror in RAID -1 SVM

Hi , I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through metainit d51 1 1 c0t0d0s2 metainit d52 1 1 c1t0d0s2 In the next step metainit d50 -m d51 d50: Mirror is setup next step is metaattach d50 d52 d50 : submirror d52 is... (7 Replies)
Discussion started by: vr_mari
7 Replies

7. Solaris

How can i grow Raid 5 volume in SVM..?

Hello experts.. How can i grow Raid 5 volume in SVM? Thanks in advance.. (2 Replies)
Discussion started by: younus_syed
2 Replies

8. Solaris

RAID controller needed for SVM?

hi this may be a very stupid question, but im quite new to Solaris (gonna buid my first system, Solaris 10 on x86 system, connected to other windows systems in a home network) i wanna put a RAID 5 system in there to back up my other systems at home; iv read that its really so easy with SVM to... (4 Replies)
Discussion started by: Landser
4 Replies

9. Solaris

How do you remove a RAID 5 under SVM?

I have this setup, i can only find docs to unmirror a raid 1 set, how do you get rid of a raid 5 set? the same way? metadetach and metaclear? d8: RAID State: Okay Interlace: 32 blocks Size: 142245693 blocks (67 GB) Original device: Size: 142247872 blocks (67 GB) ... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
Login or Register to Ask a Question