""Important: During the file system check the volume will be inaccessible and apps running on it will stop. “”
What exactly does this mean, in a practical sense, when using the NAS primary to connect to its LUN?
We use the NAS primarily for the iSCSI LUN. Will this LUN become read-only or inaccessible when the file system check is running?
Its a 25TB LUN, and i cant afford it being inaccessible or read-only for more than a weekend.
NAS model TS-673
Firmware Version/Build numbers 4.4.2.1320 Build 20200529
Network Setup (ie Single Port or Port Trunking) Simple
Drive Configuration: RAID 5
Number of drives 6
Drive Manufacturer WDC (all 6)
Drive Model: WD60EFRX-68MYMN1 (5x), WD60EFPX-68C5ZN0 (1x)
Probably not directly related, but a number of the files and folders on the LUN wont open anymore, but thats been going on for a while.
File system check will disable all storage services (SMB/NFS?ISCSI/etc) while it runs. Did you NAS lose power or why is a check needed (make sure you have your NAS on a UPS)
If you ISCSI block storage is corrupted you have to resort to your backups, the NAS no knowledge of the content of the block storage device.
Thank you for responding.
It lost power multiple times over the years. I rarely login to that NAS’ webinterface so I’m not 100% sure thats when the filesystem-not-clean warning started.
Is there any way to estimate how long the filesystem check would take?
Its 6x 6TB drives, and a 27TB volume.
So I imagine it might take multiple days to do the filesystem check, and I cant have the LUN be down for more then a weekend.
Is there any way for me to estimate how long it will take?
It probably depends partly on what, if anything, is found during the check and the overall condition of the drives. I have 5x10TB in RAID 5 and it takes a few hours at most although I’ve only had to run it a handful of times.
This is where having a secondary NAS comes in handy - particularly if you have done snapshot replicas to that second NAS. You can restore those snapshots to that NAS and keep yourself up and running with all your data while the first one is recovering.