![]() | ||
|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
![]() |
Thread Tools |
![]() |
#1 |
Cooling Neophyte
Join Date: May 2007
Location: CA
Posts: 14
|
![]()
E File System Check : FSCK fatal error = 8 Disk 10000
E File System Check : Failed to allocate 3798204 bytes for i-node cache buffers!!! Disk 10000 W File System Check : partition is NOT clean. Disk 10000 I File System Check : Executing fsck /dev/ride0a /force /fix /fixfatal Disk 10000 I'm sure you've run into this before, but I need some help... I have 2 Snap 1000 units with 500g HDs, working fine until the other day.... I cannot see the share and the disk utility shows the above errors..... Any help?? Thanks |
![]() |
![]() |
![]() |
#2 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
I hope you have a copy of the boot tracks to reload if the HD goes south.
If you have a copy of spinrite, I would pull the unit and let it check the HD for errors. Have seen a few of those. And they seam not to go away. Making me wonder if it's a problem with the big HD's every one using these day. But your under the OS limit. Do not do power cycles till it thinks it fixed and comes up. It took one user over 7 days if I recall for the unit to come back on line with a 4x00. How many users accessing the server?
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
#3 |
Cooling Neophyte
Join Date: May 2007
Location: CA
Posts: 14
|
![]()
I do have a copy of spinrite somewhere....
I only have 3 computers being served.. What would you suggest is the best way to use spinrite?? Thanks |
![]() |
![]() |
![]() |
#4 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
You will need to remove the HD from the 1000 and install in your pc. You must boot from the SpinRite CD. If it you boot from windows, it will try to setup the HD and all is lost. So just remove your main windows HD so that does not happen. Now if spinrite hangs in the 5% area your HD is toast. This is where they fail if its a non-recoverable. Run spintite in maintance mode. It will switch to recovery when it detects a pproblem.
Once it has finished use DD and copy the first 30meg of the HD, instruction in the wiki section. Then you will have the OS and can reload a new HD if needed. Now some of the later 1000 use a different set of files than the early ones. So it's possiable that the OS you get may not boot a 1000v2. So you may want to get a copy of all boot tracks just incase you have a later one. Which is the same one used on a 2200. If by chance these are a eary 1000v1, the OS may be in flash ram. If this is the case you only need to install a new/clean HD.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
#5 |
Cooling Neophyte
Join Date: Jan 2009
Location: Michigan
Posts: 19
|
![]()
I had the same issue trying to use a 500 gb drive in a snap 1000.
The device has only 32 megs of memory. as you can see it is asking for 37 meg File System Check : Failed to allocate 3798204 bytes for i-node cache buffers!!! Disk 10000 The device does not have enough memory to do the FSChK. It does a FSChK every so often or on boot up. The only way I know to get it to read the drive is to put it in a box with more memory. if you have a 1100 you might put it in there and have it run the fschk and flag the drive good and then put it back in the 1000. however this event will happen again if it ever needs to run fschk again. From most of the people upgrading their boxes have gone to 320 gb. I would try a smaller drive and force it to run fschk on it to see if you can get it to run. If you don't need the data on the drive you can have it reformat and then try again but I was never able to get it to run with a 500 gb drive. So I gave up. I did not want to get in that problem where I might lose data because of that issue. I hope that helps |
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|