Thank you - the more that I’ve fought with it, I’m at the same conclusion. I’ll try one of those out from your suggestion.
From: Job Snijders <j...@instituut.net> Date: Friday, March 8, 2024 at 12:23 PM To: Paulhamus, Jon <jpaulha...@iu17.org> Cc: juniper-nsp@puck.nether.net <juniper-nsp@puck.nether.net> Subject: Re: [j-nsp] SRX345 Boot Problem On Fri, Mar 08, 2024 at 05:06:37PM +0000, Paulhamus, Jon via juniper-nsp wrote: > I have an issue with an SRX345 that will not boot as the internal OS > is corrupted. I created a USB recovery stick from another SRX345 and > can successfully boot from it. When trying to write to the external > USB stick to the internal storage using this command, the device > crashes. > > request system snapshot media internal > > Clearing current label... > Partitioning internal media (/dev/da0) ... > xhci0: ERROR! xhci_timeout: transfer timeout, id 62. > 0x801778d4+0x124 (0xc6c88800,0xc6cd5050,0x58801e03,0x13c0301) ra 0x80178c00 > sz 64 > 0x80178b28+0xd8 (0xc6c88800,0xc6cd5050,0x58801e03,0x13c0301) ra 0x8017a750 sz > 64 > 0x8017a4b0+0x2a0 (0xc6c88800,0xc6cd5050,0x58801e03,0x13c0301) ra 0x80ac582c > sz 32 > mips_handle_this_interrupt+0x8c (0xc6c88800,0xc6cd5050,0x58801e03,0x13c0301) > ra 0x80ac58b8 sz 40 > mips_handle_interrupts+0x58 (0xc6c88800,0xc6cd5050,0x58801e03,0x13c0301) ra > 0x80ac5d64 sz 48 > mips_interrupt+0x2ac (0xc6c88800,0xc6cd5050,0x58801e03,0x13c0301) ra > 0x80e625e4 sz 32 > MipsKernIntr+0x140 (0x80f90000,0x812d2820,0xffff8010,0xffff8010) ra > 0x80ac3804 sz 368 > cpu_idle+0x10 (0x80f90000,0x812d2820,0xffff8010,0xffff8010) ra 0x80205fa0 sz > 24 > 0x80205d94+0x20c (0x80f90000,0x812d2820,0xffff8010,0xffff8010) ra 0x8020052c > sz 48 > fork_exit+0x258 (0x80f90000,0x812d2820,0xffff8010,0xffff8010) ra 0x80e632e0 > sz 48 > MipsNMIException+0x30 (0x80f90000,0x812d2820,0xffff8010,0xffff8010) ra 0 sz 0 > pid 25, process: idle: cpu0 > cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode) > badvaddr = 0x1010, pc = 0x801779f8, ra = 0x80178c00, sr = 0x508008a3 > panic: trap > cpuid = 0 > KDB: stack backtrace: > SP 0: not in kernel > 0+0x0 (0,0,0,0) ra 0 sz 0 > pid 25, process: idle: cpu0 > > Can anyone provide a way to try and get this going again? I suspect the device's NAND memory storage is broken, causing the system to panic. Maybe something like this can serve as replacement? https://www.ebay.com/itm/234083615969 Kind regards, Job _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
