This article explains an issue where srx goes down and does not boot up.
Device will go down and will get stuck in boot process. Logs from the console will show SSD corruption errors or DMA write failure as shown below:
Booting `Juniper Linux' Loading Linux ... error: no suitable video mode found. Booting in blind mode setpci: Unable to parse filter -s Invalid function number. Try `setpci --help' for more information. Cannot get kernel page_offset_base symbol address VMHost crash kernel loaded at reserved memory ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000001 ata5.00: failed command: WRITE DMA ata5.00: cmd ca/00:01:e1:f5:05/00:00:00:00:00/e0 tag 4 dma 512 out res 71/40:00:e1:f5:05/00:00:00:00:00/60 Emask 0x9 (media error) ata5.00: status: { DRDY DF ERR } ata5.00: error: { UNC } blk_update_request: I/O error, dev sda, sector 390625 Buffer I/O error on dev sda2, logical block 1, lost async page write ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000001 ata5.00: failed command: WRITE DMA ata5.00: cmd ca/00:02:40:05:06/00:00:00:00:00/e0 tag 7 dma 1024 out res 71/40:00:40:05:06/00:00:00:00:00/60 Emask 0x9 (media error) ata5.00: status: { DRDY DF ERR } ata5.00: error: { UNC } blk_update_request: I/O error, dev sda, sector 390625 Buffer I/O error on dev sda2, logical block 1, lost async page write ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000001 ata5.00: failed command: WRITE DMA ata5.00: cmd ca/00:02:40:05:06/00:00:00:00:00/e0 tag 7 dma 1024 out res 71/40:00:40:05:06/00:00:00:00:00/60 Emask 0x9 (media error) ata5.00: status: { DRDY DF ERR } ata5.00: error: { UNC } blk_update_request: I/O error, dev sda, sector 394560 Buffer I/O error on dev sda2, logical block 3936, lost async page write Buffer I/O error on dev sda2, logical block 3937, lost async page write Current Boot: Boot0000* HDD00 (Micron_5100_MTFDDAV960TCB) detected current boot medium.. ssd starting version 230 setpci: Unable to parse filter -s Invalid function number. Try `setpci --help' for more information. Mounting boot device LABEL=LINUX-BOOT
This can happen due to SSD corruption on the device. You can use the bootable USB to re-image the device, as explained in the below given kb to recover the device:
https://supportportal.juniper.net/s/article/SRX1500-How-to-install-SRX1500-from-USB-using-an-install-media-image
If this does not help to recover the device than you can proceed with the replacement of the device.