error writing fat table for volume netware Abercrombie North Dakota

Address Wahpeton, Wahpeton, ND 58075
Phone (701) 640-6547
Website Link

error writing fat table for volume netware Abercrombie, North Dakota

For details go to and find 2916958. The new system works fine most of the time, but every few days, the server spits out a few dozen error messages saying "unable to write to netware partition", or something Artikel-ID: SLN49097 Datum der letzten Änderung: 11/14/2010 12:00 AM Diesen Artikel bewerten Präzise Nützlich Leicht verständlich War dieser Artikel hilfreich? This is a discussion on [SOLVED] Netware Server errors Need Help!

Exiting the server is impossible since DOS is unable to load COMMAND.COM. I think I did check the mirroring status once and found it appeared normal, but can't remember now for sure. By joining you are opting in to receive e-mail. However, recently they've been consistantly getting the message "Error writing fat table for volume COX1/MAIN1" and I'm not sure I know what it means or how to fix it.

Join our community for more solutions or to ask questions. disclaimer The Origin of this information may be internal or external to Novell. Images and Photos Web Graphics Software How to Manage Your Email Notifications Video by: Kline Want to pick and choose which updates you receive? cause File compression starts taking files that have not been accessed for a long period of time and pulls them in memory, compresses them then writes them back to disk.

Remove Advertisements Sponsored Links Advertisement 04-21-2008, 07:42 AM #2 johnwill Microsoft MVP Join Date: Sep 2002 Location: S.E. Mein KontoSucheMapsYouTubePlayNewsGmailDriveKalenderGoogle+ÜbersetzerFotosMehrShoppingDocsBooksBloggerKontakteHangoutsNoch mehr von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Careers Vendor This error may have been caused by a hard disk or channel failure. KB 3181988 will not instal W7 64...

Get 1:1 Help Now Advertise Here Enjoyed your answer? However, the information provided in this document is for your information only. All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission. To determine if the physical size of the drive is exceeded, perform the following steps: Power the system on and press the + keys at the same time when

Experts Exchange Miscellaneous Advertise Here 769 members asked questions and received personalized solutions in the past 7 days. However, my hardware vendor have not confirm what is the problem yet. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We Then we got 7 of error writing to the directory on .../Sys. Recently, I upgraded the server.

If you only have 16MB of RAM for 4G worth of disk I would check that out. Time to upgrade. 04-23-2008, 12:18 PM #4 johnwill Microsoft MVP Join Date: Sep 2002 Location: S.E. Given that you have to turn the box on and off to get it to work, and it works ok after that, I would suspect drive controller or drive failure. Feedback enthält ungültige Zeichen, nicht angenommene Sonderzeichen: <> (, ) \ Feedback senden Derzeit ist kein Zugriff auf das Feedbacksystem möglich.

Covered by US Patent. NDS corruption, unknown objects appear in the tree. Are you using ISADISK.DSK or IDE.DSK? 0 Message Author Comment by:DarkCobra1997-11-12 Saar2: Tried running VREPAIR, it found no problems. let's help one another, not hinder.

Solved Error Writing FAT table Posted on 2000-01-05 Novell Netware 1 Verified Solution 7 Comments 932 Views Last Modified: 2007-10-18 My Novell server has been encountering this error message - 2329:Error Featured Post What Security Threats Are You Missing? Feel free to check out this quick video on how to manage your email notifications. Suggested Solutions Title # Comments Views Activity Novell DNS in conjunction with Microsott DNS 3 268 1575d GroupWise 6.5.7 Webaccess not load (Page Fault) 5 768 1067d Novell CNE now top

Connect with top rated Experts 10 Experts available now in Live! Novell IDE mirroring requires one and only one drive per standard IDE channel. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. This kept repeating so I had to manually power the server down as it was locked.

Your error most likely stems from a flaky new IDE drive that wasn't part of the P66's former life. If you see the error writing FAT Table to volume sys, this indicates a hardware failure. Pennsylvania, US Posts: 51,044 OS: Windows 7, XP-Pro, Vista, Linux My System Well, it sounds like you've had a disk crash, so I'd be unlimbering your backups and possibly shopping for fact Novell NetWare 5.1 Novell NetWare 5.0 Novell NetWare 4.2 Novell NetWare 4.11 Formerly TID 2940651 symptom Error Writing FAT Table on Volume SYS.

Consult your product manuals for complete trademark information. fix Troubleshoot the hardware by swapping Hard Drives, Controllers, Memory, or Cables. Join our community for more solutions or to ask questions. Select Modify disk partitions and Hot Fix and press the key.

If the master drive of a master/slave pair dies, the slave commits hara-kiri. I tried to run VREPAIR but it said I had to unmount the volumes which I did not do as we need it back up. When you say all attempts to access drives fail, can you still access monitor from the server ? That's from Novell Documentation.

In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. thread75-515469 Forum Search FAQs Links MVPs Why is SYS Vol dismounting? This is more than an inconvenience as it often causes the loss of work in progress for my users. If the Total is less that 50% of the original then there's your problem. 0 Message Expert Comment by:lsergio1997-12-10 I had like problem but with newest SCSI disks.