Alex.vision

I ran into problems trying to mount the new Disk 4. This was in my syslog. Aug 17 10:18:18 Media unassigned.devices: Adding disk '/dev/mapper/WDC_WD80EFZX-68UW8N0_VKGW28LX'... Aug 17 10:18:18 Media emhttpd: shcmd (69093): /usr/sbin/cryptsetup luksOpen /dev/sdab1 WDC_WD80EFZX-68UW8N0_VKGW28LX Aug 17 10:18:18 Media unassigned.devices: Mount drive command: /sbin/mount -o rw,noatime,nodiratime '/dev/mapper/WDC_WD80EFZX-68UW8N0_VKGW28LX' '/mnt/disks/WDC_WD80EFZX-68UW8N0_VKGW28LX' Aug 17 10:18:18 Media kernel: XFS (dm-28): Filesystem has duplicate UUID 55c3e94c-c28a-4132-adb2-43d2ff58c702 - can't mount Aug 17 10:18:18 Media unassigned.devices: Mount of '/dev/mapper/WDC_WD80EFZX-68UW8N0_VKGW28LX' failed: 'mount: /mnt/disks/WDC_WD80EFZX-68UW8N0_VKGW28LX: wrong fs type, bad option, bad superblock on /dev/mapper/WDC_WD80EFZX-68UW8N0_VKGW28LX, missing codepage or helper program, or other error. ' Aug 17 10:18:18 Media unassigned.devices: Partition 'WDC_WD80EFZX-68UW8N0_VKGW28LX' cannot be mounted. Looks like it can't be mounted.

OK, I will mount both drives in unassigned devices and look into their contents and try to see if it looks good.. Are you thinking I should compare the drives with something like Krusader, or should a quick look at the folder structure and layout with Midnight Commander be sufficient? I disabled SMB, Docker and VM's before starting the array as I wanted to minimize anything writing to the array. If I should use Krusader, I will need to stop the array and re-enable Docker. Thanks for all the help!!

Trurl I understand what your are saying about the parity. That makes sense. I was able to unassign disk4 and start the array. Attached in the diagnostic file and a screenshot of the array. media-diagnostics-20210817-0907.zip

No problems with the flash drive during any of this time. I think the syslog server was not running all the time that the Unraid server was, so the log is incomplete. From the timeline, I know the New Disk 4 was being built on Aug 12, but within the last say 2 hours of it being complete is when it started showing errors for Drive 1. I was monitoring the end of the rebuild closer than any other time. I want to say it had completed 98.2+ % of the rebuild before any notices about issues with Disk1 happened. So moving forward, should I tell Unraid to rebuild Disk 4 on to the new one again, hope that Disk 1 holds out, then replace Disk 1, with the new one I just ordered? or Replace Disk 1 and hope the old disk 4 holds out, then replace it? Since starting this whole thing, I have left the mover script off, I don't think I have written anything to the array but I'm not 100% sure. If I have written anything it was just some media that can be lost. Id like to minimize loosing an entire drive, but a few media files hopefully wont be missed.

Normally I have the syslog mirroring to another computer, but I don't see information in it about the rebuild during that time. I am attaching it anyways, I don't really know what Im looking for. I know this is a lot of drives for 1 parity, I was running dual parity a long time ago, but I had a backplane fry the controller on 3 data drives and one of the parity drives a while ago and I have been working on building a complete backup system for my entire array. I have offloaded about half the array onto 2 new servers that will act as a pair. I still want to make a backup of the data on this system, but with just having shelled out $2500 for my other pair I just cant afford to buy another 100TB of drives during this chia mining thing. I was hoping to make it just a little longer till prices came down. Timeline 07-03-21 Last scheduled parity check (Completed with no errors) 07-15-21 Read Errors on Disk 4 Rebuild disk 4 Pending Sector Errors Disk 4 08-08-21 Replace Disk 4 with new disk Rebuild New Disk 4 Parity Finished rebuild with 384 errors Read Errors Disk 1 Shutdown array to replace Disk 1 08-16 New Disk 1 arrives, start server to begin replacement for Disk 1 Array list places old Disk 4 in array instead of New Disk 4. Yeah I can understand not wanting to look through all those smart reports, there are a bunch of them , I don't have any other smart warnings, on the main page. Though I may have marked them as "Acknowledge" so they are not showing. I also am attaching a text file of my archive notifications that were from that time period. I do get emails as soon as a problem is detected. I don't have a complete backup of this server, it is mostly media, so I could get it all back, eventually. Though I really don't want to re-rip 100TB worth of data, ouch. (Media) - Archived Notifications.txt alex.vision syslog Aug 10-12.txt

Hey all, Recently my array had some errors with one of my disks. I had been in the process of consolidating my array using the Unbalance plugin to free up space. Though for me this was taking forever as I have a lot of SMR drives in my array. Anyways as I was moving data around I got an alert that said: Alert [MEDIA] - Disk 4 in error state (disk dsbl) ST8000AS0002-1NA17Z_Z840XT2C (sdk) This lead me down a long road of trying to rebuild parity, then deciding that I should swap the disk with a spare from another system. I replaced that drive with WDC_WD80EFZX-68UW8N0_VKGW28LX, and rebuilt the array. While rebuilding I received another error that Disk 1 a ST8000AS0002-1NA17Z_Z840X72E was also experiencing errors. The array finished the rebuild/replace for the Disk 4 failure, but we had a heat wave roll through, so before I could look into everything I shutdown the system so it wouldn't overheat. I also bought a new drive to replace Disk 1 with and it just came in. I started up the server, getting ready to replace Disk 1, when I saw that the system had tried to use my old Disk 4 ST8000AS0002-1NA17Z_Z840XT2C instead of the new Disk 4 WDC_WD80EFZX-68UW8N0_VKGW28LX. When I tried to put the correct drive that the array had rebuilt upon, Unraid said it was wrong. I didn't want to start anything with out finding out what I should do. Smart Data shows (Old Disk 4) Current pending sector 2392 Offline uncorrectable 2392 (New Disk 4) no errors (Disk 1) Reported uncorrect 7 Current pending sector 24 Offline uncorrectable 24 I have the array offline while I try to figure out what has happened. Any advise would be greatly appreciated. media-diagnostics-20210816-1407.zip

I would imagine there is no simple answer, other than to say if you can, try the discrete GPU method. I run Emby on my server with a Quadro P2200. I have it do all my transcoding instead of my Ryzen 9 3900x and it does a far superior job. I have my card split between my Emby docker and Handbrake, using the H.265 NVEnc encoder is way faster than my CPU. Though I don't often have as many concurrent streams going as you do, the card I have is newer with more VRAM. The most reliable test to see if it will work is going to be a real world test. Hope this helps.

Is this new behavior? Had the mover script been correctly moving your files in the past and just recently stopped? Do the completed downloads show in Sonarr and Radarr as being finished downloading. Do the paths show correctly in Sonarr and Radarr. In Radarr my path for my shows is \\servername\media\tv shows\ShowName Though I use a external sonarr instance, your path is is more likely to be similar to /mnt/user/sharname/showname Does the icon for the share in question show an orange triangle with an exclamation point, indicating it has files waiting to be moved from the cache?

Oh, yes that makes perfect sense. Thanks for the help, I couldn't for the life of me figure out why that share setting was not working. A seemingly hidden share with its own settings explains some of it, though it does seem strange that it wasn't showing up in the diagnostic file. If I remember correctly wasn't there a .foldername that allows hidden folders, though I don't remember if that worked with share level folders. Well thanks for helping me track this thing down. Now to complete the rest of the file transfer. -Alex

OK, I confirmed the share was still set to Fill-up, then I initiated the transfer again, but i received an error. rsync: [sender] link_stat "/mnt/user/Media/TV" failed: No such file or directory (2) rsync: [sender] change_dir "/root/Shows" failed: No such file or directory (2) I think I remember this happening last time, and I think I did change the command to what you suggested. I will change it to match your suggestion. I'm initiating the command on the destination server, should I escape both sides, of the command ie rsync --archive --dry-run --human-readable --update --rsh ssh --progress media:"/mnt/user/Media/TV\ Shows/" "/mnt/user/TV\ Shows/" Or should I add it to only one side? Source/Destination Thanks for the help Edit, I changed the command on the source only, as that was where the error was showing, and it seems to be running. It will take a while before it starts moving files. I must have use TV\ Shows on both the source and destination side of the command. So it created the extra folder on the server. Strange though that it would ignore the split-level setting though.

OK, I renamed the TV\ Shows folder on disks 1-8 to TV Shows and recomputed the share. All the files are now correctly in one folder and all show under the share.

Hmm, this is very strange, the data does appear to be only on Drive 1 according to the shares page, but if I click each disk manually and view the files I can see a share. There seems to be a folder TV Shows on Drive 1 as well as a folder TV\Shows. On all other drives there is only a TV\ Shows folder. Maybe my sync from my other server has a malformed command. Hopefully I can just log into each disk via midnight commander and move the data into the correct folder. Here is the command I used to initiate the transfer. rsync --archive --dry-run --human-readable --update --rsh ssh --progress media:"/mnt/user/Media/TV Shows/" "/mnt/user/TV Shows/" I'm not sure where I went wrong, but I know just enough to be ignorantly dangerous when it comes to the command line.

Why do I always forget the diagnostic log when asking for help? Here it is, the share is named TV Shows. media2-diagnostics-20210610-1345.zip

(Solved Edit): rsync command cause hidden share to be created that wasn't showing up under the shares tab. This hidden share must have defaulted to High-water. (Original Post): Im transferring about 84 TB to a new array. I have (9) 14TB hard drives, and (1) 14 TB Parity disk, running 6.8.2 I would like the data to fill the drives 1 by 1 to the free space limit. I have one share, set to Fill-up. Spilt level is set to Automatically split any, free space is set to 200GB. Included Disks is set to All, excluded is set to None. For some reason though my disks are filling up 1 by 1 to 50%. I thought that was what High-water would do. Am I missing something or just confused.

They all are in the same direct attach storage case with the same backplane on the same controller. I have 2 SGI Rackable 3U 16 Bay SE3016 SAS Expander Chassis. I had them daisy chained to each because I only had a single port card in my computer. I discovered while trying to preclear some new drives that they were severely bottlenecked. When I realized it would take forever I got a two port card and moved each SE3016 to its own port. For some reason when I started the array I got those errors. Now I have 9 drives that had some kind of issue. I don't think there is anything wrong with them, I think they had some communication issue when I moved to the new HBA card. They had been working for a couple of weeks daisy chained together and the unit with my main array drives has worked for years on the old single port HBA card. It wasn't until I moved to the new card that I had trouble. Now I'm trying to understand what I should do to move forward and get these drives back online. I can put the old HBA card back in but wont the drives still be Unmountable?

Hi All, I am having another problem with my system I hope I can get some help with. Currently I am on Unraid v6.8.3 (Nvidia Edition) and I have been waiting to finish my new backup system before updating to v6.9. I have purchased 10 14TB hard drives and was in the process of pre-clearing them. I have 12 8TB drives in my main case and 13 8TB drives in an external DAS case. In order to preclear then new 14TB drives I added a second DAS, daisy chained to the first one. I found that the limitations of my DAS cases are around 1,062MB/s and preclearing the drives would have taken forever. 400+ Hours plus half my array would be bottlenecked. So, I ordered a two port SFF-8088 LSI HBA to run one DAS case on each port. While I was waiting for the card to arrive, I ran preclears on 4 of the 14TB drives and paused the rest. My Idea was, I would preclear some, then pause the preclear, shutdown the system, add the new card, start the system back and resume preclearing with more bandwidth. When the card arrived, I popped it into my system and started it back up. All my drives showed up and the configuration was valid, so I started the array. Immediately I received a bunch of notifications in my browser about CRC Errors, when the page completed loading several of my drives were listed as Unmountable: No File System and my parity drive had an error. I stopped the array. I shut down the system, pulled the second DAS off and restarted the computer. I started the array in Maintenance mode and other than a red X on the parity drive, things look ok. I tried to start the array normally and it failed again with the same error. I am attaching a screenshot of my array, my diagnostic file and my syslog. I also downloaded all my drives SMART reports if needed. What should my next steps be, I hope I did not just Bork the data on 9 drives, that would be a really bad day. Main Array 1 12TB Parity Drive 23 8TB Data Drives 1 8TB Cache Drive Unassigned Devices 3 Drives in Unassigned Devices (Various Appdata Folders) 10 14TB Drives -Alex alex.vision-diagnostics-20210327-1509.zip alex.vision-syslog-20210327-2208.zip

Ok, the drive is in a DAS unit, so I can move it to another slot. I will give that a try. Thanks

This may not help because I am not 100% sure of what you need, but I use Resilio Sync for some of the plugins I need on multiple computers. With that you can set up a single share between the 2 computers, skipping Unraid. I think if you use the free version it doesn't allow selective sync options, which means the master folder will be copied in its entirety to the other computer, but this might work for you. I just have a plugins folder on my desktop that is synced on all my gaming pc's, that way any mod is just drag and drop from the folder in to the games directory. There are other methods as well if this isn't what you are looking for, this one is just really simple to implement. Hope this helps. Alex

I would recommend midnight commander as well, mainly because it does the transfer on the Unraid server. If you employ the share method and then say use a windows computer to transfer the files from share to share, it will transfer over the network i.e.. Server Share A - desktop - Server Share B which would slow everything down. If you have a lot of data to move, Midnight Commander is much more efficient. If you want to get fancier, you can install Krusader in a docker container and make the transfer there, but it sounds like your just starting out so I might skip that until you are more familiar with Unraid.

Hey Yall, I woke up to an email from my Media Unraid server: Event: Unraid array errors Subject: Warning [MEDIA] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 15 - ST8000DM004-2CX188_WCT0NR2S (sds) (errors 4) I logged into the server this morning while at work, and saw that one of the drives was marked at fault with (4) errors. Not knowing what the error was, I shutdown the server until I was home later and could diagnose. I can home and pulled the flash drive and looked at the system log. Starting at line 161 I see a kernel: nginx[6821]: segfault, followed by some TRIM status logs, then the stopping of the mover script. I see some other information that I don't understand at all, until I reach line 181. That's when I see this: Feb 26 04:45:43 Media kernel: md: disk15 read error, sector=576031088 Feb 26 04:45:43 Media kernel: md: disk15 read error, sector=576031096 Feb 26 04:45:43 Media kernel: mpt2sas_cm1: removing handle(0x000b), sas_addr(0x5001940000dd8201) Feb 26 04:45:43 Media kernel: mpt2sas_cm1: enclosure logical id(0x5001940000dd823f), slot(1) Feb 26 04:45:43 Media kernel: md: disk15 write error, sector=576031088 Feb 26 04:45:43 Media kernel: md: disk15 write error, sector=576031096 I am not sure of the difference between read errors and write errors, I think I have only ever experienced Pending Sector Count and Reallocated Sector Count errors. I honestly don't remember the last failed drive I had with Unraid, so I wanted to upload my syslog and diagnostics for some advice, should I replace this drive, could this be connection related and maybe reseating the drive in the caddy could fix it? I know this drive like all of my other ones are at between 98-99% full, I don't remember what the minimum free space was for that share, but I think it was around 20GB, and I know the mover was running right before the error but I think I was transferring 1-2GB files around. I don't think it would have filled up the drive, I don't even know if that would cause a drive error, I'm just throwing out the info. Anyways, I would appreciate any advice on this issue. Thanks for the help. -Alex Alex.vision-Media-Syslog-2021-02-26.txt media-diagnostics-20210226-0957.zip

OK, I'll put this on hold for now. Going to be out of action for the next two weeks. When I get back Ill swap all the parts with my duplicate system and see if i get the same errors. Then hopefully I can narrow down the problem, one by one. Thanks @johnnie.black for the assistance!! -Alex

Before I can change out all of the hardware to test the above hypothesis im trying to duplicate the data to another server. I strt the system and then intiate a transfer and see how much data can be pulled before it crashes. I just looked at my transfer and noticed it had stopped. So I logged into the web page, which displayed. I got three notifications about plugin updates, and when I clicked the plugins tab, the system refreshed to a blank page with the header still showing and the chrome busy icon in the tab. I quickly opened a terminal and tried to pull info from the syslog. root@Media:~# tail -f /var/log/syslog Mar 4 18:56:09 Media kernel: start_secondary+0x197/0x1b2 Mar 4 18:56:09 Media kernel: secondary_startup_64+0xa4/0xb0 Mar 4 18:56:32 Media kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Mar 4 18:56:32 Media kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 08 01 00 00 01 00 Mar 4 18:56:32 Media kernel: print_req_error: I/O error, dev sda, sector 2049 Mar 4 18:56:32 Media kernel: Buffer I/O error on dev sda1, logical block 1, lost async page write Mar 4 18:56:32 Media kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Mar 4 18:56:32 Media kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 17 91 00 00 01 00 Mar 4 18:56:32 Media kernel: print_req_error: I/O error, dev sda, sector 6033 Mar 4 18:56:32 Media kernel: Buffer I/O error on dev sda1, logical block 3985, lost async page write Mar 4 19:11:09 Media kernel: RDX: 0000000000000000 RSI: 0000000021bf5b50 RDI: 0000000000000000 Mar 4 19:11:09 Media kernel: RBP: 00000589298a6770 R08: 00000589298a6770 R09: 000000000000573e Mar 4 19:11:09 Media kernel: R10: 000000008f3bab38 R11: 071c71c71c71c71c R12: 0000000000000002 Mar 4 19:11:09 Media kernel: R13: ffffffff81e5e2a0 R14: 0000000000000000 R15: ffffffff81e5e378 Mar 4 19:11:09 Media kernel: ? cpuidle_enter_state+0xbf/0x141 Mar 4 19:11:09 Media kernel: do_idle+0x17e/0x1fc Mar 4 19:11:09 Media kernel: cpu_startup_entry+0x6a/0x6c Mar 4 19:11:09 Media kernel: start_secondary+0x197/0x1b2 Mar 4 19:11:09 Media kernel: secondary_startup_64+0xa4/0xb0 Mar 4 19:13:09 Media login[15244]: ROOT LOGIN on '/dev/pts/1' Mar 4 19:14:09 Media kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 4 19:14:09 Media kernel: rcu: 4-...0: (0 ticks this GP) idle=cd2/1/0x4000000000000000 softirq=314663/314663 fqs=814935 Mar 4 19:14:09 Media kernel: rcu: 11-...0: (2 GPs behind) idle=98e/0/0x1 softirq=365175/365176 fqs=814935 Mar 4 19:14:09 Media kernel: rcu: (detected by 8, t=3300092 jiffies, g=1434025, q=713807) Mar 4 19:14:09 Media kernel: Sending NMI from CPU 8 to CPUs 4: Mar 4 19:14:09 Media kernel: NMI backtrace for cpu 4 Mar 4 19:14:09 Media kernel: CPU: 4 PID: 15614 Comm: unraidd7 Tainted: G O 4.19.98-Unraid #1 Mar 4 19:14:09 Media kernel: Hardware name: System manufacturer System Product Name/PRIME X470-PRO, BIOS 5406 11/13/2019 Mar 4 19:14:09 Media kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x11e/0x171 Mar 4 19:14:09 Media kernel: Code: 48 03 04 cd 20 37 db 81 48 89 10 8b 42 08 85 c0 75 04 f3 90 eb f5 48 8b 0a 48 85 c9 74 c9 0f 0d 09 8b 07 66 85 c0 74 04 f3 90 <eb> f5 41 89 c0 66 45 31 c0 44 39 c6 74 0a 48 85 c9 c6 07 01 75 1b Mar 4 19:14:09 Media kernel: RSP: 0018:ffffc9000bd4fe80 EFLAGS: 00000002 Mar 4 19:14:09 Media kernel: RAX: 0000000000140101 RBX: ffffc9000bd4fec0 RCX: 0000000000000000 Mar 4 19:14:09 Media kernel: RDX: ffff88840e720740 RSI: 0000000000140000 RDI: ffff88840bfe8498 Mar 4 19:14:09 Media kernel: RBP: ffff88840bfe8498 R08: 000000000000029c R09: 0000000000000000 Mar 4 19:14:09 Media kernel: R10: 0000000000000020 R11: ffff88840e71fb40 R12: 0000000000000246 Mar 4 19:14:09 Media kernel: R13: ffff88840bfe8498 R14: ffff8883d4c81b00 R15: ffffc9000bc0faf0 Mar 4 19:14:09 Media kernel: FS: 0000000000000000(0000) GS:ffff88840e700000(0000) knlGS:0000000000000000 Mar 4 19:14:09 Media kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 4 19:14:09 Media kernel: CR2: 00001460ca2b2000 CR3: 0000000001e0a000 CR4: 0000000000340ee0 Mar 4 19:14:09 Media kernel: Call Trace: Mar 4 19:14:09 Media kernel: _raw_spin_lock_irqsave+0x29/0x31 Mar 4 19:14:09 Media kernel: prepare_to_wait_event+0x13/0xd2 Mar 4 19:14:09 Media kernel: md_thread+0x8f/0x115 [md_mod] Mar 4 19:14:09 Media kernel: ? wait_woken+0x6a/0x6a Mar 4 19:14:09 Media kernel: ? md_open+0x2c/0x2c [md_mod] Mar 4 19:14:09 Media kernel: kthread+0x10c/0x114 Mar 4 19:14:09 Media kernel: ? kthread_park+0x89/0x89 Mar 4 19:14:09 Media kernel: ret_from_fork+0x22/0x40 Mar 4 19:14:09 Media kernel: Sending NMI from CPU 8 to CPUs 11: Mar 4 19:14:09 Media kernel: NMI backtrace for cpu 11 Mar 4 19:14:09 Media kernel: CPU: 11 PID: 0 Comm: swapper/11 Tainted: G O 4.19.98-Unraid #1 Mar 4 19:14:09 Media kernel: Hardware name: System manufacturer System Product Name/PRIME X470-PRO, BIOS 5406 11/13/2019 Mar 4 19:14:09 Media kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6b/0x171 Mar 4 19:14:09 Media kernel: Code: 42 f0 8b 07 30 e4 09 c6 f7 c6 00 ff ff ff 74 0e 81 e6 00 ff 00 00 75 1a c6 47 01 00 eb 14 85 f6 74 0a 8b 07 84 c0 74 04 f3 90 <eb> f6 66 c7 07 01 00 c3 48 c7 c2 40 07 02 00 65 48 03 15 48 6d f8 Mar 4 19:14:09 Media kernel: RSP: 0018:ffff88840e8c3c80 EFLAGS: 00000002 Mar 4 19:14:09 Media kernel: RAX: 0000000000140101 RBX: ffff88840bfe8498 RCX: 0000000000000000 Mar 4 19:14:09 Media kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff88840bfe8498 Mar 4 19:14:09 Media kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: ffff88840e8c3ca0 Mar 4 19:14:09 Media kernel: R10: 0000000000000000 R11: ffff88840e71fb40 R12: 0000000000000046 Mar 4 19:14:09 Media kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Mar 4 19:14:09 Media kernel: FS: 0000000000000000(0000) GS:ffff88840e8c0000(0000) knlGS:0000000000000000 Mar 4 19:14:09 Media kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 4 19:14:09 Media kernel: CR2: 00001460ca290000 CR3: 0000000001e0a000 CR4: 0000000000340ee0 Mar 4 19:14:09 Media kernel: Call Trace: Mar 4 19:14:09 Media kernel: <IRQ> Mar 4 19:14:09 Media kernel: _raw_spin_lock_irqsave+0x29/0x31 Mar 4 19:14:09 Media kernel: __wake_up_common_lock+0x5b/0xcb Mar 4 19:14:09 Media kernel: end_request+0x178/0x18e [md_mod] Mar 4 19:14:09 Media kernel: blk_update_request+0x114/0x21e Mar 4 19:14:09 Media kernel: scsi_end_request+0x29/0x203 Mar 4 19:14:09 Media kernel: scsi_io_completion+0x27c/0x4fa Mar 4 19:14:09 Media kernel: blk_mq_complete_request+0xea/0xef Mar 4 19:14:09 Media kernel: _scsih_io_done+0x6c5/0x6d7 [mpt3sas] Mar 4 19:14:09 Media kernel: ? load_balance+0x124/0x713 Mar 4 19:14:09 Media kernel: ? __accumulate_pelt_segments+0x1d/0x2c Mar 4 19:14:09 Media kernel: ? __update_load_avg_se+0xeb/0x19c Mar 4 19:14:09 Media kernel: _base_interrupt+0x1aa/0xe0a [mpt3sas] Mar 4 19:14:09 Media kernel: __handle_irq_event_percpu+0x36/0xcb Mar 4 19:14:09 Media kernel: handle_irq_event_percpu+0x2c/0x6f Mar 4 19:14:09 Media kernel: handle_irq_event+0x34/0x51 Mar 4 19:14:09 Media kernel: handle_edge_irq+0xfc/0x11f Mar 4 19:14:09 Media kernel: handle_irq+0x1c/0x1f Mar 4 19:14:09 Media kernel: do_IRQ+0x46/0xd0 Mar 4 19:14:09 Media kernel: common_interrupt+0xf/0xf Mar 4 19:14:09 Media kernel: </IRQ> Mar 4 19:14:09 Media kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x141 Mar 4 19:14:09 Media kernel: Code: ff 45 84 f6 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 a8 8f bb ff fb 66 0f 1f 44 00 00 <48> 2b 2c 24 b8 ff ff ff 7f 48 b9 ff ff ff ff f3 01 00 00 48 39 cd Mar 4 19:14:09 Media kernel: RSP: 0018:ffffc90001a0be98 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdc Mar 4 19:14:09 Media kernel: RAX: ffff88840e8dfac0 RBX: ffff888408eb0c00 RCX: 000000000000001f Mar 4 19:14:09 Media kernel: RDX: 0000000000000000 RSI: 0000000021bf5b50 RDI: 0000000000000000 Mar 4 19:14:09 Media kernel: RBP: 00000589298a6770 R08: 00000589298a6770 R09: 000000000000573e Mar 4 19:14:09 Media kernel: R10: 000000008f3bab38 R11: 071c71c71c71c71c R12: 0000000000000002 Mar 4 19:14:09 Media kernel: R13: ffffffff81e5e2a0 R14: 0000000000000000 R15: ffffffff81e5e378 Mar 4 19:14:09 Media kernel: ? cpuidle_enter_state+0xbf/0x141 Mar 4 19:14:09 Media kernel: do_idle+0x17e/0x1fc Mar 4 19:14:09 Media kernel: cpu_startup_entry+0x6a/0x6c Mar 4 19:14:09 Media kernel: start_secondary+0x197/0x1b2 Mar 4 19:14:09 Media kernel: secondary_startup_64+0xa4/0xb0 I don't know if this helps narrow down the case of the lock up. I checked, I can still see the Overview page, but have no SMB access. I took a picture of the overview page and attached it. All information regarding the live CPU stats is frozen. Also I looked up the device listed in the errors above, sda1, sda is my flash drive. I'm at a loss for now. Thanks for the help!!

Hmm, ok, I have an Identical system, I can try swapping all my drives over to that one and try to narrow it down to hardware or hw incompatibility if that seems like a viable option.

Oh, right, I forgot about that. Sometimes it's hard to remember that your internet can go down. I have a dedicated gigabit synchronous fiber line that hasn't gone down in over a year, I forget that it is uncommon.

It may be a bit overkill, but I use Duo on a few servers, it can push a request for login authentication to your device and allow you to approve it. It also has 2FA revolving codes, but I like the seamlessness of tapping "Approve" on my smartwatch instead of getting out my device, logging into Lastpass authenticator or Google or Auth, then typing in the codes. Duo or any 2FA isn't for everyone, but my vote would be to have it at least as an option.