Tag Info

Hot answers tagged

5

Old, old, old, old... CentOS 6.2 is old (6.2, 6 December 2011 (kernel 2.6.32-220)) HP StorageWorks MSA70 is old. (End of Life - October 2010) HP Smart Array P800 is old. (End of Life - 2010) So this makes me think that firmware and drivers are also old. E.g. there's no reason to run CentOS 6.2 in 2015... And I'm assuming no effort was made to keep ...


4

If you expanded the existing array, it would only use 146GB of each disk. The rest of the 300 would be wasted. There's no reversing it. As you said HP will confirm there's no undo operations. You should be incredibly careful when making changes to make to a SAN; and plan those changes extensively. At this point you can only backup the data, delete the ...


4

It sounds like you're using SATA drives on this HP MSA60 storage setup. Given your previous experiences and problems, you should definitely avoid using RAID 5. I'd use RAID 1+0, but you can make a more informed decision by referencing the Canonical RAID question here on Server Fault. Can you explain what operating system will be in use, how the ...


3

Another reason to be wary of large RAID 5 arrays... Imagine what your rebuild times will be when (not if) you have a failure. Please consider using fewer SATA disks in your setup. There's a chance you already have errors on your existing disks! Smart Array RAID controllers run a background parity initialization upon the creation of a new logical drive. ...


3

Create 2 LUNs of 7 drives each. Use the raid abilities of your OS to stripe a volume across both arrays. Or better yet, pick a ZFS capable OS and let ZFS handle the RAID for you.


3

I know the MSA60 well and although it really is just a SAS JBOD I'd say that you'd struggle to get it to work with that Dell box and even if you could it may not be stable and won't be supported in any way, in fact I think doing that would void HP warranty.


3

The HP MSA60 and MSA70 both present themselves as a simple SAS Expander with drives. I've been told by HP and it's reps that they're only compatible with HPs other MSA and P-Series HBAs. However I've heard other people claim they work fine with other hardware. YMMV. Using them with a Dell unit wouldn't be supported by either company (that support is a large ...


3

Yes, you have some prefailure warnings, get them swapped out ASAP.


3

No. It's not possible. The HP StorageWorks MSA20 is an Ultra 320 parallel SCSI-only device for its external interface. It's a SATA backplane... But remember, it's first-generation SATA; 1.5Gbps. Terrible. If you want something compatible, you'll need an MSA50, MSA60, MSA70, D2600 or D2700... You get the idea. Something more modern. Also see the advice ...


3

I would suggest using an D2600 unit instead of the MSA60, but it will technically work when cascaded from your MSA2324 unit. 6TB drives... 4TB disks are known to work in that enclosure, so the 6TB will likely work. I wouldn't use SATA for a JBOD expansion because (depending on your cabling choice) you'll lose the dual-port/dual-pathing that the SAN ...


2

1) It is very unlikely that you'll be able to recover this particular array. RAID is not backup. This is one of the many reasons you need backups. 2) It depends how the LUNs are set up. If you have one RAID 5 array with all 12 disk that is separated into 3 logical units, then since the array is gone, all its logical units are gone. If you have three ...


2

1) Is there a way to recover? Power down the array. Reseat each disk one by one. Power up the array again. See if any of the failed disks come online. Follow the Maintenance and Administration Guide for your controller on handling failed volumes. While the array is powered down check the S.M.A.R.T data on the failed drives. The drives may be marked ...


2

Oh boy. You should really really learn about the technology you're using BEFORE trying to do maintenance/recovery on it. RAID5 consists of one parity partition alligned over all disks, which means that you can lose 1 disk and still have data available, while rebuilding a new disk (which should be a hot spare). Remove another disk while this is happening ...


2

Like ewwhite pointed out, you are having more problems with your storage system than you should. A single volume should be avoided at all costs, as it forces you to create giant RAID groups. If possible, try to create 5 RAID6 volumes, each with 7 disks (which leaves you with one hot spare). This gives you 25TB of raw storage, which almost fits your ...


1

Add a cookie to your request containing two elements, wbiusername and wbisession key. eg, wbiusername=manage; wbisessionkey=b19ec2e62b49ba39f019ab187ea5efcb I keep the sessionKey header in addition to the cookie to support these older MSAs in addition to the newer ones, works a treat and I don't have to resort to telnet.


1

I've seen this in situations where there are mismatched configurations... The P812 isn't really compatible with the MSA50. I've also seen this in cases where I had drive replacements/substitutions. Either way, you will not be able to see individual drive information, however alerts will indicate the proper slot if a disk fails. An example... The array ...


1

Your MSA2012/P2000 SAN should have a scheduled background "scrub" process enabled. If not, it can be run manually by choosing a vdisk and selecting the "Media Scrub Vdisk." option. As for notification, configure the email notification settings on the array. That's the best way to obtain fault information from the unit.


1

I recommend that you search for more information about this error before you start replacing any hdd's. Info from HP support site about this: http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/hard-drive-error-640006-on-ML350G5/td-p/5597711#.UGQfJFEv-J8 If you don't care about the cost of replacing the disks, replace them as soon as you can. You could ...


1

Well you don't mention which protocols you want to use but for FC the XP range can grow pretty linearly (gets expensive though). I know it's not what you asked for the 9100 EDS stuff is very linear but NAS protocols only.


1

I can't find an official confirmation for this sorry but I did find one for the MSA2324sa working with an MSA70 - which was the SFF version of the MSA60 - so I'd certainly place a small wager that it'll work and probably be supported. That said like ewwhite I also hate the idea of using non-HP disks in HP storage, you don't need to look far on this site to ...


1

You're really not going to be able to get this information out of an MSA or P2000 storage array. At least, no historical information. You could parse the output from the SSL CLI at regular intervals, but that's not ideal. This is just a disadvantage of the platform. You may want to check with the OEM, DotHill to see if anything is available from their ...


1

ewwhite was right. For those how want to see how i get the values in PRTG (Networkmonitoring) here are my scripts. I know the following is NOT very nice and seems to be very "froggy", but for me it works and i only need values over a periode of about a week... The ssh connection is established via "plink.exe" a smart comand line tool as a part of the SSH ...


1

Guess what, hp-fc-enablement was missing. It rebuild my initrd and now it is working. Silly of me not notifing before.



Only top voted, non community-wiki answers of a minimum length are eligible