HPE Storage Users Group https://3parug.net/ |
|
InformOs is gone https://3parug.net/viewtopic.php?f=18&t=3390 |
Page 1 of 2 |
Author: | der_gin [ Thu Apr 23, 2020 4:07 am ] |
Post subject: | InformOs is gone |
Hello Forum We have en older 3PAR c7200c. After the deinstallation process (Point 8 in Console) one of the Nodes don't boot anymore it's only shows the whack prompt. The other Node is working normally. Is there a possibility to rescue the other node ? I hear from a node recovery process but i don't found anything at HPE or Google. Thanks for an Answer and sorry for the bad English ^^ |
Author: | MammaGutt [ Thu Apr 23, 2020 11:54 am ] |
Post subject: | Re: InformOs is gone |
https://community.hpe.com/t5/3par-store ... qHHTWmxWDY Just asking, could the local drive in the node be dead as the OS is gone? Sounds really weird for it to just be gone. |
Author: | der_gin [ Thu Apr 23, 2020 1:17 pm ] |
Post subject: | Re: InformOs is gone |
This is a possibility. Do you think we should try the wipe of the disk? And after this a Node to Node recovery? |
Author: | Richard Siemers [ Thu Apr 23, 2020 11:04 pm ] |
Post subject: | Re: InformOs is gone |
Keep in mind that you do have the option for a service call charged for time and materials, even if you do not have a support contract. 7200 is still supported. The support number for out-of-warranty cases is (US) 1-844-806-3425. |
Author: | der_gin [ Fri Apr 24, 2020 5:21 pm ] |
Post subject: | Re: InformOs is gone |
This 3Par is just for training purposes. I managed to start the node to node rescue but this happened. Any idea? Do I just do something wrong? Disabled FSBC boot watchdog. Whack> Whack>set perm cnt_no_os_boot=0 Whack>set perm cnt_no_cluster=0 Whack>set perm cnt_no_shutdown=0 Whack>set perm cnt_os_panic=0 Whack>set perm cnt_same_fatal=0 Whack>set perm cnt_log_error=0 Whack>set perm sys_serial=1685706 Whack>eth dev 0 Selected ethernet device 0 at Memory c0900000 Whack>net addr 169.254.169.115 My address is 169.254.169.115 Whack>net netmask 0.0.0.16 Network mask 0.0.0.16 Whack>net gateway 169.254.169.115 Gateway address 169.254.169.115 Whack>net server 169.254.169.115 Server address 169.254.169.115 Whack>boot net install cr=2 ipaddr=169.254.169.115 nm=255.255.0.0 rp=169.254.169.115::rescue hn=1685706_1 eth=eth0 Testing CMA0 MMW address lines with walking 1 (first 4 GB only) Testing CMA0 MMW address lines with walking 0 (first 4 GB only) Testing CMA0 with random XOR (all Cluster Memory) 4095 MB [..................................................] --> Skipping: [29] Cluster PCI Diagnostic --> Starting: [30] DIMM Information Collection Collecting CPU DIMM info: Collecting ASIC DIMM info: --> Skipping: [31] Manufacturing Centerpanel GPIO Test --> Skipping: [32] Serial Port Loopback Test --> Skipping: [33] Manufacturing Serial Port Test --> Starting: [34] Environmental Initialization --> Skipping: [35] Environmental Temperature and Voltage Test --> Skipping: [36] Test CPU Operation --> Skipping: [37] Manufacturing Cluster Link Initialization --> Skipping: [38] Manufacturing Cluster Link Test --> Skipping: [39] PCI Fibre Channel/SAS Adapter Test --> Skipping: [40] PCI iSCSI Adapter Test --> Starting: [41] System Error Reporting Init --> Skipping: [43] Manufacturing CP EEPROM Test --> Skipping: [44] Certify OS Startup --> Skipping: [45] Table Execution Summary +-----------------------------------------------------------------------------+ HP SPI Image 4.8.38. Release version. 16:57:04 Jul 17 2015. +-----------------------------------------------------------------------------+ | CPU 1 x 1.80 GHz Sandy Bridge hexa core HT dual | Control Cache Size 15.100 GB (cpu mem type 11) CL9 | Set0 CC DIMM0.0 (J0155): 16384 MB CL5/11 | Data Cache Size 4 GB CL4/6 | Set0 DC DIMM0.0 (J0300): 2048 MB CL4/6 | Set0 DC DIMM1.0 (J0301): 2048 MB CL4/6 | Slot ID 1 [2 Node HP 3PAR 7200c Centerplane] | FPGA Eos v0.f | SATA0 Disk SanDisk DX110128A5xnNMRI 144503400881 128 GB | PCI Slot 0 LSI-SAS 9205-8e | PCI Slot 1 Emulex LPe12002 VM80175440 2-port | PCI Slot 2 Emulex LPe12004 5CF45003JX 4-port | Board 920-200040.B5 FXN 2014/52/Sun 02811946 d4:c9:ef:08:df:20 | Cluster serial 1685706 d4:c9:ef:08:df:21 | Board reset reason PCI_RESET | Current Time 2020-04-24 23:37:37 (UTC+2) +-----------------------------------------------------------------------------+ AHCI0 MBR does not have a valid partition table BIOS wrote initial PCIe tree to idelog Booting from net... TFTP "install" from 169.254.169.115.No ethernet ARP response for 169.254.169.115 TFTP send failed for 169.254.169.115 at 00:00:00:00:00:00 failed Disabled FSBC boot watchdog. |
Author: | der_gin [ Tue Apr 28, 2020 9:58 am ] |
Post subject: | Re: InformOs is gone |
No ideas? |
Author: | Richard Siemers [ Tue Apr 28, 2020 8:24 pm ] |
Post subject: | Re: InformOs is gone |
Have you seen this? https://support.hpe.com/hpesc/public/do ... =c02998730 Your log shows its trying to TFTP boot but doesn't find the server, I think you just need to establish connectivity with an ethernet cross over cable per the manual recovery instructions section of the link above. Let us know how it goes! |
Author: | der_gin [ Wed Apr 29, 2020 8:02 am ] |
Post subject: | Re: InformOs is gone |
Thanks yes i try this but this guid is for a physical SP to Node but we have a VM SP. Is there no Node to Node options? |
Author: | MammaGutt [ Wed Apr 29, 2020 10:02 am ] |
Post subject: | Re: InformOs is gone |
I'm pretty sure that document is obsolete from 3.1.2 and later. Node rescue should be node-to-node on newer systems. Maybe verify that you don't have any spanning tree or similar preventing the network to be available as soon as the link is up. Maybe try a direct connection between the nodes in this 2-node system or try a dumb 5-port non-managed switch. |
Author: | der_gin [ Wed Apr 29, 2020 1:40 pm ] |
Post subject: | Re: InformOs is gone |
Unfortunately this all did not work. The system IP is not active. Any idea? 3PAR Console Menu 1685706-0 3.3.1.410 1. Out Of The Box Procedure 2. Re-enter network configuration 3. Update the CBIOS 4. Enable or disable CLI error injections 5. Perform a Node-to-Node rescue 6. Set up the system to wipe and rerun ootb 7. Cancel a wipe 8. Perform a deinstallation 9. Update the system for recently added hardware (admithw) 10. Check system health (checkhealth) 11. Finish SP-to-Node rescue procedure 12. Exit > 5 Enter the node number which needs to be reinstalled: 1 Proceed with rescue of node 1? y The system IP address is not active. |
Page 1 of 2 | All times are UTC - 5 hours |
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |