SSD Drive replacement process
Step 1) Confirm the drive is missing
On the Dashboard GUI the Disk status will no longer be “GOOD”.
And the disk status will look similar to below:
Notice “SSD 0” is missing from the list here.
NOTE: depending on which drive is faulty the drive name may be different.
Step 2) Locate the Serial number of faulty disk
Edit the file in:
/opt/fmadio/etc/disk.lua
And locate the line of the faulty disk, in this case “ssd0”, the value on the left is the Serial number of the drive:
fmadio@fmadio100v2-228U:/opt/fmadio/etc$ cat disk.lua | grep ssd0
["201727D219C2"] = "ssd0",
fmadio@fmadio100v2-228U:/opt/fmadio/etc$
In this case the faulty drive serial number is “201727D219C2”.
Step 3) Power down and replace the Faulty drive
Power down the system using the following command:
sudo poweroff
Wait for the system to power off.
Then locate the faulty drive by the serial number on the drive from Step 2)
Replace the faulty drive with a new drive.
Step 4) Power on
Power on the system.
This can be done physically by pressing the power button on the device, or remotely powering on the system using the IPMI interface.
Step 5) Update the Serial number of new Drive
Get a list of all drives on the system by running the following command:
devblk_info.lua
The output will look something like the following:
fmadio@fmadio100v2-228U:~$ devblk_info.lua
fmad fmadlua Sep 7 2024 (/opt/fmadio/bin/fmadiolua /opt/fmadio/bin/devblk_info.lua )
calibrating...
0 : 2095067842 2.0951 cycles/nsec offset:4.932 Mhz
Cycles/Sec 2095067842.0000 Std: 0 cycle std( 0.00000000) Target:2.10 Ghz
ls: /sys/block/sd*: No such file or directory
nvme0n1 0000:86:00.0 nvme0n1 0x1344 1949256760C6 os0
nvme5n1 0000:b0:00.0 nvme5n1 0x1344 201727D219C1
nvme6n1 0000:d8:00.0 nvme6n1 0x1344 20182802A6ED ssd1
nvme7n1 0000:d9:00.0 nvme7n1 0x1344 201727D21F9E ssd2
nvme8n1 0000:da:00.0 nvme8n1 0x1344 20182802A712 ssd3
nvme4n1 0000:af:00.0 nvme4n1 0x1344 21032D02D9F3 ssd4
nvme2n1 0000:88:00.0 nvme2n1 0x1344 20182802AA97 ssd5
nvme3n1 0000:89:00.0 nvme3n1 0x1344 201727D21AD5 ssd6
nvme1n1 0000:87:00.0 nvme1n1 0x1344 201727D21ED2 ssd7
nvme9n1 0000:db:00.0 nvme9n1 0x1344 201527CB05CA par0
Total Devices: 0
done 0.053198Sec 0.000887Min
fmadio@fmadio100v2-228U:~$
In this case a drive mapping is missing from one of the drives:
This indicates the system has not allocated a logical drive mapping for that serial number. In this case the serial number is “201727D219C1" which is the newly added drive.
Step 6) Update the disk configuration
Edit the following file with nano or vi:
/opt/fmadio/etc/disk.lua
Locate the line where the faulty drive (in this case its under “ssd0”).
Replace the serial number with the one obtained in Step 5).
Save the file.
Step 7) Confirm new mapping is correct
After saving the file in Step 6) run the same command to confirm the drive is good:
devblk_info.lua
Example output below, all drives should have a logical mapping:
fmadio@fmadio100v2-228U:/opt/fmadio/etc$ devblk_info.lua
fmad fmadlua Sep 7 2024 (/opt/fmadio/bin/fmadiolua /opt/fmadio/bin/devblk_info.lua )
nvme0n1 0000:86:00.0 nvme0n1 0x1344 1949256760C6 os0
nvme5n1 0000:b0:00.0 nvme5n1 0x1344 201727D219C1 ssd0
nvme6n1 0000:d8:00.0 nvme6n1 0x1344 20182802A6ED ssd1
nvme7n1 0000:d9:00.0 nvme7n1 0x1344 201727D21F9E ssd2
nvme8n1 0000:da:00.0 nvme8n1 0x1344 20182802A712 ssd3
nvme4n1 0000:af:00.0 nvme4n1 0x1344 21032D02D9F3 ssd4
nvme2n1 0000:88:00.0 nvme2n1 0x1344 20182802AA97 ssd5
nvme3n1 0000:89:00.0 nvme3n1 0x1344 201727D21AD5 ssd6
nvme1n1 0000:87:00.0 nvme1n1 0x1344 201727D21ED2 ssd7
nvme9n1 0000:db:00.0 nvme9n1 0x1344 201527CB05CA par0
fmadio@fmadio100v2-228U:/opt/fmadio/etc$
Step 8) Reboot and confirm
Reboot the system with the following command:
sudo reboot
Wait for the system to reboot and come back. It typically takes 1-3 minutes for the reboot to complete.
The Web GUI should be “GOOD” with all status showing GREEN as shown below:
Step 9) Quick Format
We recommended doing a quick format after disk replacement. This is the fastest (5min) and quickest way to get the system back up and operational.
If you require data recovery and rebuild, please contact support to walk you thru the process.