[j-nsp] Booting from alternate media

[Javier Gallardo (DF/TEM)]

Hi,

Yes, I will try to get a new flash and do some tests rebooting the router as Leon suggest.

Thanks all for your help.
> Javier Gallardo 
 

-----Original Message-----
From: Matt Yaklin [mailto:myaklin at g4.net] 
Sent: Miércoles, 23 de Noviembre de 2005 10:39 a.m.
To: Javier Gallardo (DF/TEM)
Cc: 'InterXS - L. Croese'; Javier Gallardo Córdova; juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] Booting from alternate media



On Wed, 23 Nov 2005, Javier Gallardo (DF/TEM) wrote:

> 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?.

Would it not be easier to see if a new sans disk flash card works?
Thus eliminating your router hardware and pointing all the blame to the flash.

m

>
> 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
>