w1kl4s/lab-docu
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

add missing sudo, clarify kernel panic note

Browse Source
This commit is contained in:
Jon Sands
2020-02-11 09:32:16 -05:00
parent f497f4692c
commit 29430dff83
5 changed files with 16 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/H310.md
View File

@@ -26,13 +26,13 @@ H310
``` ```
It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note.
**Note:** For some reason, if power is not reset, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something. This only happens the first reboot after crossflashing. There's two ways around this. If you don't have physical access to the server, just reboot now as normal back into the live ISO - the first time you'll get a kernel panic, and it will reboot again. Reboot back into the Live ISO, and the second time it will be fine as IDRAC is now aware his son is gone. **Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well.
The easier way if you have physical access to the server, just completely remove power (unplug all power to the server and wait 20 seconds). Then plug power back in and boot the server back into Linux.
## Programming SAS Address Back ## Programming SAS Address Back
Now rebooted back into the live Linux image, just run the following command, filling in the example address with your own, that you noted down earlier: Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier:
``` ```
sudo su -
setsas 500605b123456777 setsas 500605b123456777
``` ```
It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version: It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version:

7
docs/H710-B0.md
View File

@@ -50,13 +50,12 @@ B0-H710
``` ```
It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note.
**Note:** For some reason, if power is not reset, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something. This only happens the first reboot after crossflashing. There's two ways around this. If you don't have physical access to the server, just reboot now as normal back into the live ISO - the first time you'll get a kernel panic, and it will reboot again. Reboot back into the Live ISO, and the second time it will be fine as IDRAC is now aware his son is gone. **Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well.
The easier way if you have physical access to the server, just completely remove power (unplug all power to the server and wait 20 seconds). Then plug power back in and boot the server back into Linux.
## Programming SAS Address Back ## Programming SAS Address Back
Now rebooted back into the live Linux image, just run the following command, filling in the example address with your own, that you noted down earlier: Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier:
``` ```
sudo su -
setsas 500605b123456777 setsas 500605b123456777
``` ```
It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version: It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version:

8
docs/H710-D1.md
View File

@@ -48,15 +48,15 @@ Now we run the flashing script. Issue the following command to begin the process
``` ```
D1-H710 D1-H710
``` ```
It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note.
**Note:** For some reason, if power is not reset, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something. This only happens the first reboot after crossflashing. There's two ways around this. If you don't have physical access to the server, just reboot now as normal back into the live ISO - the first time you'll get a kernel panic, and it will reboot again. Reboot back into the Live ISO, and the second time it will be fine as IDRAC is now aware his son is gone. **Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well.
The easier way if you have physical access to the server, just completely remove power (unplug all power to the server and wait 20 seconds). Then plug power back in and boot the server back into Linux.
## Programming SAS Address Back ## Programming SAS Address Back
Now rebooted back into the live Linux image, just run the following command, filling in the example address with your own, that you noted down earlier: Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier:
``` ```
sudo su -
setsas 500605b123456777 setsas 500605b123456777
``` ```
It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version: It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version:

6
docs/H710P-B0.md
View File

@@ -50,13 +50,13 @@ B0-H710
``` ```
It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note.
**Note:** For some reason, if power is not reset, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something. This only happens the first reboot after crossflashing. There's two ways around this. If you don't have physical access to the server, just reboot now as normal back into the live ISO - the first time you'll get a kernel panic, and it will reboot again. Reboot back into the Live ISO, and the second time it will be fine as IDRAC is now aware his son is gone. **Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well.
The easier way if you have physical access to the server, just completely remove power (unplug all power to the server and wait 20 seconds). Then plug power back in and boot the server back into Linux.
## Programming SAS Address Back ## Programming SAS Address Back
Now rebooted back into the live Linux image, just run the following command, filling in the example address with your own, that you noted down earlier: Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier:
``` ```
sudo su -
setsas 500605b123456777 setsas 500605b123456777
``` ```
It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version: It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version:

6
docs/H710P-D1.md
View File

@@ -50,13 +50,13 @@ D1-H710
``` ```
It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note. It should automatically do everything required to flash the card. If you don't get any unexpected errors and it completes, we need to reboot and program the SAS address back to finish. See the following note.
**Note:** For some reason, if power is not reset, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something. This only happens the first reboot after crossflashing. There's two ways around this. If you don't have physical access to the server, just reboot now as normal back into the live ISO - the first time you'll get a kernel panic, and it will reboot again. Reboot back into the Live ISO, and the second time it will be fine as IDRAC is now aware his son is gone. **Note:** For some reason, the very first boot after crossflashing the card will cause a kernel panic - I believe it's iDRAC not letting go of something (I was able to see the card put in a fault state via the debug UART when this happens). This only happens the first reboot after crossflashing. When you boot back into the live ISO and get the panic, either let it reboot itself, or use iDRAC to force a reboot. After that boot back into the live ISO again and all will be well.
The easier way if you have physical access to the server, just completely remove power (unplug all power to the server and wait 20 seconds). Then plug power back in and boot the server back into Linux.
## Programming SAS Address Back ## Programming SAS Address Back
Now rebooted back into the live Linux image, just run the following command, filling in the example address with your own, that you noted down earlier: Now rebooted back into the live Linux image, just run the following commands, filling in the example address with your own, that you noted down earlier:
``` ```
sudo su -
setsas 500605b123456777 setsas 500605b123456777
``` ```
It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version: It should succeed without errors. That's it! You can run the following command to get some info about your new card. You should be able to see your SAS address and the same firmware version: