November 7, 20187 yr I woke up to this error yesterday. I've rebooted my unRAID box, changed where the drive is plugged in (no longer in my SAS controller, now directly connected to motherboard), still no change. I've seen a few topics about this, but I'd rather not risk losing my data. I've attached my logs. Any ideas what is causing this? tower-syslog-20181107-0851.zip
November 7, 20187 yr Community Expert Please go to Tools - Diagnostics and attach the complete diagnostics zip to your next post. Diagnostics includes syslog and many other useful things that make it a lot easier for us to get a more complete understanding. We never want just the syslog.
November 7, 20187 yr Community Expert Yes you'll have to repair the filesystem on disk3. Can you give us any more details about what might have led to this?
November 7, 20187 yr Author When you say repair the file system, what does that entail? The night before I had deleted quite a few old files. A week or so before I stopped using my unRAID as my ESXi storage, and migrated the VMs to local storage on the ESXi box. Other than that, I haven't really made any changes.
November 7, 20187 yr Community Expert 29 minutes ago, vagrantprodigy said: what does that entail? https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui or https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS
November 7, 20187 yr Author 1 hour ago, johnnie.black said: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui or https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS xfs_repair fixed it. It required the -l switch, but I'm back up and running. Thank you for your assistance.
Archived
This topic is now archived and is closed to further replies.