misc fixes (spacing, fastiron linux password etc)

docs/extract.md

@@ -84,8 +84,12 @@ If you have a non-linux based switch (eg ICX6610) and you REALLY want to extract
 
 Now run the following in the bootloader:
 ```
+#dump the first 32MB of flash (this is usully enough)
 dd f4000000 8388608
+
+#alternatively, dump the full 64MB flash chip
+dd f4000000 16777216
 ```
 It will start printing the raw flash contents line by line in your serial window for a second, then stop. When it stops, press enter (NOT space), to make it continue dumping without user input, so it will dump overnight, and putty will be logging it.
 
-This will take about 10 hours, so go to bed. In the morning, reboot the switch, and take a look at your putty log file. The dump will only be in raw hex, not ASCII - so to find your license strings you need to search the dump for `2a4220` which is the license start string `*B ` in hex. Once you find that, copy the following several blocks of hex values and paste them all into an online hex to ASCII converter, and you should get your string. Make sure you don't paste the leading memory address bits like `f40001e0:` into the converter.
+This will take about 12 hours per 32MB, so go to bed. In the morning, reboot the switch, and take a look at your putty log file. The dump will only be in raw hex, not ASCII - so to find your license strings you need to search the dump for `2a4220` which is the license start string `*B ` in hex. Once you find that, copy the following several blocks of hex values and paste them all into an online hex to ASCII converter, and you should get your string. Make sure you don't paste the leading memory address bits like `f40001e0:` into the converter.

docs/index.md

@@ -1,8 +1,8 @@
 # Welcome
-This is the home of all public documentation by Jon Sands. Originally planned as documentation to share amongst [FBOM](http://fbom.club/) members, it has become more useful on [STH](https://forums.servethehome.com/index.php?threads/brocade-icx6450-icx6610-etc.21107/). Pull requests to the [github repo](https://github.com/Fohdeesha/lab-docu) are always welcome.
+This is the home of all public documentation by Jon Sands. Originally planned as documentation to share amongst [FBOM](http://fbom.club/) members, it has become most useful on [STH](https://forums.servethehome.com/index.php?threads/brocade-icx6450-icx6610-etc.21107/). Pull requests to the [github repo](https://github.com/Fohdeesha/lab-docu) are always welcome.
 
 Other documentation I have written or contributed to:
 
  - [Brokeaid Crossflashing](https://brokeaid.com/)
  - [Xen Orchestra](https://xen-orchestra.com/docs/)
- - [XCP-ng](https://github.com/xcp-ng/xcp/wiki)
+ - [XCP-ng](https://xcp-ng.org/docs/)

docs/linux.md

@@ -35,7 +35,7 @@ Enter 'help' for a list of built-in commands.
 
 / #
 ```
-**Note:** If your ICX7xxx series switch asks for a root password, it's `wYbRaMWrYIJgg`
+**Note:** If your ICX7xxx series switch asks for a password, see the note at the bottom of this page
 
  Press tab twice and it'll show you all possible commands (just typing `help` will not show you all commands), there's a couple hundred, most of the utilities you'd expect including `wget`, `curl`, `vi`, and `ftpput`.
 

docs/perc.md

@@ -64,15 +64,15 @@ If it displays anything that doesn't exactly match the above choices, [contact m
 
 ## Extra: Disable ThirdPartyPCIFanResponse
 
->Warning: Use this at your own risk.  Modifying thermal settings can cause unforeseen circumstances.  If you are running your server in a warm environment, it is probably best to leave this alone.
+>Warning: Use this at your own risk.  Modifying thermal settings can cause unforeseen circumstances.  If you are running your server in a hot environment, it's probably best to leave this alone
 
-The LSI firmware is not supported by Dell.  This will cause the iDRAC to no longer keep track of the drive temperatures.  This is confirmed with the error PCI3018 in the Lifecycle Log and the fans being set to a static speed of about 30%.  The fan speed acts as a failsafe to prevent any disks from possibly overheating.
+iDRAC does not expect to see a PERC card running LSI firmware - this will cause the iDRAC to no longer see the drive temperatures. In some cases, this will cause the error PCI3018 in the Lifecycle Log, and the fans will be set to a static speed of about 30%. The fan speed acts as a failsafe to prevent any disks from possibly overheating.
 
-To correct this behavior, you can disable the "ThirdPartyPCIFanResponse" feature by using IPMItool or RACADM.  IPMItool is built into the live image so this will usually be the easiest option.  If you are no longer booted into the live image, use the RACADM option instead to disable via SSH.
+If you are affected by this and would like the fan behavior to return to normal, you can disable the `ThirdPartyPCIFanResponse` feature by using IPMItool or RACADM. IPMItool is built into the live image so this will usually be the easiest option.  If you don't want to use the Linux live ISO, you can use the RACADM option to disable it via SSH.
 
 ### Option 1: Disable ThirdPartyPCIFanResponse using IPMItool via Linux Shell
 
-IPMItool is built into the live image.  Otherwise, you will need to install IPMItool in a Linux environment first.
+IPMItool is built into the Linux live ISO in this guide. Otherwise, you will need to install IPMItool in a Linux environment first.
 
 To disable ThirdPartyPCIFanResponse, run the following command in the Linux shell:
 ```
@@ -91,7 +91,7 @@ ipmitool –I open raw 0x30 0xce 0 0x16 5 0 0 0 5 0 0 0 0
 
 ### Option 2: Disable ThirdPartyPCIFanResponse using RACADM via SSH
 
-Connect to port 22 on your iDRAC's IP address using your preferred SSH client.
+Connect to port 22 on your iDRAC's IP address using your preferred SSH client (you may need to enable SSH in the iDRAC web menu under iDRAC settings > Network > Services tab).
 
 To disable ThirdPartyPCIFanResponse, run the following command via the SSH client:
 ```
@@ -108,7 +108,7 @@ If you need to enable the feature again, run this command via the SSH client:
 racadm set system.thermalsettings.ThirdPartyPCIFanResponse 1
 ```
 
->Note: This information was collected from the Dell White Paper "Disabling a Third-Party PCIe Card Cooling Response with Dell PowerEdge Servers" which can be referenced here: https://fohdeesha.com/data/other/perc/ThirdPartyPCIFanResponse.pdf .
+>Note: The above commands were pulled from the following Dell White Paper: [Disabling a Third-Party PCIe Card Cooling Response with Dell PowerEdge Servers](https://fohdeesha.com/data/other/perc/ThirdPartyPCIFanResponse.pdf)
 
 ## Extra: Revision Info & Part Numbers
 The main difference between the B0 and D1 revisions is the D1 will link at PCIe 3.0 speeds, instead of PCIe 2.0. This will almost certainly never cause a bottleneck unless you have every SAS port on the card connected to very fast SSDs that all get hammered at the same time. Even then, you're likely to reach the card's processor limitations before the bus bandwidth limit. The difference with the *P* cards (H710P) is more cache (1GB vs 512MB), but this is totally irrelevant when running the card flashed to IT mode as the cache is not used.