|
|
Sponsored Content
Operating Systems
Solaris
Unable to add disk to VG group.
Post 302538735 by jpkumar10 on Thursday 14th of July 2011 04:45:51 AM
07-14-2011
|
|
9 More Discussions You Might Find Interesting
1. AIX
Hi,
I'm trying to create a new group on an AIX 5.2.0.0. server but am getting the following error:
root:/root $ mkgroup debt
3004-698 Error committing changes to "debt" : Value is invalid.
I've change the group name to no affect.
Does anyone have any ideas what could be causing this?
... (0 Replies)
Discussion started by: m223464
0 Replies
2. Solaris
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies
3. Shell Programming and Scripting
I have a file in the following format. Groups of data merge together and the group number is indicated above each group.
1
adrf
dfgr
dfg
2
dfgr
dfgr
3
dfef
dfr
fd
4
fgrt
fgr
fgg
5
fgrt
fgr (3 Replies)
Discussion started by: Lucky Ali
3 Replies
4. Shell Programming and Scripting
Hi All
I do have a file like this with 6 columns. Groups of data merge together and the group number is indicated above each group.
1
1 12 26 289 3.2e-027 GCGTATGGCGGC
2 12 26 215 6.7e+006 TTCCACCTTTTG
3 9 26 175 ... (1 Reply)
Discussion started by: Lucky Ali
1 Replies
5. UNIX for Dummies Questions & Answers
We want to deactivate a VG but failed, because one of the LVs created there is busy. When we are trying to unmount the LV, it is telling "not mounted" and if I execute mount command it will be informing us "already mounted". dmsetup info is indicating "Open Count = 1".
Please help me, how we... (5 Replies)
Discussion started by: atanubanerji
5 Replies
6. Solaris
I have installed Solaris 10 in VMware. Whenever I am trying to add new group using the command '/usr/sbin/groupadd/oinstall' while logged in as root , it is showing as '/usr/sbin/groupadd/oinstall can not execute'.
It will be great to hear any inputs/advice here. (4 Replies)
Discussion started by: sandip250382
4 Replies
7. AIX
Would some help me on this below
I am trying to extend file system on AIX and however unable to extend the file system.
0516-306 extendvg: Unable to find physical volume 20 in the Device
Configuration Database.
0516-321 extendvg: Physical volume u01-lv is not configured.
0516-792... (15 Replies)
Discussion started by: murali969
15 Replies
8. HP-UX
Hello all,
So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'`
do
rmsf -H $i
done
I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies
9. HP-UX
This has got to be the system from hell. Once again, on the RP4440 (after the supplier replaced the entire box due to the bad RTC battery), finally have it all reloaded with the packages the developers need. The last thing is to add the secondary disk to the OS.
BCH sees both OS and secondary... (2 Replies)
Discussion started by: mrmurdock
2 Replies
LEARN ABOUT NETBSD
mly
MLY(4) BSD Kernel Interfaces Manual MLY(4) NAME
mly -- Mylex AcceleRAID/eXtremeRAID family driver SYNOPSIS
mly* at pci? dev ? function ? scsibus* at mly? DESCRIPTION
The mly driver provides support for Mylex AcceleRAID and eXtremeRAID family of PCI to SCSI RAID controllers with version 6.00 and later firmware. Supported controllers include: o AcceleRAID 160 o AcceleRAID 170 o AcceleRAID 352 o eXtremeRAID 2000 o eXtremeRAID 3000 Compatible Mylex controllers not listed should work, but have not been tested. Logical devices (disk arrays) attached to the controller are presented to the SCSI subsystem as though they were direct-access devices on a virtual SCSI bus. Physical devices which are not claimed by a logical device are presented on SCSI channels which match the physical chan- nels on the controller. The results of the SCSI ``INQUIRY'' command from logical devices are overwritten with status information by the mly driver. The vendor field is the string ``MYLEX'', the product field indicates the type of logical device, and the revision field contains a four letter status code. The possible status codes and their meanings are as follows: OFLN offline UNCF unconfigured ONLN online - optimal CRIT critical - one or more disks in the array has failed NORD write only STBY standby MISS missing DIAGNOSTICS
Controller initialization phase mly%d: controller initialization started mly%d: initialization complete The controller firmware has started initialization. Normally this process is performed by the controller BIOS, but the driver may need to do this in cases where the BIOS has failed, or is not compatible (e.g. on non-x86 systems). mly%d: drive spinup in progress Drive startup is in progress; this may take several minutes. mly%d: mirror race recovery failed, one or more drives offline mly%d: mirror race recovery in progress mly%d: mirror race recovery on a critical drive These error codes are undocumented. mly%d: FATAL MEMORY PARITY ERROR Firmware detected a fatal memory error; the driver will not attempt to attach to this controller. mly%d: unknown initialization code %x An unknown error occurred during initialization; it will be ignored. Operational diagnostics mly%d: physical device %d:%d online mly%d: physical device %d:%d standby mly%d: physical device %d:%d automatic rebuild started mly%d: physical device %d:%d manual rebuild started mly%d: physical device %d:%d rebuild completed mly%d: physical device %d:%d rebuild cancelled mly%d: physical device %d:%d rebuild failed for unknown reasons mly%d: physical device %d:%d rebuild failed due to new physical device mly%d: physical device %d:%d rebuild failed due to logical drive failure mly%d: physical device %d:%d found mly%d: physical device %d:%d gone mly%d: physical device %d:%d unconfigured mly%d: physical device %d:%d expand capacity started mly%d: physical device %d:%d expand capacity completed mly%d: physical device %d:%d expand capacity failed mly%d: physical device %d:%d parity error mly%d: physical device %d:%d soft error mly%d: physical device %d:%d miscellaneous error mly%d: physical device %d:%d reset mly%d: physical device %d:%d active spare found mly%d: physical device %d:%d warm spare found mly%d: physical device %d:%d initialization started mly%d: physical device %d:%d initialization completed mly%d: physical device %d:%d initialization failed mly%d: physical device %d:%d initialization cancelled mly%d: physical device %d:%d write recovery failed mly%d: physical device %d:%d scsi bus reset failed mly%d: physical device %d:%d double check condition mly%d: physical device %d:%d device cannot be accessed mly%d: physical device %d:%d gross error on scsi processor mly%d: physical device %d:%d bad tag from device mly%d: physical device %d:%d command timeout mly%d: physical device %d:%d system reset mly%d: physical device %d:%d busy status or parity error mly%d: physical device %d:%d host set device to failed state mly%d: physical device %d:%d selection timeout mly%d: physical device %d:%d scsi bus phase error mly%d: physical device %d:%d device returned unknown status mly%d: physical device %d:%d device not ready mly%d: physical device %d:%d device not found at startup mly%d: physical device %d:%d COD write operation failed mly%d: physical device %d:%d BDT write operation failed mly%d: physical device %d:%d missing at startup mly%d: physical device %d:%d start rebuild failed due to physical drive too small mly%d: physical device %d:%d sense data received mly%d: sense key %d asc %02x ascq %02x mly%d: info %4D csi %4D mly%d: physical device %d:%d offline mly%d: sense key %d asc %02x ascq %02x mly%d: info %4D csi %4D The reported event refers to the physical device at the given channel:target address. mly%d: logical device %d:%d consistency check started mly%d: logical device %d:%d consistency check completed mly%d: logical device %d:%d consistency check cancelled mly%d: logical device %d:%d consistency check completed with errors mly%d: logical device %d:%d consistency check failed due to logical drive failure mly%d: logical device %d:%d consistency check failed due to physical device failure mly%d: logical device %d:%d automatic rebuild started mly%d: logical device %d:%d manual rebuild started mly%d: logical device %d:%d rebuild completed mly%d: logical device %d:%d rebuild cancelled mly%d: logical device %d:%d rebuild failed for unknown reasons mly%d: logical device %d:%d rebuild failed due to new physical device mly%d: logical device %d:%d rebuild failed due to logical drive failure mly%d: logical device %d:%d offline mly%d: logical device %d:%d critical mly%d: logical device %d:%d online mly%d: logical device %d:%d initialization started mly%d: logical device %d:%d initialization completed mly%d: logical device %d:%d initialization cancelled mly%d: logical device %d:%d initialization failed mly%d: logical device %d:%d found mly%d: logical device %d:%d gone mly%d: logical device %d:%d expand capacity started mly%d: logical device %d:%d expand capacity completed mly%d: logical device %d:%d expand capacity failed mly%d: logical device %d:%d bad block found mly%d: logical device %d:%d size changed mly%d: logical device %d:%d type changed mly%d: logical device %d:%d bad data block found mly%d: logical device %d:%d read of data block in bdt mly%d: logical device %d:%d write back data for disk block lost The reported event refers to the logical device at the given channel:target address. mly%d: enclosure %d fan %d failed mly%d: enclosure %d fan %d ok mly%d: enclosure %d fan %d not present mly%d: enclosure %d power supply %d failed mly%d: enclosure %d power supply %d ok mly%d: enclosure %d power supply %d not present mly%d: enclosure %d temperature sensor %d failed mly%d: enclosure %d temperature sensor %d critical mly%d: enclosure %d temperature sensor %d ok mly%d: enclosure %d temperature sensor %d not present mly%d: enclosure %d unit %d access critical mly%d: enclosure %d unit %d access ok mly%d: enclosure %d unit %d access offline These events refer to external enclosures by number. The driver does not attempt to name the enclosures. mly%d: controller cache write back error mly%d: controller battery backup unit found mly%d: controller battery backup unit charge level low mly%d: controller battery backup unit charge level ok mly%d: controller installation aborted mly%d: controller mirror race recovery in progress mly%d: controller mirror race on critical drive mly%d: controller memory soft ecc error mly%d: controller memory hard ecc error mly%d: controller battery backup unit failed These events report controller status changes. SEE ALSO
cd(4), ch(4), intro(4), mlx(4), scsi(4), sd(4), st(4), scsictl(8) HISTORY
The mly driver first appeared in NetBSD 1.6, and was based on the FreeBSD driver of the same name. BUGS
The mly driver currently assumes that all busses support at most 16 targets and 1 logical unit per target. Enclosures are not named or otherwise identified in event messages. The transfer speed for devices is always reported to the kernel as 20MHz. BSD
July 29, 2001 BSD