NASLite Network Attached Storage

have lost a disk for some reason - its on the new neoware thing - no big deal - i have everything backed up but a couple of questions before i start again

it shows fail on the disk check - so i go to repair - starts pass 1 and it goes on for ever - it then gave a memory allocation error and told me to reboot to mount the disc - that i did but the disk showed fail again

the neoware only as 128mb - is that a problem - would i be better pulling the drive and doing it in a system with more memory

or should i just start again

Insufficient RAM. How big is the drive and how much RAM?

thanks for the reply tony

128 ram - 1 terrabyte drive [sata] - works fine when its working but fell over for no reason and then gave that error message when trying to repair

took the bull by the horns and did a reformat - but if its going to happen again then will look at alternatives - almost impossible to get more ram in

As far as my experience goes ... 128MB will run ok, but as soon as an fsck is needed the check takes too many resources on such a large disk and it can't complete. Probably a disk of around 80GB or less would be ok (that's a wild guess). Additional (much more remote) possibility is bad RAM, but even with good RAM you will run into the first problem.

thanks georg - will run a ram test - i think its ok but a test will prove it

as i said i decided to take the easy?? route and start again - the box will only take 256 and thats difficult - i guess i could have pulled the drive and repaired it in another machine with much more ram - is that possible - dont really know

as i said at the top - nothing lost - i have it backed up [twice!!] - am playing and learning at the same time

I can't tell you exactly how much RAM will be needed with the 1TB drive during an fsck. (A really really expert Linux guru might, based on number of inodes and block size ...) Even 256 may be too low. 512 should work with 500GB, and likely 1TB, but not sure.

Yes, you could let the fsck run in another machine (Ubuntu, Linux LiveCD or Naslite). Lots of learning opportunity there

thanks again georg - more interested in why it failed - i am not aware i did anything - it may have got swiched off without a proper shutdown so was not surprised it initiated a disk check - it had done that before and been fine - but i was surprised when the disk showed - FAIL

is a disk check ram dependant - i thought not