NASLite Network Attached Storage

3ware hardware raid controler,with 4 seagate 500 Mb HD, fail to mount after months of working witout a problem.
BIOS did not show any problems.Raid is working and hard drives are present.
i would hate to loose a data.

Does NASLite fail to mount the array after attempting to check the volume? If so how much RAM is in the system?

BTW, 4x500 in RAID-0 is pretty gutsy. That's almost asking for trouble

Yes,NASLite fail to mount the array after attempting to check the volume.
I'm thinking about -check and repair-option.
There is a 1 Gb of memory and more storage.
There is 4 Gb of total storage

1G of RAM is sufficient. Yes, check and repair is the next step. If you are in no rush, then checking for bad blocks is a good idea. With your 2TB volume, it willtake some time, literally, but is worth the trouble since that’s the only way you can identify bad areas in the media.

If you prefer to be cautious, you can use the RO check option and see what errors are reported prior to launching the check and repair. In any case, check and repair is your next definitive step.

I’m not sure what you meant by “4G more storage”, but I’d assume it irrelevant at this point. You should be able to use the NAS by safely accessing other storage during the check and repair process.

Another thing to look at is the reason for the problem. Did it happen after a reboot, power outage, or else what was the cause for the glitch. Make sure you have sufficient power for all devices in the server. Inadequate power can destroy your data so make sure the PS is capable of driving everything.

Of course I meant 4 TB of storage
Total of 8 -500 Gb drives
Im in the proccess of -check and repair- it does take a long time.
All I did was shutdown of Naslite last night.
Today my Raid 0 did not mount.
PS is 500W

When shutting the NAS down (something I do nightly) I take care to shutdown any machine which may have accessed any file at any time on the NAS - *before* I shut the NAS down. I have had instances in the recent past where I had to check & repair my 1.25TB array for no apparent reason - put it down to Windows and sloppy file handling (again, by Windows). Oh, and I couldn't check & repair with only 256MB onboard - I needed 512MB for that size of drive (it did the bad block check no problem with 256MB (in 10 hours.....) then failed with a memory allocation error on the inode bit).

Check and Repair finished in about 7 hrs.Everything seems to be back to normal.Array mounted after restart as normal. All files are where they were before
Thanks for tips everyone

All:

I've occasionally had the same symptom as NickC ... and as he says ... it's most likely Windows doing sloppy file handling. I only shutdown once in a while (as much as 30 days of uptime), but when I do, everything else is either already off or purposely powered down first.

Georg