Link to home
Start Free TrialLog in
Avatar of Xetroximyn
XetroximynFlag for United States of America

asked on

chkdsk Volume bitmap is incorrect/MFT bitmap attribute incorrect - SBS 2008

It appears there are some chkdsk errors... this is an old SBS 2008 server... already EOL, we are planning to replace first thing 2019.  

This server has some critical files on it (Accounting, HR, etc)

I am a bit nervous to run the chkdsk /f due to risk of data loss/problems/it running for days... etc... but of course I realize there must be risk running with these errors.

Curious if anyone has any input on how bad these errors might be (given that it does atleast say 0 bad sectors)

See screenshots for details

thanks!
1.png
2.png
ASKER CERTIFIED SOLUTION
Avatar of Dr. Klahn
Dr. Klahn

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Is everything up to date? Windows sp1 or sp2?
You can try the hotfix for the bug microsoft identified.
https://support.microsoft.com/en-ca/help/976329/error-message-when-you-run-the-chkdsk-exe-utility-in-read-only-mode-on
if your MFT is incorrect, you can have troubles accessing your files.
here's how to repair the MFT with testdisk :  https://www.cgsecurity.org/wiki/Advanced_NTFS_Boot_and_MFT_Repair
here a way with easus :  https://www.easeus.com/format-recovery/fix-corrupt-master-file-table-error-without-losing-data.html
Avatar of Xetroximyn

ASKER

Thanks!

@Dr. Klahn - with these not appearing to be major issues - how safe/risky do you think it is to ignore this and just run the server for another 2-3 months until we replace it?  (particularly weighted against the risk of downtime of a day or more, if anything goes wrong with trying to fix it and then having to revert to backups, which I would _hope_ will restore it bare metal just fine, but I don't really trust Acronis all that much these days.  

@joinaunion I believe it should be up to date. It says Windows Server Standard FE SP2 (is Windows Server Standard FE another way to say SBS?  This is an SBS 2008 server) - I checked out the link you posted... a bit confused - I see it says "A hotfix is available for the following operating systems:"... but I don't at a glance see exactly how to check if i have the hotfix installed.  Any tips on how to check that?  


@nobus Do those tools work with SBS 2008 (Looked like the easus one mentioned win 7/8/10)
whty should they not work?  give any reason?
whty should they not work?  give any reason?

To answer your question - A large amount of software these days does not support SBS 2008.  (or Vista, the closest desktop equivalent)

The easues page specifically mentions Win 7/8/10 and does not mention Vista/SBS 2008.  In most cases, I have found that if something specifically mentions versions and does not mention Vista/SBS2008 it won't run.

One recent example I ran into.... Veeam Windows agent even says it will run on "2008 R2 SP1 or later" - BUT - their support team warned me, and they were right, that it will NOT run on SBS 2008.
well- i must say i have no experience  with SDS 2008, so i'd say  : try it
take testdisk first
Thanks @nobus!  


@Dr. Klahn - with these not appearing to be major issues - how safe/risky do you think it is to ignore this and just run the server for another 2-3 months until we replace it?  (particularly weighted against the risk of downtime of a day or more, if anything goes wrong with trying to fix it and then having to revert to backups, which I would _hope_ will restore it bare metal just fine, but I don't really trust Acronis all that much these days.  

@joinaunion I believe it should be up to date. It says Windows Server Standard FE SP2 (is Windows Server Standard FE another way to say SBS?  This is an SBS 2008 server) - I checked out the link you posted... a bit confused - I see it says "A hotfix is available for the following operating systems:"... but I don't at a glance see exactly how to check if i have the hotfix installed.  Any tips on how to check that?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks @Dr. Klahn.  So this drive is actually a raid array... and I don't have spare hardware I could try to clone the raid array to.  (And as of now I only have acronis to try to do that, because Veeam will not work with SBS 2008)....

Any ideas?

If the main concern is stuff being marked used that is not, I'm not worried... that other way around thing though... is that likely?  that it could think something is free that is actually allocated, and thus wind up overwriting something?  

And to confirm - are you saying the risk both ways is hard to say?  (i.e. both the risk of just leaving it AND the risk of running an offline chkdsk /r /f)
Look for Volsnap.sys and check the version and date.
@joinaunion - thanks - see attached screenshot
volsnap.png
What make is the hdd?
Have you run manufacturer diagnostics on the drive in question?
@joinaunion The HDD is in a Dell server - it's whatever came with it... it's in a RAID array though... can you still run SMART diagnostics on a disk in a raid array?  (I vaguely thought that the raid controller abstracts away the individual disks in the array and just presents the OS the array as if it were a single disk... do I misunderstand that?)
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I have not yet.  This is an important server and we are in the middle of our busy season.  We normally don't do anything unless absolutely critical during this time... that's why I am so torn... I don't want to NOT act and that cause a problem... I also don't want to act, and then wind up with a machine that wont boot (and resorting to trying to do bare metal restores) and/or running some test/scan that might take who knows how long, that shouldn't be interrupted once it starts.
Can it be done after hours? I think the diagnostics can take up to 1 hour.
The only other option is to ignore the  error and carry on.
Are they planning on getting a new server?
If it definitely wont take a super long time or have risk - I suppose it could be done after hours... (chkdsk though I hear stories of it taking hours and hours... even over a day... I think anyway... it was a long time ago)

After hours is not long here... midnight to 8am

Yea - plan is to get new server ASAP 2019.   That's why I am so on the fence about risk... it seems to be running OK... I just need about 2-3 more months out of it.
The test I refer to is not chkdsk. It's built in Dell diagnostics.
Thanks! - Cool - so you think it is safe to assume it won't take more than an hour and it doesn't risk causing further damage?
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Split:
-- 'Dr. Klahn' (https:#a42725172)
-- 'Dr. Klahn' (https:#a42725582)
-- 'joinaunion' (https:#a42726550)


If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer