Syslog-message : <3>Oct 19 09:25:55 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>> One will see one time or continuous flooding of the logs on cRPD
Oct 19 21:25:56 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 19 21:25:56 kernel: ata2.00: irq_stat 0x40000001
Oct 19 21:25:56 kernel: ata2.00: failed command: READ DMA
Oct 19 21:25:56 kernel: ata2.00: cmd c8/00:20:00:00:00/00:00:00:00:00/e0 tag 26 dma 16384 in\x0a res 53/10:00:00:00:00/00:00:00:00:00/00 Emask 0x81 (invalid argument)
Oct 19 21:25:56 kernel: ata2.00: status: { DRDY SENSE ERR }
Oct 19 21:25:56 kernel: ata2.00: error: { IDNF }
Oct 19 21:25:56 kernel: ata2.00: configured for UDMA/133
Oct 19 21:25:56 kernel: sd 1:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 19 21:25:56 kernel: sd 1:0:0:0: [sda] tag#26 Add. Sense: Logical block address out of range
Oct 19 21:25:56 kernel: sd 1:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 00 00 00 00 00 00 20 00
Oct 19 21:25:56 kernel: blk_update_request: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Oct 19 21:25:56 kernel: ata2: EH complete
>> Later it continued on 20th, 21st and 22nd Oct.
Oct 20 09:25:58 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 21 09:26:23 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 21 09:26:24 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 22 21:26:28 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>> These logs are related to SSD issue which generally gets reset after hardware reboot.
>> As this is CRPD and not actual junos hardware. These logs are indicating there is some issue with SSD on physical hardware on which these cprd are running.
>> There must be some more crpd or software running on same hardware, these log messages is not related to CRPD and more on the physical hardware on which crpd is running.
>> Please ask customer to check on physical hardware.