MonadProxy

Thanks, it ended up coming back up by itself after a little while but I will remember this command.

Hi folks, I would like to know, is it possible to reconnect our server to unraid connect after the server lost the connection to the internet? So far as it stands, it stays like this and it seems the only way to get it back up is to register/unregister or reboot the server? Let me know if I missed something. Much thanks.

My bad I did one but I forgot about it since it's on another page. I guess all I can do is wait and hope now.

You can use the unassigned devices plugin, remove all the 3TB drives from the array but keep the data, create a new array with the 14TB drives, move all the data from the unassigned 3TB drives to the new array? Since everything is pooled together the folder structure should remain the same.

Hi folks, I found this thread from 6 years ago that mention similar things: https://forums.unraid.net/topic/89443-default-critical-disk-utilization-threshold/ That being said I would like to somehow resurrect it for other reasons: These days drives sizes can be huge, not allowing the users to use floating point values for warning thresholds on a 24TB+ drives leaves 240gb+ of space on the table. I understand that it's not a good idea to fill drives to the brim but floating point values would allow to bring this down to maybe 48-64gb which would be much more efficient. 1% these days represent a lot so setting the threshold at 99% just isn't enough. Some people recommend to just set this to 100% and ignore it but then we lose the warning feature completely which makes no sense. This may have been less important 8-10 years ago but now it will matter more and more as drive size increases This should not be a very hard change to implement as this is just changing the type of certain values that are used mostly for display and notifications. Thanks for thanking this into consideration.

Did you have Unraid connect set up by any chance? That would be the easiest way to restore the flash drive with a cloud copy to a working condition.

I just noticed something recently but I did not have time to document it with logs and I will have to wait for a power outage to happen again in order to re-create this scenario: When a power outage occurs and NUT sends the shutdown signal to the server, if the power suddenly comes back, it does not go through with the shut down and aborts it. The problem if it happens midway is that you will end up with a server that cancelled the shutdown operation, has drives that are spun down and others not, same for the containers. It would be nicer if when the shut down signal is sent by the plugin during a power outage, it would go through completely even if the power comes back during the procedure (happens a lot for regions with small outages) and leave it to the user. That way we could avoid completely having a 'half running server' that stopped it's shutdown process mid procedure and could cause other problems. Another issue I always had is also that the signal is never sent to my windows machine through WinNUT even if it says that I am connected and everything is fine and dandy but I guess that's another story for another day. Thanks in advance if someone has any clue.

Mhh curiously enough I was not asked for this before upgrading to 7.2.3 (I was on 7.2) and yes you are right I used the wrong term it is remove and not erase. That being said since that was a single drive pool that I use for scratch and the drive died, I just removed it until the replacement arrives so no worries here.

I have a pool disk that I use for my downloads pool that went down and to start the array I can't just check "Yes, I want to do this" anymore... I would have to erase that pool to use the main array and re-create it later when I get a new drive.

Ok, I went to re-read the docs and yeah I misunderstood what you had said so after I ran the check button on that specific emulated drive and it fixed itself, the second check returned no errors and I could proceed with the parity rebuild. No more unmountable or wrong filesystem messages. Thanks.

I am attempting a read check (in maintenance mode for xfs as advised) without disk 2 and if the result is okay should i re-add the disk and attempt a re-build will the unmountable message go away if the read check goes okay?

So do you mean by that if I leave disk2 unassigned, start the array in non-maintenance mode, run a read-check on the array and then what if it comes up ok? Sorry I am just trying to make sure before pushing buttons.

Thanks for the tip, I don't know if you remember me from a few weeks ago, I was the person with this issue: I took the radical approach of replacing, the mobo, the psu and all related power/sata cables and rebuilding all from scratch, the issues I had seem to be gone now and I don't get anymore read errors so my guess is that it was either the motherboard controller failing, the psu or the cables which I will trouble shoot later. Here are my diagnostics after leaving the drive unassigned and starting the array. taichi-diagnostics-20251225-1428.zip (I stopped the array after generating the diagnostics)

Hi folks, so before touching anything further, I wanted to seek some advice. Recently I had some issues with my previous motherboard/psu that made unraid go a little bonkers with the read errors. During my troubleshooting, I attempted to remove a drive that became unmountable, start the array in maintenance mode, turn it off, start it again and rebuild on that same drive but since I started getting more and more errors on more drives, I decided to turn off everything. As it stands now, I replaced all the parts/cables that could be culprits and I stopped getting read errors on all my drives, I want to attempt a rebuild on that drive but it shows as unmountable, should I assign it at the same spot and start a rebuild or do a format and then rebuild?? I would like to know the steps about it, I checked the docs but it seems that my scenario is a bit unusual so I would like to make sure before proceeding. I started the data rebuild initially but from what I've seen in the docs/forums, a data rebuild on an unmountable drive results in an unmountable drive regardless? What should I do then format the drive and the assign it to the same spot in the array? Any help would be appreciated. If I have to lose data on said drive I can take that hit but would rather avoid it if possible. Thanks again for any advice and merry Christmas. As it stands here is the status of my array (stopped, and the unassigned device is the one I wish to put back):

Okay so I extracted only the relevant days in the syslog, everything started on Nov 29 up to Dec 3rd where I decided to stop everything, the file is 796mb I hope it fits here. The more relevant entries should be the ones with sata connection issues, the first nvme error (you can find that one very early in the log) and the read errors during the rebuild. Thanks for your time. syslog.txt

Yes in this case when it first crashed well obviously I had no other choice but to cold shut down (inaccessible through SSH or the terminal) but the second time during the rebuild when I saw that much errors I just decided to stop everything in a panic, calm down and try to think slowly. I decided to order a new motherboard, new sata cables, new sata power cables, new psu and 2 spare drives and try to pin point the issue by checking the drives 1 by 1, I know you can't really speak without any form of logs but I do have a syslog and I also would like to know what would be the best approach to take when I get the new hardware, should I attempt another rebuild with a new drive (even if some others gave errors without failing), or should I attempt to slowly transfer everything to the brand new drives and then move the data drive by drive to just restart an array as if I was a new user with an unprotected array of xfs drives trying to build parity? Until the re-build attempt, Unraid was able to emulate the array, so I took advantage of that to catalog all my media but after the failed rebuild attempt I stopped because of too many read errors, I am missing some files which are probably from the failed disk, I'm not asking for a super specific answer but if you had to take some shots in the dark, how would you go about it? Obviously I won't have any diagnostics to post until I get the new hardware and I really hope I won't have to post new ones because I really don't want this to happen again 😅 Part of me really want to point a failing motherboard connection or PSU because even the ssds on my cache pool by the end started throwing read-errors, no way an NVME, 3 enterprise drives and 1 ssd would show all the same errors at the same time being from totally different times of purchase and batches in my humble opinion. (Let me know if the syslog would be relevant to you though, thanks)

My bad I meant to add them but I forgot, here they are. taichi-diagnostics-20251203-0140-anon.zip

Hi folks, So this weekend my little server has been driving me nuts here is what happened from start to finish: -I was moving some data from my nvme scratch disk to the array and Unraid became unresponsive, even over ssh or directly through the terminal. -The motherboard after that refused to boot and got stuck in b2 or a0 mode until I removed that NVME. -After that it's been nothing but problems, it started saying that one drive is unusable. -I tried removing it from the array re-assign it and rebuild but after wards other read errors started popping for other drives so I decided to cancel the rebuild for now. -I also tried moving most of the drives from the motherboard SATA ports to the LSI card thinking there might be some issue with the motherboard, a little better but I still get errors during a rebuild or read check. -I also tried changing a few SATA cables to no avail. -Since so many different drives are throwing errors, I decided to pause the current rebuild attempt I was doing since the same drive becomes unusable during the rebuild. I am not sure that buying a new drive will solve this issue, if I had to take a guess I would say it is motherboard related?? I do not have access to another mobo for testing. I really want to fix this but I would appreciate some help to pin point the issue. I don't want to throw money at the problem without knowing if it will fix it if possible. Here are most of the errors I got in order: NVME failure: ``` nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" ``` Then I started getting this kinds of errors when most drives where plugged through the motherboard: ``` Nov 30 19:01:05 Taichi kernel: ata6.00: exception Emask 0x10 SAct 0x7fe000 SErr 0x4890000 action 0xe frozen Nov 30 19:01:05 Taichi kernel: ata6.00: irq_stat 0x04400040, connection status changed Nov 30 19:01:05 Taichi kernel: ata6: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 30 19:01:05 Taichi kernel: ata6.00: failed command: READ FPDMA QUEUED Nov 30 19:01:05 Taichi kernel: ata6.00: cmd 60/00:68:00:e7:00/04:00:08:00:00/40 tag 13 ncq dma 524288 in Nov 30 19:01:05 Taichi kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Nov 30 19:01:05 Taichi kernel: ata6.00: status: { DRDY } ``` When I moved things to the LSI cards I stopped getting these but I caught read errors while trying to rebuild or just complete a read check. Thanks in advance for any help.

Ok thanks for the tip, the reason I was asking is because I use to be able to use NTFS ADS streams to set certain information in the files and it would be preserved when moved to the array back then I had no extra config, after that I did disable them for performance tests and then I just removed the settings thinking that would immediately re-enable them but it didn't until I explicitly set them to the opposite. So not sure here.

DMCA? Yes hello, I am calling to report this MAM59 he committed the evil crime of possessing a fitgirl ISO 😝

Hey folks so I was wondering, If I add a line in the smb extra config such as `ea support = no` for instance, and later on I decide to revert the setting, is removing that line in the extra config enough to revert to the default which should be yes or do I have to explicitly set it to `ea support = yes` and only then I will be able to take the line off? Do all of these extra settings have a default to revert to when a line is removed or only some of them? Thanks for any reply.

I was able to re-enable them by using these options in the smb extra config: ea support = yes store dos attributes = yes vfs objects = streams_xattr streams_xattr:prefix = user. streams_xattr:store_stream_type = no The thing I still wonder about is that isn't this the default behavior, especially for the first 2? As far as I remember before touching the extra config that was working fine, I only tried disabling them to see if I could squeeze better performance.

Hi folks, if I recall correctly, I remember being able to set labels and statuses with directory opus that uses ntfs alternate data streams to store these properties and when I disabled these in the SMB config, it stopped being able to store them there and the program used an internal config file instead that does not preserve them on copy, move, etc. ea support = no store dos attributes = no The advantage of storing them in the files is obviously to preserve these attributes. I don't know if I had a day dream but I think I remember being able to preserve those in the SMB share as well and copying back and forth from my machine. Now my question is, is the xfs array when shared through SMB actually able to keep track of such attributes even if not usable directly in that file system and if I copy a file with ADS streams, will they remain but just not viewable outside of Windows? If yes then I will take the question to Directory Opus forums because I already took off these lines from the SMB config and nothing happened which is why I am unsure. If no then I guess the discussions stops here and I should be less distracted when I play with settings. Thanks again for any tips.

My bad after checking the logs I think this is because of NUT actions defaults so indeed related to the plugin: Aug 5 10:23:23 10.0.0.246 Taichi daemon notice upsmon[4950] UPS [email protected] on battery Aug 5 10:23:23 10.0.0.246 Taichi user notice xnut-notify-hooks.sh ONBATT commands are now executing in background... Aug 5 10:23:23 10.0.0.246 Taichi user notice nut-notify [ups] UPS is on battery. The system will shutdown in 240 seconds. Aug 5 10:23:25 10.0.0.246 Taichi user notice root nut-actions: Stopping Docker containers: nextcloud-aio-apache nextcloud-aio-notify-push nextcloud-aio-nextcloud nextcloud-aio-imaginary nextcloud-aio-redis nextcloud-aio-database nextcloud-aio-mastercontainer stash-s6 binhex-jackett resilio-sync kavita Debian-Bookworm binhex-qbittorrentvpn binhex-nicotineplus TubeArchivist-Redis VideoDuplicateFinder Unraid-Cloudflared-Tunnel P3R-OpenRGB TubeArchivist TubeArchivist-ES EmbyServer binhex-krusader Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel br-f8b8724bae99: port 6(vethfaad1fa) entered disabled state Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel vethd7a1e9c: renamed from eth0 Aug 5 10:23:28 10.0.0.246 Taichi daemon notice upsmon[4950] UPS [email protected] on line power Aug 5 10:23:28 10.0.0.246 Taichi user notice xnut-notify-hooks.sh ONLINE commands are now executing in background... Aug 5 10:23:28 10.0.0.246 Taichi user notice nut-notify [ups] UPS is online, any planned shutdowns were cancelled. Aug 5 10:23:28 10.0.0.246 Taichi user notice root nut-actions: 'on_battery' task still running, killing task and running 'on_line' task Aug 5 10:23:28 10.0.0.246 Taichi user notice xnut-notify-hooks.sh Terminated Aug 5 10:23:28 10.0.0.246 Taichi user notice root nut-actions: Starting Docker containers: nextcloud-aio-mastercontainer Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel docker0: port 14(vethdf477e4) entered disabled state Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel vethfe1f698: renamed from eth0 Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel br-f8b8724bae99: port 3(vethed2ff2f) entered disabled state Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel veth6a4d6f7: renamed from eth0 Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel br-f8b8724bae99: port 2(veth843de59) entered disabled state Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel veth63fecb9: renamed from eth0

Hi folks, So since I started my Unraid server I played a lot with the settings to optimize the speeds I get with the networks, by disabling certain stuff like NTFS extended attrs, hardlinks, and enabling turbo-write, multi-channel, I get some decent transfer speeds that I consider very acceptable. Very close to what a direct connection through SATA would give me. Now the issue is that when I do a file transfer, I am unable to perform basic operations on the same folders such as renaming, right clicking items and such without it taking 30 secs. 20-30 secs for a right click on an item is quite annoying, same if I try to open a file etc. Anyway to have some small portion of the bandwidth reserved only for that kind of stuff while I am performing a transfer? So that way it would make the transfer a little slower or prioritize when needed? If someone has any clue please let me know. I can post my SMB settings if needed. Thanks in advance.