Pro/Forums - View Single Post

cliff_stokes · 01-05-2009, 08:39 PM

Everything was working right with the larger hard drive. However I wanted to have the system checked out before I started to put any data on it.
So I set it to reboot and run the fsck. That is when I started to get the errors saying that it could not get enough free memory to store the i-nodes in ram. Needed about 3 meg more.

I tried to turn off several services to see if that would add more memory but that did not work.

I tried to set the mode of the fsck with the debug command to have it work in a slower way but still run. There is a flag to do in it swap mode but that did not work either.

I then tried to install a smaller drive that I had. 200 gig, but that was a maxtor and it had problems. I get the disk light on and the double blink. I assume it is the issue with the type of drive. I have read that they don't like maxtor's. 133's. I am going to get the original drive and see what version of software is on it. If it is still 3.4.805 then I am going to retry it. And see if that will work.

I know there used to be a utility that maxtor had to change the UDMA speed of the drive. Do you know where it might be found. I can't find in on maxtor's site since they were bought by seagate.

I have been running 4.0.830 with the 40 gig drive and have had no problems.

I have been running it without the cover in a cold room. Spare bedroom. I got the green drive to help with heat but I will look into changing the flow through the drive.

Again thanks for any suggestions. I have been lurking around here for a while reading everything that I can so I don't ask dumb questions that have already been answered.

01-05-2009, 08:39 PM	#5
cliff_stokes Cooling Neophyte Join Date: Jan 2009 Location: Michigan Posts: 19	Re: Fsck Error with Snap 1000 Everything was working right with the larger hard drive. However I wanted to have the system checked out before I started to put any data on it. So I set it to reboot and run the fsck. That is when I started to get the errors saying that it could not get enough free memory to store the i-nodes in ram. Needed about 3 meg more. I tried to turn off several services to see if that would add more memory but that did not work. I tried to set the mode of the fsck with the debug command to have it work in a slower way but still run. There is a flag to do in it swap mode but that did not work either. I then tried to install a smaller drive that I had. 200 gig, but that was a maxtor and it had problems. I get the disk light on and the double blink. I assume it is the issue with the type of drive. I have read that they don't like maxtor's. 133's. I am going to get the original drive and see what version of software is on it. If it is still 3.4.805 then I am going to retry it. And see if that will work. I know there used to be a utility that maxtor had to change the UDMA speed of the drive. Do you know where it might be found. I can't find in on maxtor's site since they were bought by seagate. I have been running 4.0.830 with the 40 gig drive and have had no problems. I have been running it without the cover in a cold room. Spare bedroom. I got the green drive to help with heat but I will look into changing the flow through the drive. Again thanks for any suggestions. I have been lurking around here for a while reading everything that I can so I don't ask dumb questions that have already been answered.