06-08-2013
Speaking from the experience with Netra T4-2: when you configure hardware RAID, the resulting disk in "format" contains "LSI" in its name, which is not the case here. Also, when two disks are hardware-mirrored, they are visible as single disk in Solaris, so there would be 7 disks visible here and not 8.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
How does the Solaris identifies the controller subscript ? ( like c0txdxs0 or c1txdxsx ?? )
I have a unix box ( Ultra 30) running with 2.5.1.
When I connected an external hard disk to the on-board scsi port, it got identified as c0t1dxsx...
(... (1 Reply)
Discussion started by: shibz
1 Replies
2. Solaris
Hi,
I am a newbie to Solaris. I want to know how to find out the controller target and disk number on a SunFire V890 box that has 6X72GB disks. The probe-scsi output is as shown below:
/pci@8,600000/SUNW,qlc@2
LiD HA LUN --- Port WWN --- ----- Disk description -----
0 0 0 ... (1 Reply)
Discussion started by: sudhir_shet
1 Replies
3. Solaris
Dear Solarizer,
If i have a disk let say like this c1t0d0s0
How to change the controller to be come example : c3t0d0s0
Thanxs For your replay
Regads,
tpx (3 Replies)
Discussion started by: tpx99
3 Replies
4. SCO
hi...
i hav a problem to install sco unix
while installing sco unix 5.0.5 in acer altos with hardware raid
am getting error
"Warning HD: no root disk controller was found
system error 5: while getting fs type
flushing controller: DAC960PRL cache done."
i hav use the following... (18 Replies)
Discussion started by: mselvaprakash
18 Replies
5. HP-UX
Replace an unknown status controller on HP FC60 disk array
Author:JoyOnline JoyChangLu@gmail.com
Trouble description:
The users detected that the status of controller at A is unknown.
Analysis and diagnostic:
Physical observed all leds on enclosure of disk array is normal.
The... (4 Replies)
Discussion started by: JoyOnLine
4 Replies
6. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
7. Solaris
hi all
i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies
8. SCO
So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller.
First, I downloaded the megasas driver from SCO and installed it on the old system.
Then I created a new Microlite Edge emergency boot cd with the new driver on it.
I... (2 Replies)
Discussion started by: jgt
2 Replies
9. Solaris
I changed disk controller. Unplugged every disk, inserted another controller card, an IBM M1015. The disks are recognized in BIOS, and the controller card's BIOS shows up. But after that, I drop into GRUB and a prompt. That is all.
How shall I solve this problem? I am thinking of booting from... (2 Replies)
Discussion started by: kebabbert
2 Replies
10. Solaris
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
LEARN ABOUT PHP
addbadsec
addbadsec(1M) System Administration Commands addbadsec(1M)
NAME
addbadsec - map out defective disk blocks
SYNOPSIS
addbadsec [-p] [ -a blkno [blkno...]] [-f filename] raw_device
DESCRIPTION
addbadsec is used by the system administrator to map out bad disk blocks. Normally, these blocks are identified during surface analysis,
but occasionally the disk subsystem reports unrecoverable data errors indicating a bad block. A block number reported in this way can be
fed directly into addbadsec, and the block will be remapped. addbadsec will first attempt hardware remapping. This is supported on SCSI
drives and takes place at the disk hardware level. If the target is an IDE drive, then software remapping is used. In order for software
remapping to succeed, the partition must contain an alternate slice and there must be room in this slice to perform the mapping.
It should be understood that bad blocks lead to data loss. Remapping a defective block does not repair a damaged file. If a bad block
occurs to a disk-resident file system structure such as a superblock, the entire slice might have to be recovered from a backup.
OPTIONS
The following options are supported:
-a Adds the specified blocks to the hardware or software map. If more than one block number is specified, the entire list should be
quoted and block numbers should be separated by white space.
-f Adds the specified blocks to the hardware or software map. The bad blocks are listed, one per line, in the specified file.
-p Causes addbadsec to print the current software map. The output shows the defective block and the assigned alternate. This option
cannot be used to print the hardware map.
OPERANDS
The following operand is supported:
raw_device The address of the disk drive (see FILES).
FILES
The raw device should be /dev/rdsk/c?[t?]d?p0. See disks(1M) for an explanation of SCSI and IDE device naming conventions.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
disks(1M), diskscan(1M), fdisk(1M), fmthard(1M), format(1M), attributes(5)
NOTES
The format(1M) utility is available to format, label, analyze, and repair SCSI disks. This utility is included with the addbadsec,
diskscan(1M), fdisk(1M), and fmthard(1M) commands available for x86. To format an IDE disk, use the DOS "format" utility; however, to
label, analyze, or repair IDE disks on x86 systems, use the Solaris format(1M) utility.
SunOS 5.10 24 Feb 1998 addbadsec(1M)