Author Topic: WXC-250 Disk1:Error  (Read 5806 times)

dapurwin

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
WXC-250 Disk1:Error
« on: March 05, 2008, 01:18:21 pm »
If anyone has encountered a red X on their hard disk in the WEB UI on their WXC, it may not necessarily mean your hard disk is bad.  Run the code below.  After reboot, if the Red X is still there, your disk is bad and most likely you will have to get another device from Juniper (RMA).

http://home.comcast.net/~purwin/Disk_Error.gif


Code: [Select]
copy cfg/startup.cfg protect.ovr
rm cfg/disk_status.txt
reboot -no-resync

JintsFan

  • Newbie
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Re: WXC-250 Disk1:Error
« Reply #1 on: March 20, 2008, 08:38:19 pm »
Not 100% accurate:

SSH to the box and enter the following commands

# copy cfg/startup.cfg protect.ovr
# rm cfg/disk_status.txt

Then perform a clean reboot This is very important.

ajacob

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: WXC-250 Disk1:Error
« Reply #2 on: August 13, 2009, 09:53:48 am »
I agree that the commands need to be performed via telnet/ssh, but in the original post:
copy cfg/startup.cfg protect.ovr
rm cfg/disk_status.txt
reboot -no-resync

the "reboot -no-resync" command at the end accomplishes the clean reboot.

You can see this if you access via SSH and put in reboot vs reboot -no-resync
********
XXX (WXC-250A)# reboot
You are about to reboot system immediately.
Are you sure? yes/no n
The system will not be rebooted
XXX (WXC-250A)# reboot -no-resync
You are about to reboot system immediately.
The disk-based compression dictionary will be deleted.
Are you sure? yes/no
********
notice the second command informs the user that the compression dictionary will be deleted.

Also, here's more information on this error:
When the device detects a problem with the disk, it marks it bad. The status is stored in the disk_status.txt. There isn’t a way to clear it. The disk_status.txt is a hidden and protected file in the cfg directory. The workaround starts by removing “file protection” by adding the protect.ovr. Then, you can delete the disk_status.txt. We hope that by performing a clean reboot, the system will clear up any software related problems. Upon reboot, the protect.ovr is automatically removed and file protection is back on.

If the error returns, then the drive is truly bad and you will need to open a case with Juniper to RMA the device or hard drive.
This is the information needed by Juniper to perform the RMA:

***************************************
 Contact Name: 
 Contact E-mail: 
 Contact Phone: 
 ***************************************
 Shipping Address:
 
 
 ***************************************
 Device Type: 
 Serial Number of WX:
 ***************************************
 Reason for return:
 
 
 Date of Failure
 ****************************************