Groo

I'm just trying to set it up and I'm getting the same error when I start.

just an update, I was able to use the drive as parity disk, no issues at all, was able to re-use my old parity in the array.

Closing this, there's no solution here. The drive is a Seagate Exos 2x14 Mach 2, Dual-actuator drive. It's simply not supported in Unraid. However, it may work if in a ZFS pool.

2 days of heavy I/O on the same drive and no errors or issues. gonna try and upgrade to the latest beta, then next step will be to roll back to 7.0.1. homer-diagnostics-20250905-2010.zip

It's weird, I switched the disk to a different port. (this is a supermicro MB with a SAS backplane). I cleared the disk and added it again, unraid did a clear and gave me the option to format the drive. When I tried to format, it took the drive offline again. I'm currently doing a full preclear with a pre-read right now. What's weird is that I was able to write to it fully, it wasn't until I added it to the array and formatted it that it failed. This is the 2nd time it's happened. I don't believe that there is a connectivity issue with the drive, it feels like the array is reading something incorrectly. This is a Seagate Exos 2x14 Mach 2. Once the pre-clear has completed, I'll send a new diagnostic file. It would be strange if there were no disconnection issues during a full read/write cycle, but only when the array tries to access the drive. homer-diagnostics-20250903-2056.zip

bought a new 14tb drive and added it to my server. Pre-cleared, then stopped the array and added the new drive. When I tried to write to it, it spit out these errors: [134070.932535] unraidd7: attempt to access beyond end of device sdj: rw=0, sector=23622320272, nr_sectors = 8 limit=0 [134070.932536] md: disk7 read error, sector=23622320208 [134070.932537] unraidd7: attempt to access beyond end of device and failed the drive. I did a rebuild and everything completed successfully, once I tried to access the drive, I got the same errrors. Any clue what's going on? homer-diagnostics-20250830-2333.zip

Haven't rebooted yet, just in case there was information that would be lost. Hoping that a reboot will solve everything. Haven't seen an error similar before and have been running unraid on this hardware for a few years.

Haven't rebooted yet. This can't be good. Any help would be appreciated. homer-diagnostics-20231210-2047.zip

I'm getting very high cpu usage and IO wait when I try to download to my cache drive. system load skyrockets and download speed drops from 100mb/s to 5-10k/s. I have my dockers and download folder on a BTRFS cluster of 2 cache drives. I originally thought it was the sonarr process of moving the files to the array that was killing things, but this is happening well before the download completes. Prior to this, I have had no issues downloading at full speed. load shows: 15:14:41 up 16 days, 1:20, 1 user, load average: 9.05, 6.95, 3.65 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT root pts/0 10.0.1.154 14:57 1.00s 0.01s 0.00s w I've seen load hit 25+ over the past few days when I download larger files iotop is showing me: Total DISK READ : 0.00 B/s | Total DISK WRITE : 94.77 K/s Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 54.18 M/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 17449 be/4 root 0.00 B/s 0.00 B/s 0.00 % 99.99 % shfs /mnt/user -disks 1023 -o noatime,allow_other -o remember=330 15101 be/4 root 0.00 B/s 0.00 B/s 0.00 % 86.57 % [kworker/u32:10+btrfs-worker] 19429 be/4 root 0.00 B/s 14.58 K/s 0.00 % 6.41 % shfs /mnt/user -disks 1023 -o noatime,allow_other -o remember=330 26760 be/4 root 0.00 B/s 72.90 K/s 0.00 % 0.00 % [kworker/u32:5-bond0] 18835 be/4 root 0.00 B/s 7.29 K/s 0.00 % 0.00 % shfs /mnt/user -disks 1023 -o noatime,allow_other -o remember=330 Was going to try and remove a cache drive and switch to a single ssd as a next step? homer-diagnostics-20220109-1513.zip

ok, stopped array, and restarted in maintenance mode. Ran a (successful) repair on the unmountable disk (had to use -L) and started the array. It appears to be happy. Thanks for your help! homer-diagnostics-20211214-1037.zip

# smartctl -H /dev/sdm -d sat smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Looks promising, but already have a replacement, so I'd rather not trust this disk. How do I identify which md device refers to my unmountable disk?

it looks good, no lost+found

is it possible that after it rebuilt the party on the new drive, the file system just needs to be repaired and it will be good? i.e. the array is healthy, but the filesystem on that particular disk isn't. i.e. if I run xfs_repair on the unmountable disk, it should recover?

The disk in slot 1 is the new drive that appears to have been rebuilt, but shows up as unmountable. The old drive is mounted on /mnt/temp after I ran an xfs_check -L # xfs_repair -L /dev/sdm1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... sb_fdblocks 500481120, counted 500481113 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 data fork in ino 4298782893 claims free block 805568742 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:3286931) is ahead of log (1:2). Format log to cycle 4. done