[j-nsp] Booting from alternate media

[Hannes Gredler]

Javier Gallardo Córdova wrote:
> 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?.
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1. start a shell

2. become superuser

% su

3. issue the following sysctl command

root at gasherbrum2% sysctl -w machdep.bootdevs=pcmcia-flash,compact-flash,disk,lan

---

it looks like that your flash is broken - pls RMA your RE;

/hannes