Greetings: Interesting I did not receive an email showing that somebody posted on this thread. Anyway, I stopped by and found your post.
Here is an interesting thing, I have a 250GB ATA100 in my unit. ATA100 or PATA100 is what you should use in these units and the SnapOS is limited to approx 1TB.
I've never had anything larger then a 250GB in my 1000, but I've seen many post and units on ebay with larger hard drives. I've seen one 1000 with a 750GB ATA100 hard drive in it and it worked. There is a utility I believe that will change the Maxtor from EIDE ATA133 to ATA100, but I'll have to look to find this program to see if I have it. Let me check to make sure it is the correct program.
If the hard drive goes or you put it in to a fsck command via the webgui it will take sometime to complete. What I would do is run mfg. util and quik zero out the hard drive then run spinrite on HD then load the SnapOS image again.
I had the same problem with my 250GB HD and what saved mine(I believe) was going from the 3.4.805 image and then loaded the newest image 4.0.860 rebooted...it took 2hrs to run the fsck and came back with errors. Then, it told me to run via the webgui "Repair all errors (Warning: repairing severe errors may result in the loss of disk data.)"
After selecting this and rebooting again...and taking another 2hrs or so it came back and corrected the problem on the hard drive. So, I don't know which event fixed the problem here. Either the upgrade did it or I just got lucky. It's hard to recreate this event because I don't have control over the errors on the hard drive. Personally, I'd like to know how to turn the fsck OFF. And I'll tell you why, if there is an error then you still have access to your files and can back them up. If there are some files that don't copy because of the errors on the hard drive then that would be ok for me. Because the end result is if fsck finds an error and if it cannot correct it...you have NO access to ANY of your files and loose it ALL.
The 500GB(ATA100) should work, but if you are woried about errors on the platters then run Spinrite and it will flag the bad sectors not to be used by the SnapOS. You still have the problem of the fsck auto checking the hard drive and if with time it finds bad one(sector) then the same thing might happen. That's why I'd like to turn that option OFF. But then again it could be that the earlyer SnapOS had a bug in it and the newer image(4.0.860) might have been corrected. I don't know for sure.
bitor
Quote:
Originally Posted by cliff_stokes
Well I tried with a 3.4.805 image.
The disk formatted and look ok.
I then ran the fsck on the disk to see if I would get the same error.
I did. I ran out of memory.
I guess that I am going to have to look for a smaller drive.
Thanks for the help and information.
Cliff
|