Re: Fsck Error with Snap 1000
Thanks for the info.
I check the original drive it has 3.4.805 on it. I am going to get a new image of the drive tonight and the apply it to the 500gb drive. Then check to see if that all works. I ran the fsck from the gui and that is when I got the error. It could not allocate the memory it needed and the put the drive in an unknow state. I want it to be able to run it without errors. I don't want to put data on it and then have it lock up on me some time down the road.
I tried with the maxtor drive the Master/CS jumpers. As I read in another thread, Maxtor seem to want to stay in 133 ATA. I was looking for a utility to force it down to see if that works.
All I ever get from the drive is the drive light on and the double blink of the system light. I left it like that for a day but it never got any better. I assume that is it some issue with the drive.
I will let you know if things work with the 3.4.805 or if I need to find another hard drive. I am looking at a 320 seagate. I have seen that they have been used on other snaps and working.
Again thanks for the info I will continue to play and see what happens.
|