Sponsored Content
Full Discussion: 3510 Disk Array Problem
Top Forums UNIX for Advanced & Expert Users 3510 Disk Array Problem Post 302345204 by DukeNuke2 on Tuesday 18th of August 2009 04:44:53 PM
Old 08-18-2009
you have to take a look at the 3510... the mapped devices are volumes from the 3510, so you have to look there...

---------- Post updated at 22:44 ---------- Previous update was at 22:44 ----------

To keep the forums high quality for all users, please take the time to format your posts correctly.

First of all, use Code Tags when you post any code or data samples so others can easily read your code. You can easily do this by highlighting your code and then clicking on the # in the editing menu. (You can also type code tags [code] and [/code] by hand.)

Second, avoid adding color or different fonts and font size to your posts. Selective use of color to highlight a single word or phrase can be useful at times, but using color, in general, makes the forums harder to read, especially bright colors like red.

Third, be careful when you cut-and-paste, edit any odd characters and make sure all links are working property.

Thank You.

The UNIX and Linux Forums
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Problemwith 3510 array.

I have 2 3510FC arrays, one a JBOD with (7) 146GB drives, and the other with dual RAID controllers, also (7) 146GB drives. The idea was to get 1TB mirrored. Anyway, after installing the Enterprise Storage Manager on a connected V880, I was able to use the "sccli" command and see/configure all the... (7 Replies)
Discussion started by: ridgeback00
7 Replies

2. Solaris

adding existing disks to a 3510 array

I would like to extend a logical drive on our 3510. I have four unallocated disks which I would like to use for this purpose. The 3510 supports a Sun Cluster but for now all I wish to see is a "new" disk when I run format. I am a little familiar with the telnet/ssh session on the 3510 but am... (2 Replies)
Discussion started by: malcqv
2 Replies

3. Solaris

storEDGE A5000 disk Array

Do you know how do I make my solaris 8 detect the storEDGE A5000?. I have problem making it recognise, without that I cannot install VxVM. Any ideas? (7 Replies)
Discussion started by: calsum
7 Replies

4. Solaris

SE 3510 Battery Issue

Hi everyone, I changed the batteries on 29-Jun-2008 for the storedges. But received error messages from the server today,I used the "-u" option to update the service date information but it syntaticaly fails. Why? Jul 4 12:00:03 auriga SUNWscsdServer: <rctrl8001> The battery on... (3 Replies)
Discussion started by: incredible
3 Replies

5. Solaris

EFI Disk labels on 3510 raid array

Hi Peeps, Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it. Anyone got any ideas on how to remove the EFI label? Thanks in advance Martin (2 Replies)
Discussion started by: callmebob
2 Replies

6. Solaris

Disk Array

So I have 2 solaris sun servers one with a disk array with 14 drives which I need to move to the other server. How do I move the disk array configured as a Raid 5 to another server without losing data? So far I know I'll connect the drive, run devfsadm, use format to verify the server see's... (5 Replies)
Discussion started by: Kjons76
5 Replies

7. UNIX for Advanced & Expert Users

Disk Array

HI: I have a DUAL redundant system running in HP-UX 10.20 ( 2 servers) Both servers share an external SCSI disk array. Both server runs a Data base wich uses the disk array to write the data, and that is the way they share the information. The way that the servers see the disk array, is like... (1 Reply)
Discussion started by: pmoren
1 Replies

8. UNIX for Dummies Questions & Answers

Raid0 array stresses only 1 disk out of 3

Hi there, I've setup a raid0 array of 3 identical disks using : mdadm --create --verbose /dev/md0 --level=stripe --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1I'm using dstat to monitor the disk activity : dstat --epoch -D sdb,sdc,sdd --disk-util 30The results show that the stress is not... (8 Replies)
Discussion started by: chebarbudo
8 Replies

9. Filesystems, Disks and Memory

DISK ARRAY PROTECTION SUSPENDED message displayed following disk replacement

Hello, On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active. We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED. ... (1 Reply)
Discussion started by: terrya
1 Replies

10. AIX

DISK ARRAY PROTECTION SUSPENDED message following disk replacement

Hello, On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active. We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED. ... (3 Replies)
Discussion started by: terrya
3 Replies
disksecn(1M)															      disksecn(1M)

NAME
disksecn - calculate default disk section sizes SYNOPSIS
block_size] [-n disk_name] DESCRIPTION
is used to calculate the disk section sizes based on the Berkeley disk partitioning method. recognizes the following options: Produce tables suitable for inclusion in the device driver. Produce tables suitable for generating the disk description file When generating the above tables, use a sector size of block_size bytes, where block_size can be or Defaults to DEV_BSIZE (defined in if not specified. Specifies the disk name to be used in calculating sector sizes; for example, or If an unknown disk name is specified, prompts the user for the necessary disk information. If neither nor table selection switches are specified a default table of the section sizes and range of cylinders used is output. Disk section sizes are based on the total amount of space on the disk as given in the table below (all values are supplied in units of 256-byte sectors). If the disk is smaller than approximately 44 Mbytes, aborts and returns the message Section 44-56MB 57-106MB 107-332MB 333+MB 0 97120 97120 97120 97120 1 39064 39064 143808 194240 3 39064 39064 78128 117192 4 unused 48560 110096 429704 6 7992 7992 7992 7992 10 unused unused unused 516096 Note It is important to note the difference between the block size passed into via the switch argument and the sector size the user is asked to input when an unknown disk name is passed to via the switch argument. The block size is the sector size that assumes the disk to have when it prints the requested tables. All information printed in the tables is adjusted to reflect this assumed sector size (block size) passed in by the user. The sector size requested by when an unknown disk name is passed does not necessarily have to be the same as the assumed sector size (block size) passed in by the switch argument. For example, a user wants to see the device driver tables for the disk named with an assumed sector size (block size) of 256 bytes. The user has the following information about the disk: Disk type = winchester Sector size = 512 Number of sectors per track (512 byte sectors) = 16 Number of tracks = 7 Number of cylinders = 968 Revolutions per minute = 3600 The user invokes by typing the following command: Assuming that is an unknown disk name, prompts the user for the necessary disk information. The user should input the information as shown above, reflecting a sector size of 512 bytes. All the information will be adjusted within to reflect the assumed sector size (block size) of 256 bytes, passed as the argument of the switch, before the requested device driver table is output. This adjustment also takes place when the disk name is known and an assumed sector size (block size) is passed in as the argument of the switch which is not DEV_BSIZE bytes, the assumed sector size (block size) used to create the file. RETURN VALUE
returns the following values: Successful completion. Usage error. User did not input parameters for an unknown disk. Disk too small or an invalid block size. aborts and prints an error message under the following conditions: o was invoked without specifying a disk name. o Requested both and switch. o Illegal block size requested. o Unknown disk name was specified and user did not supply disk information. o Disk's maximum storage space is less than approximately 44 MB. WARNINGS
Alternate names are not included in the output when the switch is used. Blanks are required in the command line between each of the switches when invoking A blank is required between the switch and the disk name argument to that switch. For example: does not save the block size used to generate the disk description file. The system assumes that the block size used was DEV_BSIZE when it reads the information stored in the file. AUTHOR
was developed by the University of California, Berkeley. FILES
SEE ALSO
disktab(4). Servers Only disksecn(1M)
All times are GMT -4. The time now is 11:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy