[j-nsp] Booting from alternate media

[Harry Reynolds]

There is a hidden command that can be used to diagnose RE related memory issues. This command is hidden because it may disrupt normal RE activities and should be used in non-production environments or under advise of jtac:

lab at foo> request chassis routing-engine diagnostics ?
Possible completions:
  <[Enter]>            Execute this command
  all                  Run all diagnostics
  compact-flash        Run compact flash diagnostics
  hard-disk            Run hard disk diagnostics
  memory               Run memory diagnostics
  |                    Pipe through a command

Note that you are likely to find that the CF has been removed from the boot device listing, and as such you may get a "device not found" or similar error. There is a way to add the CF back to the boost listing with sysctl at a root shell, but I would wager that the CF is bad, which is why you see the log entries and boot from alternative media. IOW, you will need to RMA the RE.

HTHs


 

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> Javier Gallardo (DF/TEM)
> Sent: Wednesday, November 23, 2005 8:04 AM
> To: 'InterXS - L. Croese'; Javier Gallardo Córdova; 
> juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] Booting from alternate media
> 
> Hi Leon,
> 
> I will try to do your suggest when the router has low 
> traffic. Anyway, do you know how can to do extensive hw test 
> over flash drive card?.
> 
> Thanks and regards.
> //Javier
> 
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> InterXS - L. Croese
> Sent: Miércoles, 23 de Noviembre de 2005 09:44 a.m.
> To: Javier Gallardo Córdova; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Booting from alternate media
> 
> Hi Javier,
> 
> try "request system snapshot" and then "request system 
> reboot", it should boot from the flash disk then.
> 
> Leon
> 
> ----- Original Message -----
> From: "Javier Gallardo Córdova" <jagc64 at yahoo.com>
> To: <juniper-nsp at puck.nether.net>
> Sent: Wednesday, November 23, 2005 4:32 PM
> Subject: [j-nsp] Booting from alternate media
> 
> 
> Hi,
> 
>   We had a M10 router without access from console port or 
> telnet. As a remedy to get access, the router was turned off 
> and on. After to do this, router boot fro alternate media 
> (HD) instead of flash drive.
>   There are two alarm presents:
>   Alarm time               Class  Description
> 2005-11-22 17:58:11 CST  Major  compact-flash missing in Boot List
> 2005-11-22 17:58:08 CST  Minor  Boot from alternate media
> 
>   Reviewing at messages lod, I find the next lines since more 
> of ten days
> ago:
>     Nov 9 21:15:44 MEXSJCTIJA /kernel: ad0: read interrupt 
> arrived early
>   Nov 9 21:15:44 MEXSJCTIJA /kernel: ad0: read error detected 
> (too) late
>   Nov 9 21:15:44 MEXSJCTIJA /kernel: ad0 removed from the Boot List
>   Nov 9 21:15:45 MEXSJCTIJA alarmd[2293]: Alarm set: RE 
> color=YELLOW, class=CHASSIS, reason=compact-flash drive error
>   Nov 9 21:15:50 MEXSJCTIJA feb CM: ALARM SET: (Minor) Slot 
> 0: compact-flash drive error
> 
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ad0: timeout waiting for DRQ
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: - resetting
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ad0: enabling readahead 
> cache failed
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0-master: timeout 
> waiting to give command=ef s=d0 e=04
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ad0: enabling write cache failed
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0-master: timeout 
> waiting to give command=ef s=d0 e=04
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0-slave: timeout 
> waiting to give
> command=c6 s=d0 e=04
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ad1: set multi features failed
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0-slave: timeout 
> waiting to give command=ef s=d0 e=04
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ad1: enabling readahead 
> cache failed
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0-slave: timeout 
> waiting to give command=ef s=d0 e=04
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ad1: enabling write cache failed
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0-slave: DMA limited 
> to UDMA33
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0-slave: timeout 
> waiting to give command=ef s=d0 e=04
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0-slave: timeout 
> waiting to give command=ef s=d0 e=04
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ad0: timeout waiting for DRQ
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: - resetting
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0: resetting devices ..
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ata0: Finished 
> resetting devices .. 
> (after 1 seconds)
>   Nov 11 21:35:59 MEXSJCTIJA /kernel: ad0: timeout waiting for DRQ
>   Nov 22 17:20:15 MEXSJCTIJA /kernel: ad0: not attached, 
> missing in Boot List
> 
>   Do you know how can do extensive hardware tests over flash 
> drive in order to diagnose if it have a uncorrectable  HW 
> failure?. And, how reincorporate flash drive to boot list?.
> 
>   Thanks and regards.
>   //Javier
> 
> 
> __________________________________________________
> Correo Yahoo!
> Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
> Regístrate ya - http://correo.espanol.yahoo.com/ 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>