The device might become unstable and might or might not be able to generate logs during the outage. You may notice the below logs in console output:
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20031
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20159
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20191
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20447
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20703
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20735
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20831
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20863
ad1: FAILURE - WRITE_DMA status=41<READY,ERROR> error=4<ABORTED> LBA=20895
This syslog message is generated under the following circumstances:
A hardware fault occurs on the hard drive OR
Communication between the hard drive and the kernel or the Routing Engine (RE) and the main board fails.
In VC-Setup, DMA failure errors might also be seen when the cache flush or the cache is full. It might cause the device not to accept SSH credentials and Virtual-Chassis to go into the hang state.PR for reference - https://prsearch.juniper.net/problemreport/PR13836081. If you have access to the device and you are able to run the commands on the console, please try the below to confirm issue with the hard disk or the software. Please ensure you have root access while using shell prompt. If it is a software issue, we can move to step 3.KB13103 [juniper.net] -- [Junos] How to perform SMART test from the shellhttps://supportportal.juniper.net/s/article/Junos-How-to-perform-SMART-test-from-the-shell