1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

NSLU2 wierd problems with scandisk

Discussion in 'Cisco/Linksys Network Storage Devices' started by Sbelew, Sep 16, 2005.

  1. Sbelew

    Sbelew Network Guru Member

    I have 2 NSLU2's on my network, both running the v2.3R63 firmware. Unit A has 2 hard drives connected to it, unit B has 1.
    Unit A is set to run a daily scandisk of both drives, right before scheduled backups. Since going to this latest firmware, I check the log, Unit A will have run a scandisk on disk 2, no information at all in the log on disk 1. When I check the scandisk setting under the ADVANCED/DISK tab, it is set to do a scandisk of disk 1. I will change it back to run scandisk on both disks, save it and the next day, same problem. Unit B is also set to do a scandisk of disk 1, since there is only 1 disk connected to it. When I check the logs on this one, It says repeatedly that scandisk failed on disk 2. There is no disk 2. and states nothing at all about disk 1. The backups scheduled on both units run fine without a hitch. I also have both units set to do a restart 5 minutes before the scandisks and backups are scheduled to run.
    Also, the email alerts still don't work. Does anyone have any suggestion or ideas on what to do here? I upgraded to this version of the firmware for the FTP functions, which work fine once I figured out to forward the port in the router.
  2. d__l

    d__l Network Guru Member

    Have you actually watched the unit go through the automated sequence of restart, and then the scan disk? I mean does an NSLU2 actually scandisk disk 1 and not report it in the log or is it really skipping the scandisk of disk 1?
  3. Sbelew

    Sbelew Network Guru Member

    No, I haven't actually watched it. They are set to start the processes at 2:30am and 6:30am. What i am going by is the log files.
  4. d__l

    d__l Network Guru Member

    I tried to duplicate your sequence of an automated restart, a scandisk, and then run a backup job while I watched. My NSLU2 seemed to become stuck in the scandisk operation or at least it lasted much longer than a manually started scandisk and much longer than I had time to wait. Also there didn't seem to be any disk activity, so I terminated the scandisk with a powerdown. The stop button wouldn't do it.

    The log said that the scheduled backup job was skipped because the scandisk was in progress at its start time.

    My results are completely different than yours, but it might be worth while to schedule a run of your sequence of NSLU2 operations at a time when you can watch its progress. Frankly the R63 firmware is so fraught with bugs and quirks, that I wouldn't trust it to do anything scheduled without at least a practice run through before hand during a time it could be watched.
  5. Sbelew

    Sbelew Network Guru Member

    Thank you for trying, seems you confirmed my original thoughts that there are problems with this firmware. Not sure what to do about it though as I use the FTP abilities of this firmware. Guess I can manually run the scandisk periodically and wait for Linksys to fix these problems and create some more. I still have not been able to get the email alerts working either which should have reported me these problems. I had to go in a read the logs to see what is going on.
    Again, thank you for your time in trying to duplicate this scenario.


Share This Page