DEBIAN ….Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

So I’m getting corrupted error msg on my Raspberry PI:

[   48.261326] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

umount /boot
 git clone
 cd dosfstools
 ./fsck.fat -a /dev/mmcblk0p1

Get this output:

 fsck.fat 3.0.26 (2014-03-07)
 0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
 Automatically removing dirty bit.
 Performing changes.
 /dev/mmcblk0p1: 14 files, 1232/7161 clusters

And now:

 mount /boot

Troubleshooting VSS on MS Servers

First make sure that VSS is properly configured.  Go to properties/shadow copies tab on any local drive.  All drives in the list on this tab should say disabled.  Then highlight each drive in turn and make sure it is set to use limit and the limit is at the default value of 10% of the total drive space in MB.  In order for Windows to get access to this 10% there must be at least 13% free space with 15% considered minimum and 20-25% recommended.  When you are looking at the drives on the shadow copies tab you will see how much space is being used.  If no backups are running, they should all be zero.  If they show more, click settings and (after making a note of the limit) change the limit to 300 MB and click OK.  If it says zero, go back into settings and put the original number back.  If it says 300 MB, click the Create Now button below and then click the Delete Now button.  If it now says zero go back into settings and put the original (10%) number back.
Please apply suggestion 1 and 2 below.  Please note that suggestion 2 has multiple parts.

Suggestion 1: Install VSS patches

I would specifically start with these three Microsoft patches: KB940349 first, then KB967551 and finally KB975928.  Reboot as necessary.

Suggestion 2: Reset VSS configuration
If this problem continues, please perform the following steps to reset VSS

1. Go into control panel and reset the com configuration.

a. In control panel click “add remove programs”.
b. Click “Add remove windows components”.
c. Click the “Next” button (windows will re-initialize the COM configuration).

2. Look in “Component Services” MMC and make sure that the MS Shadow Copy Provider does not show up as a COM+ application. The software provider should NOT show up in Component Services on Windows 2003 and above. If it is, you will have trouble initializing the VSS coordinator and provider instances.

a. In the Component Services MMC, navigate to “Component ServicesMy ComputerCOM+ Applications”
b. View the properties of the “MS Software Shadow Copy Provider” if it exists. In the “advanced” tab, uncheck the “Disable deletion” checkbox and then delete the “MS Software Shadow Copy Provider” from COM+ Applications.

3. Run FIXVSS03.BAT to reset VSS configuration.

net stop “System Event Notification”
net stop “COM+ Event System”
net stop “Microsoft Software Shadow Copy Provider “
net stop “Volume Shadow Copy”
cd /d %windir%system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
Cd /d %systemroot%syswow64
regsvr32 /s ole32.dll
regsvr32 /s vss_ps.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml4.dll
net start “COM+ Event System”

Reboot the system to bring all writers into a stable state.

Volume Shadow Copy – good to know

Displays current volume shadow copy backups and all installed shadow copy writers and providers. The vssadmin tool is a command-line utility to interact with the VSS.


vssadmin list writers
Lists all writers in the system

vssadmin list providers
Lists all currently installed shadow copy providers

more info on MS Technet website: