Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Check for CompactFlash Card and Hard Disk Failure

    If the Routing Engine has a CompactFlash card failure, the router boots from the hard disk. When you log in to the router, the CLI will indicate that the router has booted from alternate media.

    If the Routing Engine has a hard drive failure, the router boots from the CompactFlash card as usual. However, the router cannot write to the hard drive.

    1. When the CompactFlash Card Is Removed from the Boot List
    2. Determine Why CompactFlash Card Did Not Mount
    3. When the Hard Disk Is Removed from the Boot List
    4. Verify That the Hard Disk Did Not Mount
    5. Verify That the Hard Disk Is Missing from The Boot List
    6. View Alarms When Media Is Removed from the Boot List

    When the CompactFlash Card Is Removed from the Boot List

    Problem

    You can have a CompactFlash card error when conditions, such as a HARD READ error occurs. When the CompactFlash card is removed from the boot list, the following message displays you log in to the router:

    Solution

    login: user
    --- JUNOS 6.0R1.6 built 2003-09-24 04:06:27 UTC
    ---
    --- NOTICE: System is running on alternate media device     (/dev/ad1s1a).
    ---
    
    user@host>
    

    Check to see which file system is mounted by using the following :

    user@host> show system storage
    user@host> show system storage
    Filesystem        512-blocks       Used      Avail Capacity Mounted on
    /dev/ad1s1a           218690      56502     144694     28%  /
    devfs                     32         32          0    100%  /dev/
    /dev/vn0               18316      18316          0    100%  /packages/mnt/jbase
    devfs                     32         32          0    100%  /dev/
    /dev/vn1               45448      45448          0    100% /packages/mnt/jkernel-6.0R1.6
    /dev/vn2               20532      20532          0    100%  /packages/mnt/jpfe-M160-6.0R1.6
    /dev/vn3                3580       3580          0    100%  /packages/mnt/jdocs-6.0R1.6
    /dev/vn4               20728      20728          0    100%  /packages/mnt/jroute-6.0R1.6
    /dev/vn5                9256       9256          0    100%  /packages/mnt/jcrypto-6.0R1.6
    mfs:139              4064278          2    3739134      0%  /tmp
    /dev/ad1s1e            24234          4      22292      0%  /config
    procfs                     8          8          0    100%  /proc
    /dev/ad1s1f         52492630    7988510   40304710     17%  /var
    

    The command output will not show ad0 (the CompactFlash card) mounted, but instead, ad1 (the hard disk) has the root file system mounted.

    Determine Why CompactFlash Card Did Not Mount

    Problem

    To determine why the CompactFlash card did not get mounted, use the following command:

    user@host> show system boot-messages | match "ad0|ad1"
    user@host> show system boot-messages | match "ad0|ad1"
    ad0: not attached, missing in Boot List
    ad1: 28615MB <FUJITSU MHS2030AT> [58140/16/63] at ata0-slave using BIOSDMA Mounting root from ufs:/dev/ad1s1a
    

    Solution

    The command output shows that the CompactFlash card (ad0) was removed from the boot list.

    When the Hard Disk Is Removed from the Boot List

    Problem

    The following boot messages list on the console shows symptoms that signify a hard disk failure. These messages are not in the boot-messages log file.

    /dev/ad1s1f: CAN'T CHECK FILE SYSTEM.
    /dev/ad1s1f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    Can't open /dev/ad1s1f: Device not configured
    WARNING:
    WARNING: /var mount failed, building emergency /var
    WARNING:
    dumpon: sysctl: kern.dumpdev: Device not configured
    mgd: commit complete
    dumpon: sysctl: kern.dumpdev: Device not configured
    mgd: commit complete
    

    Solution

    The boot messages show that the hard disk (ad1) was removed from the boot list (using Junos OS, Release 6.1R1.4).

    Verify That the Hard Disk Did Not Mount

    Problem

    To verify that the hard disk (ad1) did not get mounted, use the following command:

    user@host> show system storage

    The following sample output was taken from a RE-333 Routing Engine.

    user@host> show system storage
    Filesystem        512-blocks       Used      Avail Capacity Mounted on
    /dev/ad0s1a           218690      60294     140902     30%  /
    devfs                     32         32          0    100%  /dev/
    /dev/vn0               20044      20044          0    100%  /packages/mnt/jbase
    devfs                     32         32          0    100%  /dev/
    /dev/vn1               51920      51920          0    100%  /packages/mnt/jkernel-6.1R1.4
    /dev/vn2               22328      22328          0    100%  /packages/mnt/jpfe-M160-6.1R1.4
    /dev/vn3                3844       3844          0    100%  /packages/mnt/jdocs-6.1R1.4
    /dev/vn4               23328      23328          0    100%  /packages/mnt/jroute-6.1R1.4
    /dev/vn5                8820       8820          0    100%  /packages/mnt/jcrypto-6.1R1.4
    mfs:139               127006      16914      99932     14%  /tmp
    /dev/ad0s1e            24234         28      22268      0%  /config
    procfs                     8          8          0    100%  /proc
    

    Solution

    The command shows that the hard disk (ad1) is not mounted. Instead, /var now exists only in the swap partition (mfs:139), so any contents saved to /var will not be saved at the next reboot.

    user@host> start shell
    user@host% ls -l /
    total 47
    -rw-r--r--  1 root  wheel  4735 Mar 31  2001 COPYRIGHT
    dr-xr-xr-x  2 root  wheel   512 Jan 20  2004 altconfig
    dr-xr-xr-x  2 root  wheel   512 Jan 20  2004 altroot
    drwxr-xr-x  2 root  wheel   512 Dec 29 12:00 bin
    dr-xr-xr-x  3 root  wheel   512 Feb  4 23:16 boot
    drwxr-xr-x  3 root  wheel   512 Feb  3 18:08 config
    dr-xr-xr-x  4 root  wheel  2084 Feb  4 23:18 dev dr-xr-xr-x  7 root  wheel  1536 Feb  4 23:19 etc
    lrwxr-xr-x  1 root  wheel    17 Dec 29 12:02 kernel -> /packages/jkernel
    dr-xr-xr-x  2 root  wheel   512 Jan 20  2004 mnt
    drwxr-xr-x  2 root  wheel   512 Feb  3 21:16 modules
    drwxr-xr-x  3 root  wheel  1536 Feb  3 21:19 packages
    dr-xr-xr-x  1 root  wheel   512 Feb  4 23:29 proc
    dr-xr-xr-x  2 root  wheel   512 Feb  3 21:15 root
    dr-xr-xr-x  3 root  wheel  1536 Feb  3 21:15 sbin
    drwxrwxrwt  3 root  wheel   512 Feb  4 23:19 tmp
    dr-xr-xr-x  8 root  wheel   512 Dec 29 12:00 usr
    lrwxr-xr-x  1 root  wheel     8 Feb  4 23:18 var -> /tmp/var
    

    The example shows that var has a symbolic link to the /tmp/var directory. It resides under the /tmp/var directory, and is mounted on the mfs partition.

    Verify That the Hard Disk Is Missing from The Boot List

    Problem

    To verify that the hard disk (ad1) is missing from the boot list, use the following command:

    user@host> show system boot-messages | match "ad0|ad1"
    user@host> show system boot-messages | match "ad0|ad1"
    ad0: 122MB <SanDisk SDCFB-128> [980/8/32] at ata0-master using PIO4
    ad1: not attached, missing in Boot List
    Mounting root from ufs:/dev/ad0s1a
    

    Solution

    The device is taken out of the boot list because of an error condition, such as a HARD READ errror.

    View Alarms When Media Is Removed from the Boot List

    Problem

    To display an alarm that is generated when media (CompactFlash card or hard disk) is removed from the boot list, use the following command:

    user@host> show chassis alarms
    user@host> show chassis alarms
    1 alarms currently active
    Alarm time               Class  Description
    2005-02-04 23:19:27 CET  Major  hard-disk missing in Boot List
    

    Solution

    When the router is operational and the hard disk is removed from the boot list, a minor yellow alarm is generated. When the router is rebooted and the hard disk is still removed from the boot list, a red major alarm is generated.

    The command output displays a major alarm indicating what media is missing from the boot list and the time and date when the event occurred.

    Published: 2012-08-20