Fixing file system corruption on Synology NAS

I recently recycled my hard-drives on my Synology DS1010+ as one of the drives started to fail. Migration of the drives was easy, but I did notice that I had file-system corruption when looking at dmesg:

htree_dirblock_to_tree: bad entry in directory
Multiply-claimed block(s) in inode

The Synology does not have a facility to check the file-system during boot up, and the following instructions will allow you to run a file-system repair (if possible, make a backup of critical files before):

1. Make sure that you have SSH enabled and log into the Synology via SSH
2. Shutdown all services except SSH (this will unmount the volume):

   syno_poweroff_task -d

3. Enable the volume:

   vgchange -ay

4. Check for errors, but do not fix:

   e2fsck -nvf -C 0 /dev/vg1/lv

5. Try to fix the file-system errors

   e2fsck -pvf -C 0 /dev/vg1/lv

6. If -pvf can’t work, use -yvf instead.

   e2fsck -yvf -C 0 /dev/vg1/lv

7. Reboot the Synology

 

---

🍺 Pay it forward: If any of my content helped you in any way, then follow me on Twitter or send me some coins:

(CRO)    cro1w2kvwrzp23aq54n3amwav4yy4a9ahq2kz2wtmj (Memo: 644996249) or 0xb83c3Fe378F5224fAdD7a0f8a7dD33a6C96C422C (Cronos)
(USDC)   0xb83c3Fe378F5224fAdD7a0f8a7dD33a6C96C422C
(BTC)    3628nqihXvw2RXsKtTR36dN6WvYzaHyr52
(ETH)    0xb83c3Fe378F5224fAdD7a0f8a7dD33a6C96C422C
(BAT)    0xb83c3Fe378F5224fAdD7a0f8a7dD33a6C96C422C
(LTC)    MQxRAfhVU84KDVUqnZ5eV9MGyyaBEcQeDf
(Ripple) rKV8HEL3vLc6q9waTiJcewdRdSFyx67QFb (Tag: 1172047832)
(XLM)    GB67TJFJO3GUA432EJ4JTODHFYSBTM44P4XQCDOFTXJNNPV2UKUJYVBF (Memo ID: 1406379394)

🚀 Use my referral link https://crypto.com/app/ref6ayzqvp to sign up for Crypto.com and we both get $25 USD 😸

🧨 During signup use my referral code ref6ayzqvp to claim your reward 🧨
Go to Curve.com to add your Crypto.com card to ApplePay (get 1% cashback)