Re: HP MSA 2040 SAN crashing

October 9, 2017, 7:42 am

≫ Next: MSA P2000 G3 FC migrate RAID-10 to RAID-6

≪ Previous: Re: HP MSA 2040 SAN crashing

$

0

0

Hello,

Sorry, I'm sure this isn't the answer you were hoping for but I think you need to open a support case. My guess is that you have a failed/failing controller. You are also extremely far behind on the firmware. Updating the firmware may be part of the recommneded resolution by support but you'll need to follow a specific upgrade path to get to the latest (GL220P010) since you cannot do a direct upgrade from the version you are on. 

Yes, it also appears that a certain server is trying to frequently login via SSH? Perhaps you have some sort of monitoring script installed and it's using an old password? I'd investigate on that host and see what is making the SSH call and why. 

Sorry I couldn't be more helpful. 

---

MSA P2000 G3 FC migrate RAID-10 to RAID-6

October 9, 2017, 5:35 am

≫ Next: P2000 Password Reset

≪ Previous: Re: HP MSA 2040 SAN crashing

$

0

0

Hi,

I would like to migrate a RAID-10 VDISK to a RAID-6 ! How can i perfom this please ?

I initialy thought of making a new RAID-6 VDISK and moving the volumes to the new VDISK.

How ever i don't know how to proceed. Can any one help please ?

P2000 Password Reset

October 10, 2017, 11:46 pm

≫ Next: Which is the correct way to connect MSA2040 sas to HBA H421

≪ Previous: MSA P2000 G3 FC migrate RAID-10 to RAID-6

$

0

0

Hi guys,

I have a P2000 storage and I have forgotten the password of P2000 storage. I couldn't log in both cli and ui. I had changed the password before a long time. I don't want to lose my datas, how to get recover my data without erasing?

I tried this information to login at the below,

admin\!admin

manage\!manage

but I couldn't still log in again

Have a nice day and thanks for your helping.

Which is the correct way to connect MSA2040 sas to HBA H421

October 11, 2017, 1:03 am

≫ Next: Re: P2000 Password Reset

≪ Previous: P2000 Password Reset

$

0

0

Hi

I bought a MSA 2040 sas with 2 sas controllers (C8S53A), DL380 G9 whit 2 hba h241, autoloader and 3 sas cables, miniSas hd to minisas for the autoloader (Part NO: 716191-B21), and the others two cables are minisas hd to minisas hd for the msa to server (Part NO: 716195-B21) 

In theory always is compatible and should be works

The autoloader works fine whit her cable, but the msa connected to the server doesn't work with minisas hd cables, only works if I connect it using minisas hd to miniSas cable, I have tried some combinations with the 2 minisas HD cables but no one works

Please help!

 

Re: P2000 Password Reset

October 11, 2017, 5:08 am

≫ Next: Re: P2000 Password Reset

≪ Previous: Which is the correct way to connect MSA2040 sas to HBA H421

$

0

0

HPE Support has a specific process to do this but you'll need to call and engage them. I'm not aware of a supported way without engaging support. You'll need the serial cable that came with the array to connect between your computer and MSA controller. 

Re: P2000 Password Reset

October 12, 2017, 4:18 am

≫ Next: MSA P2000 vdisk crash after replacing failed drive

≪ Previous: Re: P2000 Password Reset

$

0

0

Hi, thanks for your comment. I contacted to HPE. They presented me a solution but it didn't work.  The solution is like this at the below.

I connected to the storage and used this information user name: restoredefaults, password: 00C0FFXXXXXX after this process, the device entered restore mode and restarts it itself. The printable version is this at the below.

note: XXXXXX is the last digital number of my controller.

System Version: TS251P005
MC Version: L251R005-09
Serial Number: 00C0FFXXXXXX
192.168.x.x login: restoredefaults
Password: 00C0FFXXXXXX

2017-10-12 13:41:50: Perform Restore Defaults
2017-10-12 13:41:50: Sleeping for 60
2017-10-12 13:42:50: Killing apps
killall: mccli: no process killed
killall: rpcget: no process killed
killall: udhcpc: no process killed
killall: ntpclient: no process killed
killall: logc: no process killed
2017-10-12 13:42:55: Sleeping for 5
PID USER VSZ STAT COMMAND
1 root 3716 S init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [kworker/0:0]
5 root 0 SW [kworker/u:0]
6 root 0 SW [rcu_kthread]
7 root 0 SW< [khelper]
8 root 0 SW [kworker/u:1]
85 root 0 SW [sync_supers]
87 root 0 SW [bdi-default]
88 root 0 SW< [kblockd]
97 root 0 SW [khubd]
184 root 0 SW< [rpciod]
185 root 0 SW [kworker/0:1]
196 root 0 SW [kswapd0]
197 root 0 SW [fsnotify_mark]
198 root 0 SW< [aio]
199 root 0 SW< [nfsiod]
201 root 0 SW< [crypto]
271 root 0 SW [mtdblock0]
276 root 0 SW [mtdblock1]
281 root 0 SW [mtdblock2]
286 root 0 SW [mtdblock3]
291 root 0 SW [mtdblock4]
296 root 0 SW [mtdblock5]
301 root 0 SW [mtdblock6]
306 root 0 SW [mtdblock7]
311 root 0 SW [mtdblock8]
316 root 0 SW [mtdblock9]
321 root 0 SW [mtdblock10]
326 root 0 SW [mtdblock11]
331 root 0 SW [mtdblock12]
491 root 0 SWN [jffs2_gcd_mtd9]
528 root 3716 S klogd
541 root 1792 S timed
551 root 3584 S slattach -p slip -s 230400 /dev/ttyS2
577 root 0 SW [flush-1:0]
668 root 1800 S memtrack
670 root 1796 S vmtrack
694 root 1804 S portmap
784 root 3716 S init
785 root 3716 S init
786 root 3716 S init
787 root 3716 S init
788 root 3720 S /sbin/getty -L ttyS1 115200 vt100
881 root 0 SW [flush-mtd-unmap]
948 root 3716 S telnetd
1243 root 2360 S pure-ftpd (SERVER)
3063 root 3716 S /bin/sh /home/restore/shell
3086 root 3720 S /bin/sh /app/default/restoreDefaults.sh
3293 root 3720 R ps
2017-10-12 13:43:01: restoring normal defaults
2017-10-12 13:43:01: Restore SysInfo Defaults
2017-10-12 13:43:02: saving lastKnownGoodProductBrand [9]
2017-10-12 13:43:02: saving brandDir [hp]
2017-10-12 13:43:02: saving vendorName [HP]
2017-10-12 13:43:02: saving productBrand [MSA]
2017-10-12 13:43:02: saving productId [P2000]
2017-10-12 13:43:02: saving scsiVendorId [HP]
2017-10-12 13:43:02: saving scsiProductId [P2000]
2017-10-12 13:43:02: saving timezoneOffset [2]
2017-10-12 13:43:02: saving ntpActive [false]
2017-10-12 13:43:02: saving ntpIpV4Address [0.0.0.0]
2017-10-12 13:43:02: saving ntpIpV6Address [::]
2017-10-12 13:43:02: saving timezoneOffset [2]
2017-10-12 13:43:02: saving timezoneOffsetInMinutes [120]
2017-10-12 13:43:03: saving lastANotified [254]
2017-10-12 13:43:03: saving lastBNotified [251]
2017-10-12 13:43:03: saving macAddress [c0ff159898]
2017-10-12 13:43:03: saving hostName [192.168.50.2]
2017-10-12 13:43:03: saving nameServer [-null-]
2017-10-12 13:43:03: saving ipV6Address [::]
2017-10-12 13:43:03: saving macAddress [c0ff159b89]
2017-10-12 13:43:03: saving hostName [192.168.50.3]
2017-10-12 13:43:03: saving nameServer [-null-]
2017-10-12 13:43:03: saving ipV6Address [::]
2017-10-12 13:43:03: saving addressSource [1]
2017-10-12 13:43:03: saving ipV4Address [192.168.50.2]
2017-10-12 13:43:03: saving ipV4Mask [255.255.255.0]
2017-10-12 13:43:03: saving ipV4Gateway [192.168.50.1]
2017-10-12 13:43:03: saving dhcpLease [0]
2017-10-12 13:43:04: saving addressSource [1]
2017-10-12 13:43:04: saving ipV4Address [192.168.50.3]
2017-10-12 13:43:04: saving ipV4Mask [255.255.255.0]
2017-10-12 13:43:04: saving ipV4Gateway [192.168.50.1]
2017-10-12 13:43:04: saving dhcpLease [0]
2017-10-12 13:43:04: saving bundleVersion [TS251P005]
2017-10-12 13:43:04: saving bundleBuildDate [Thu Jul 10 15:11:38 MDT 2014]
2017-10-12 13:43:04: saving mcVersion [L251R005-09]
2017-10-12 13:43:04: Restore emailOut Defaults
2017-10-12 13:43:04: Restore user Defaults
2017-10-12 13:43:04: Restore roles Defaults
2017-10-12 13:43:05: Restore etc Defaults
2017-10-12 13:43:05: Restore secure Defaults
2017-10-12 13:43:05: Restore log Defaults
2017-10-12 13:43:05: Restore rs Defaults
2017-10-12 13:43:05: Restore scheds Defaults
2017-10-12 13:43:05: Restore tasks Defaults
2017-10-12 13:43:05: sleeping for 5
2017-10-12 13:43:10: Rebooting now...

have a nice day.

MSA P2000 vdisk crash after replacing failed drive

October 11, 2017, 9:22 am

≫ Next: Re: MSA1000 Conroller CLI Cable Pin out...

≪ Previous: Re: P2000 Password Reset

$

0

0

Two days ago I began receiving emails from my P2000 that the drive in slot 12 was experiencing a unrecoverable read error (event 58).  This continued for a few minutes until the drive failed completely and the vdisk went into a critical state.

The next morning, I replaced the drive with a new one and configured it as a hot spare.  The vdisk began reconstruction, but after about 10 minutes, I received a vdisk quarantined message followed by a reconstruct failed message.

Following that the LED on the replacement drive in slot 12 stayed green, but the drive in slot 10 went amber and was labelled "leftovr" in the management utility. The vdisk was again in a critical state and was inaccessible, crashing several of my VMs.

I shut down all of my VMs and then the SAN, removed the new drive from slot 12 and restarted everything.  When everything was back up, the vdisk was again accessible though in a critical state being one drive short.

I repeated the drive replacement this morning. Cleared the metadata from the drive and added it as a hot spare. Again, in about 10 minute of reconstruction, the vdisk failed and the drive in slot 10 was marked "leftovr".  I removed the drive from slot 12 and the vdisk recovered in about 30 seconds.

Can anyone tell me what's going on?

Re: MSA1000 Conroller CLI Cable Pin out...

October 16, 2017, 2:45 am

≫ Next: p2000 コントローラーFWのDLについて

≪ Previous: MSA P2000 vdisk crash after replacing failed drive

$

0

0

Hello!

Thanks, this circuit works!

---

p2000 コントローラーFWのDLについて

October 16, 2017, 7:50 pm

≫ Next: Re: MSA P2000 vdisk crash after replacing failed drive

≪ Previous: Re: MSA1000 Conroller CLI Cable Pin out...

$

0

0

p2000コントローラーのFWをダウンロードしたいのですが、HPEにログインしFirmware(Entitlement Required)よりCP018819やcp024276のダウンロードをしているのですが０KBで正常にダウンロード出来ません。

解決策等ご存知の方いましたら教えてください。

Re: MSA P2000 vdisk crash after replacing failed drive

October 19, 2017, 11:57 am

≫ Next: msa 2040 is not connect to hba sn1000q 16 gb/s

≪ Previous: p2000 コントローラーFWのDLについて

$

0

0

Hello Ben Dalton

I had problems similar to yours. As the EVENT CODE: 58 errors occurred in different HD's and at different times, I opened the incident on HP before making the HD switch. In the end, I thought it would be better to empty the whole P2000 and then go to firmware update of all HD's and after all the controllers. I did'nt update since 2010. After all this we detected that only one disk was in trouble, the rest were probably bugs.

If your firmwares are not updated, I think that update can help you. But in my case, I migrated all data before.

msa 2040 is not connect to hba sn1000q 16 gb/s

October 23, 2017, 1:57 am

≫ Next: Re: MSA 2042, setup SSD Tiering

≪ Previous: Re: MSA P2000 vdisk crash after replacing failed drive

$

0

0

hello.

i have msa 2040 (k2r80a) and sfp transiver is c8r24a 16 gb/s on it, and i have dl380 gen 9 with hba card sn1000q 16 gb/s(qw972a), when i connect transiver to hba by fiber channel cabel is not showing initiator in smu and host section in msa 2040.

but when i use hba 82q(aj764a) 8gb/s the connection is ok and initiators is show in smu

 

Re: MSA 2042, setup SSD Tiering

October 23, 2017, 3:35 pm

≫ Next: admin password issue on Hp MSL 2024 Tape library

≪ Previous: msa 2040 is not connect to hba sn1000q 16 gb/s

$

0

0

Hi there, looking your answers regarding tiering and asking for information. You said:  "...then add to it a virtual disk group with the 2 SSD disks. this will be your performance tier.". My questions:

1. Can one ssd disk be selected for performance tiering? When I tried to Add disk group to a pool I am offered only RAid1, 5, 6 or 10 for Virtual Group. (For Read Cashe I can select one disk)

2. It looks I have to commit twlo SSD's and have RAID1 (minimum) to get performance tiering in that group. Correct?

rgds

admin password issue on Hp MSL 2024 Tape library

October 24, 2017, 6:07 am

≫ Next: MSA 2040 how to change hard disk correctly?

≪ Previous: Re: MSA 2042, setup SSD Tiering

$

0

0

MSA 2040 how to change hard disk correctly?

October 24, 2017, 7:21 am

≫ Next: Re: MSA 2040 how to change hard disk correctly?

≪ Previous: admin password issue on Hp MSL 2024 Tape library

$

0

0

Hello.

We have storage MSA 2040, now it is working in our company.

Vdisk is not created. Now i can see the message, that 1 of hard disk is have healf "degraded" and Status - "LEFTOVR".

As I read information from Internet, the firs recomendation is "Before you can use the disk in a new vdisk or as a spare, you must clear the disk’s metadata."

But this device in production, so i can`t have risk and make mistakes when try to solve the problem.

Please, tell me correct procedure to solve the problem. 

If the hard disk is broken, i will have to change it to same disk with same size?

If you need any additional information, I will send it. Thanks.

Есть в наличии хранилище MSA 2040. Сейчас находится в работе. 

Vdisk на нем не созданы. Недавно появилось сообщение о том, что 1 из дисков "Degraded".  судя по информации из Интернета, для устранения ошибки, необходимо очистить метаданные. Тк устройство "боевое", рисковать не хочется. прошу подсказать правильный порядок действий для исправления ошибки. 

Если все же диск вышел из строя, заменить его можно только аналогичным такого же размера?

Заранее спасибо.

Re: MSA 2040 how to change hard disk correctly?

October 25, 2017, 2:38 am

≫ Next: Re: admin password issue on Hp MSL 2024 Tape library

≪ Previous: MSA 2040 how to change hard disk correctly?

$

0

0

For any reason the contents of this disk is no longer current, hence "leftover".

 

Consider to clear the metadata of this disk, this will "empty" this disk and you can try to use it again. Maybe you need to declare it as a spare.

 

If you replace a disk, it must be the same type and should be the same size (or even larger), then you need it to declare as a global or dedicated spare.

---

Re: admin password issue on Hp MSL 2024 Tape library

October 25, 2017, 4:05 am

≫ Next: Re: MSA 2040 how to change hard disk correctly?

≪ Previous: Re: MSA 2040 how to change hard disk correctly?

$

0

0

Open a Case.

They can generate you a One Time Passord for 1h.

Re: MSA 2040 how to change hard disk correctly?

October 25, 2017, 5:31 am

≫ Next: MSA2040 hard drive firmware - ST4000NM0125 E002

≪ Previous: Re: admin password issue on Hp MSL 2024 Tape library

$

0

0

Hello.

Torsten, thank you for you answer. I have 2 storages in HP 2040, each contains 12 hard disks. As I know, each storage has RAID 5 structure. 

If I will make "clear disk metada", after that, will I have to do any ather action to install this disk to the RAID?

MSA2040 hard drive firmware - ST4000NM0125 E002

October 26, 2017, 1:24 pm

≫ Next: Re: MSA2040 hard drive firmware - ST4000NM0125 E002

≪ Previous: Re: MSA 2040 how to change hard disk correctly?

$

0

0

Hi All, running a batch of 4TB Seagate drives just now, and noticing that 11/12 of the drives I have are at E002 firmware, but one is at E001 (all came from factory sealed boxes).  Normally no big deal, but in this case there doesn't appear to be any kind of update file from HP for this specific drive model, the ST4000NM0125.  Can anyone point me to such a file?  Even the MSA matrix here shows E002 as the proper version for these - https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04315770

Re: MSA2040 hard drive firmware - ST4000NM0125 E002

October 26, 2017, 2:59 pm

≫ Next: Re: MSA2040 hard drive firmware - ST4000NM0125 E002

≪ Previous: MSA2040 hard drive firmware - ST4000NM0125 E002

$

0

0

Hi Mike!

Does just the drive label say E001 or did you install the drive in the array and the arrary reported the drive firmware at E001?   

Thanks!
/Kipp

Re: MSA2040 hard drive firmware - ST4000NM0125 E002

October 27, 2017, 5:00 am

≫ Next: Re: MSA2040 hard drive firmware - ST4000NM0125 E002

≪ Previous: Re: MSA2040 hard drive firmware - ST4000NM0125 E002

$

0

0

Unfortunately it says it within the GUI - It's the real deal.