highgear

Ok running a correcting check now. I've run a number of parity checks since running XFS repair on disk 6 FYI.

Manually I believe. Since then I've run a check via the GUI that came up clean. I've also had parity checks with no errors since then.

Hello all, I just had a scheduled non-correcting parity check finish up that returned a fairly large number of errors in the GUI, around 800. I'm not aware of any unclean shutdowns recently. All my disks look ok to me as far as SMART data. I did have some filesystem corruption on a disk a while back that I thought was fixed with XFS repair (disk 6). What's the best course of action at this point? I'm attaching my diagnostics. I haven't shutdown the server since the parity check FYI. Thanks in advance for the help. tower-diagnostics-20231205-0924.zip

Thanks for the help everyone. I ran xfs_repair on my other disks and everything looked good.

Ok thanks for explaining. So what command do you recommend using first? Just -n? Run this on all drives in maintenance mode, even parity? Thanks again.

Ok I am using ECC so good to know. No unclean shutdowns in at least 3-4 months. I thought as long as parity checks came back ok everything was fine? What would I look for in the storage subsystem? Thanks

Gotcha that's what I thought. How can I prevent this in the future? This is the second time I've lost a significant amount of data due to filesystem corruption. I recently swapped to all new SATA cables but I suppose the damage could have already occurred. I use a Supermicro mb and a solid Seasonic PSU w/ server grade RAM. Should I run memtest?

Ok thanks. Unfortunately no backup for the media files. If I pulled the disk and did a rebuild from parity what would happen?

Thanks! Ok that ran and completed without any errors. Now that disk has 1.2+TB free whereas before I'd guess it only had <200gb free. There's also a bunch of files in a new lost+found folder. Should I continue using this disk? Is there anything I can do to recover the lost files assuming I don't have a backup of this disk? Anything I should do moving forward to prevent this?

Ok thanks. I just tried to run xfs_repair within the GUI using the -v command and got this error after a bit: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 33370936 bytes) in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(693) : eval()'d code on line 895

@JorgeB Ok I rebooted and grabbed new diagnostics. After I rebooted, Disk 6 says "Unmountable: Wrong or no file system". tower-diagnostics-20230426-0843.zip

Hello, I noticed the other day that a number of my media files were inaccessible within Plex. I investigated and found that these certain files no longer showed at all within the media folder. After looking into it I found that disk6 shows in midnight commander in red as "?disk6" and when I click on it I get a message saying "Cannot read directory contents". All the other disks appear to be functioning normally. Does this mean that disk6 is corrupted? What could have caused this/what can be done to prevent it in the future? If so, am I able to remove the drive and rebuild using parity data on a new or even the same disk to recover my files? If the disk is corrupted, why would the disk still show as normal/green from within Unraid? Thanks for the help any and all assistance is appreciated! I've attached my diagnostics I just pulled. Edit: I reviewed the logs and I keep seeing these repeated, among other errors: emhttpd: error: get_fs_sizes, 6081: Input/output error (5): statfs: /mnt/user/downloads sys_disk_free: VFS disk_free failed. Error was : Input/output error smbd[25122]: chdir_current_service: vfs_ChDir(/mnt/user/Hyperspin) failed: Input/output error. I'm thinking I need to run xfs_repair on disk6 but I want to confirm there's nothing I should do first. If I need to run xfs_repair, I should be using this command correct? xfs_repair -v /dev/md6 tower-diagnostics-20230425-1300.zip

Ok thanks that makes sense. Ok cool I’ll stop that in the future. Chugging along at 160MB now so looking good. Thanks for the help everyone.

Thanks. I'm now seeing it cycle between 30-90ish MB/sec. tower-diagnostics-20230213-1146.zip

Ok sounds good, thanks! Rebuilding onto the drive now. I'm currently only getting speeds of around 50 MB/sec on the rebuild though. Docker is disabled and there shouldn't be any other reads/writes happening that I'm aware of. For parity checks I normally get 100MB+ speeds. Any thoughts? Thanks yeah I have plenty of extra space currently but my allocation settings are a bit wonky and always fill my drives up more than I'd like. What's a reasonable amount of minimum free space on each drive you like to see?