Sponsored Content
Full Discussion: Liveupgrade with RAID
Operating Systems Solaris Liveupgrade with RAID Post 302758199 by chilinski on Friday 18th of January 2013 03:05:14 PM
Old 01-18-2013
Liveupgrade with RAID

I am not a Solaris maven.

I've read and read and read the docs, and I just don't get it, so I'm here to ask for clarification.

I have a T2000/Solaris10u8. It has three drives. Drive 0 and Drive 1 are mirrored with metaxxxxx. Drive 2 has some untouchable data. It hasn't been treated nicely in a very long time and now it's on my plate.

It needs to be patched. So my approach was to install a fourth drive (Drive 3) and do a lucreate to copy the system to a backup environment on Drive 3. I then patched the backup and luactivate(d) it and booted from it. Everything was fine. Since it's only one drive, it exists as c1t3d0s0.

So after successful testing, I want to return control to Drive 0 so I can take Drive 3 out and use it on the next machine to update. Lumake didn't like me trying to use either md0 or c1t0d0s0. In the end I got rid of the original BE that was on Drive 0 (ludelete) and did a lucreate from Drive 3 to Drive 0 (using its /dev/md/dsk/d0 address). When I activated Drive 0 and rebooted, it came up just fine. The mirror was in place and metastat reported all was good.

But that all seemed kind of a clunky way to do it. Anyone have a better, more educated and experienced approach?
 

9 More Discussions You Might Find Interesting

1. Solaris

Solairs 9 to Solaris 10 liveupgrade issue

Hello, I started the upgrade using LiveUpgrade. I am using Solaris 10 instalation CDs (5 CDs). My server is Enterprise 3500 - SPARC. 1) lucreate -c first_disk -m /:/dev/dsk/c0t11d0s7:ufs -n second_disk ... luupgrade -u -n second_disk -s /cdrom/cdrom0/s0 WARNING: <5> packages failed to... (0 Replies)
Discussion started by: zafyil
0 Replies

2. Solaris

solaris 10 liveupgrade issues

I got this output from a system running solaris 10 : # lustatus BE_name Complete Active ActiveOnReboot CopyStatus -------------------------------------------------------------------------------- oldvol yes yes yes - newvol no no no - bigvol no no no - # How do i remove (or... (1 Reply)
Discussion started by: ibroxy
1 Replies

3. Solaris

Solaris liveupgrade will NOT boot into new BE

OK, latest in a loooong trail of errors with no information. I've finally gotten a new BE created on another drive, run liveupgrade on it to bring it from sol10u3 to sol10u8 I luactivate sol10u8 lustatus shows the sol10u8 as the active one init 6 system just starts into 10u3 again. I'm... (4 Replies)
Discussion started by: awoodby
4 Replies

4. Solaris

Hardware Raid - LiveUpgrade

Hi, I have a question. Do LiveUpgrade supports hardware raid? How to choose the configuration of the system disk for Solaris 10 SPARC? 1st Hardware RAID-1 and UFS 2nd Hardware RAID-1 and ZFS 3rd SVM - UFS and RAID1 4th Software RAID-1 and ZFS I care about this in the future to take... (1 Reply)
Discussion started by: bieszczaders
1 Replies

5. 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

6. 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

7. Solaris

Using liveupgrade on single ZFS pool

Hi Guys, I have a single ZFS pool with 2 disk which is mirrored if i create a new BE with lucreate should i specify which disk where the new BE should be created? (7 Replies)
Discussion started by: batas
7 Replies

8. 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

9. Solaris

Solaris 10 liveupgrade/ABE advice

Hi all, I have got a few questions on the above topic -> q1) if my intention for creating an ABE is just to use for patching / patchset update - e.g. ./installpatchset -B secondboot --s10patchset luactivate secondboot What is the recommendation that my ABE should consist of ?... (5 Replies)
Discussion started by: javanoob
5 Replies
UMASS(4)						   BSD Kernel Interfaces Manual 						  UMASS(4)

NAME
umass -- USB Mass Storage Devices driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device scbus device usb device umass Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): umass_load="YES" DESCRIPTION
The umass driver provides support for Mass Storage devices that attach to the USB port. To use the umass driver, usb(4) and one of uhci(4) or ohci(4) must be configured in the kernel. Additionally, since umass uses the SCSI sub- system and sometimes acts as a SCSI device, it requires da(4) and scbus(4) to be included in the kernel. HARDWARE
The umass driver supports USB Mass Storage devices, including: o ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M o Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20 o FujiFilm Zip USB Drive ZDR100 USB A o GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M o Huawei Mobile (SD slot) o IBM 32MB USB Memory Key (P/N 22P5296) o IBM 256MB USB Drive (MSYSTEM DiskOnKey2) o IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151) o I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM only) o I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only) o I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI o Iomega USB Zip 100/250 drive o Iomega Zip750 USB2.0 drive o Keian USB1.1/2.0 3.5-inch HDD Case KU350A o Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0 o LaCie P3 HardDrive USB 200GB o Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive o Logitec Mobile USB Memory LMC-256UD o Logitec USB1.1/2.0 HDD Unit SHD-E60U2 o Logitec USB Double-Speed Floppy Drive LFD-31U2 o Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only) o MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M o MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm o MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2 o MELCO USB2.0 MO Drive MO-CH640U2 o Matshita CF-VFDU03 floppy drive o Merlin SM300 MP3/WMA Player (256Mb) o Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable o Motorola E398 Mobile Phone (TransFlash memory card) o NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U o PNY Attache Flash Drive o Panasonic ("Matshita FDD CF-VFDU03") o Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW o Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW) o Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only) o Panasonic floppy drive o Qware BeatZkey! Pro o RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B o SanDisk SDDR-31 (Compact Flash) o SanDisk SDDR-75 (only Compact Flash port works) o Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick) o Sony Portable CD-R/RW Drive CRX10U (CDROM only) o TEAC Portable USB CD-ROM Unit CD-110PU/210PU o Time DPA20B MP3 Player (1Gb) o Trek Thumbdrive 8MB o VAIO floppy drive (includes Y-E Data Flashbuster-U) o Y-E Data floppy drive (720/1.44/2.88Mb) Among the supported digital cameras are: o Asahi Optical (PENTAX) Optio 230 & 330 EXAMPLES
device umass device scbus device da device pass Add the umass driver to the kernel. camcontrol rescan 0 Rescan a Zip drive that was added after boot. The command above assumes that the Zip drive is on the first SCSI bus in the system. camcontrol rescan 0:0:0 camcontrol rescan 0:0:1 camcontrol rescan 0:0:2 camcontrol rescan 0:0:3 Rescan all slots on a multi-slot flash reader, where the slots map to separate LUNs on a single SCSI ID. Typically only the first slot will be enabled at boot time. Again, this assumes that the flash reader is the first SCSI bus in the system. bsdlabel -w da0 zip100 newfs da0c mount -t ufs /dev/da0c /mnt Write a disklabel to the Zip drive (see vpo(4) for the disktab(5) entry), creates the file system and mounts the new file system on /mnt. newfs_msdos /dev/da0 Create a new FAT type file system. Care should be taken not to run newfs(8) on devices that already contain data, as this will result in the information being lost. Many consumer devices such as digital cameras automatically create MS-DOS based file systems when storing information such as images and videos. These file systems can be accessed by specifying the file system type as msdos when using mount(8). SEE ALSO
ehci(4), ohci(4), uhci(4), usb(4), vpo(4), disktab(5), bsdlabel(8), camcontrol(8) AUTHORS
The umass driver was written by MAEKAWA Masahide <bishop@rr.iij4u.or.jp> and Nick Hibma <n_hibma@FreeBSD.org>. This manual page was written by Nick Hibma <n_hibma@FreeBSD.org>. BSD
October 22, 2009 BSD
All times are GMT -4. The time now is 04:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy