This article describes the steps to be taken when the device fails to boot up during boot-up process (reboot or power-cycle) / format install.
The below error logs would be seen during the boot-up process on console :
t='/dev/ram0'
rootfs=''
fstype='ramfs'
initdebug=''
NEWROOT='/sysroot'
ata5: COMRESET failed (errno=-16)
ata5: reset failed, giving up
Unpacking root filesystem....
873236 blocks
Mounted root filesystem on /dev/ram0
Switching to newStarting udev: [ OK ]
ERROR: expected SATA disks not found or not disk type.
ERROR: Only found /dev/sda.
ERROR: System cannot proceed without the disks
####################################################
ERROR: Halting the system ....
Entering non-interactive startup
Sending all processes the TERM signal... [ OK ]
Sending all processes the KILL signal... [ OK ]
Saving random seed: [ OK ]
Syncing hardware clock to system time [ OK ]
init: Re-executitmc-fpga: TMC FPGA driver shutdown called.
ng /sbin/init
Halting system...
Power down.
As per the above logs, the error message ata5: COMRESET failed (errno=-16) indicates that the system is unable to reset the SATA disk 1. This error message is usually caused by a disk failure or a loose connection between the disk and the motherboard.
The switch attempted to reset ATA channel 5 but ultimately failed and decided to give up and since not finding the expected SATA disks, the system decides to halt.
There are number of reasons for SSD to fail and few of the reason could be due to Controller failure [SSD controller manages data storage and retrieval. If it fails, the SSD may become inaccessible] and other possible could be due to corrupted firmware on SSD itself.
The device ends up in RMA, as it doesn't complete the boot process.
2024-09-13 : Article Created