Ockingshay
Members
-
Joined
-
Last visited
-
about the note, does this release have the security updates from 7.2.5?
-
I am running out of space in my cache pool but will eventually upgrade my motherboard and cpu, so I don’t really want to buy 2 larger ssd sata3 drives in the interim just for extra space and then ultimately replace them and buy 2 gen4 nvme drives planned for the new motherboard. Is there a way that I can buy the new nvme drives now but put them into some sort of adaptor, so that I can plug them into my current and very old sata3 mobo? They obviously will be limited to sata3 speeds, but means I can increase the cache size now and then when I’m ready with the new mobo, I can transfer them across and it will be seamless. I do not have any spare PCIe slots as they are currently taken up with storage controllers. If not, I will continue to use the old, smaller drives until the upgrade.
-
I’m slowly going through the process of replacing all my reiserfs disks with xfs and adding additional capacity. I’ve noticed that after I move all the data off the old drive (3tb) and then replace it with the new drive (14tb), that after the reformat and during the rebuild, the drive always shows 268GB of used space. i assume that it’s the difference in the logical and physical (correct terminology?) from a 14tb drive and what is actually usable, but it’s off putting as the drive is empty but showing usage. Its been a while since I’ve added drives to my array, so may not even be a v7 induced issues.
-
Just updated to 7rc1. Have tried it with no dockers running and straight after starting the array, the drives won’t ever spin down. Even clicking the spin down button, the drives won’t spin down. ruby-diagnostics-20241209-1655.zip
-
Dec 8 21:06:29 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 7 failed: 7 Dec 8 21:06:29 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 7 tries: 1 Dec 8 21:06:29 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 3 failed: 3 Dec 8 21:06:29 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 3 tries: 1 Dec 8 23:56:31 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 8 23:56:31 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 15:48:41 Ruby kernel: md: sync done. time=97863sec Dec 9 15:48:41 Ruby kernel: md: recovery thread: exit status: 0 Dec 9 15:49:07 Ruby sSMTP[978858]: Authorization failed (535 5.7.139 Authentication unsuccessful, basic authentication is disabled. [LO6P265CA0028.GBRP265.PROD.OUTLOOK.COM 2024-12-09T15:49:07.452Z 08DD1672FDC2C2F7]) Dec 9 15:49:13 Ruby sSMTP[978961]: Authorization failed (535 5.7.139 Authentication unsuccessful, basic authentication is disabled. [LNXP265CA0004.GBRP265.PROD.OUTLOOK.COM 2024-12-09T15:49:13.329Z 08DD162E3F2292E4]) Dec 9 16:18:43 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 3 failed: 3 Dec 9 16:18:43 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 3 tries: 1 Dec 9 16:18:43 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:18:43 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:30 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:30 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:30 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:30 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:30 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:30 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:30 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:30 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:30 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:30 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:30 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:30 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:30 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:30 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:31 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:31 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:31 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:31 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:34 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:34 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:34 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:34 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:34 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:34 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:34 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:34 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:34 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:34 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:43 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:43 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:44 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:44 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:44 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:44 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:47:44 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:47:44 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 Dec 9 16:50:37 Ruby kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Dec 9 16:50:37 Ruby kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 started to receive these errors since updating to 7 rc1. Doesn’t seem to stop things working and all drives are recognised. I’ve rebooted a couple of times and every time the server is happy. ruby-diagnostics-20241209-1655.zip
-
2013 for me and hoo boy was it like the Wild West!! 🤣 How I miss the drama of shoehorning extra functionality into the OS, it’s all too professional and easy nowadays! Many a time has Tom been a broken man on major release days; I think it’s time we’re due another one for nostalgia 😂 A toast to all the great people that have come and gone and to those today that make this software wonderful 🥂🍻 Cheers!
-
With all these new features it would be nice to go back to simple fundamental functionality as mentioned: array shrink and native integration of unbalance. I should be able to add drives, remove drives and change file systems via the webgui and unraid manages that safely behind the scenes. all this new stuff is all very nice on newly rolled systems but those of us that have systems since the days of unraid 4 and earlier, need a little help moving with the times. I’ve upgraded my hardware several times on 2 pro servers that I have but struggle to control the arrays. and so if the most popular request is multiple arrays, surely before that happens, tools should be in place to manage it? after we have that, staying on the fundamental train of thought, data being the reason unraid began, as also mentioned, a way to back it up on or off site. Internet speeds have come a long way recently and it would be nice to backup my critical data to either another unraid server (extra sales) or cloud based storage.
-
I've ordered a new drive, but in the meantime i wanted to learn a little more about what it's actually reporting as the failure. I've run extended smart and it came back ok, but i've attached diagnostics etc. Wondering if someone could take a quick look at it and enlighten me? Many Thanks ruby-smart-20230808-1440.zip
-
I use safari on iPad only with authy app and for me to get this to work I had to do the following: my old password was strong enough to pass the new checks, so didn’t have to change it and it logged me straight in after the conversion. when I went to enable MFA it would hang when I put the code from authy on the webpage. In safari options I had to disable pop-up blocker. using the my servers app already installed on my machine, I signed out and then attempted to sign back in. It would take me to a new webpage and would tell me that my username/password was incorrect. I uninstalled and reinstalled the plugin and it worked first time. this has been a very clumsy implementation and for those that aren’t tech savvy will cause issues.
-
when does linuxserver update their dockers? Fridays? 4.0.1 has dropped and is whitelisted on most sites now.
-
It's time to give this a go! I have x2 14TB drives arriving today, so i thought i would start moving some data around with what space i have whilst i wait. 1) I would like to replace disk 1 (as that's the oldest) with a new 14TB drive, but formatted to XFS. 2) Once that is in place i will be able to copy the data over from other 3TB drives, remove them from the system and then add the other 14TB drive. I do not have any further sata ports, so i will need to remove a drive (1) before i can add a new one. What would be the correct procedure to accomplish part 1? In order to remove that drive (1), i will need to copy over the data to make it empty? Many thanks for your help! Part 1) Replace disk 1 with new 14TB drive and formatted in XFS. **I have the unbalance plugin to copy (instead of move as per your suggestion?) and there will be no other activity happening on the server whilst this completes**
-
Incredible, thank you
-
Hi, just wanted to say thanks for the enlightening response. I'm going to tackle this over the Christmas period when i have some free time. I have a Parity drive that's 14TB and 3 14TB array drives already; the rest are 3TB, being a mixture of XFS and reiserFS. If i understand your steps i will be able to: copy over the 3TB drive data to the 14TB format them to XFS or remove from the array set new config run a parity ? That sounds very doable! but i may need to clarify with a few screenshots if that's ok before i press go!
-
Just been checking my log and noticed this. My server is very old and has gone through V4, 5 and now 6 of Unraid and as such 7 disks are REISERFS. I have never dared attempt to replace my file structures as the only way i can think of doing it would be to move all the data off a drive via something like the unbalance plugin, remove the drive from the array, rebuild the array, add it back in and then rebuild the array again. Doing that 7 times on an array with 14tb drives doesn't appeal to me 🤣 and so although the date is 2025, will Limetech work on any sort of array manipulation GUI tools? i would also like to get rid of some of my old 3TB drives and replace with fewer 14TB and cut down on my energy consumption. I even bought a second license key with the idea of just building a new server and copying over 96TB of data, but again that doesn't really appeal to me either! As technology and storage tech improves, it would nice to be able to upgrade the array just like we can with mobos and processors etc. kernel: REISERFS warning: read_super_block: reiserfs filesystem is deprecated and scheduled to be removed from the kernel in 2025
-
setup: transmission client Cache enabled download share I have been using transmission for years and after a file has downloaded and seeding, mover will kick in on it's schedule (11am) and as long as there's no activity on that file, will move the file to the array. so far so good and has always worked a treat. I now have 1gbps and transmission doesn't seem to handle that speed. The webgui will become unresponsive and the torrent will max around 70MB/s. So i decided to try another client and my first attempt is rtorrent with the rflood UI. Set it all up and my goodness it's fast! i'm now downloading at LAN gigabit speeds of around 110MB/s! The only issue i have is that mover will now not move the files. Same scenario with files simply seeding, but mover recognises them as always open (even with manual invoke) and obviously won't do anything with them. I've read someone had success by enabling pre-allocation but i have added that to my config file but still no movement. Before i try another client, has anyone been able to get this to work as i really like this client?
