Tony wrote:
IDE is CPU-driven and as such can get messy in the event of a processor failure. The good thing is that on reboot, the OS is clean and should perform as expected.
With a 200G drive, time can vary a lot based on number of files, CPU speed and available RAM, however the 16 hours you are describing (in email) is excessive. If the HD LED is on, then the system is still checking, or perhaps stuck checking. It is also possible that the board logic is damaged as well, but that is less likely.
One thing you can do is boot a live distro (Knopix, Slax, Ubuntu, etc.) and check the drives manually. That will give you the feedback you are looking for. NASLite is incapable of launching services until the drives are properly mounted and the services properly configured per the available storage resources.
Hope that helps.
Tony,
Thanks. That helps a lot - knew I could count on you. Does your last sentence answer the question about telnet not being available? In other words, are the logs not reachable until the filesystems are mounted?
I just got a copy of RIPLinux - I'll try that and see.