darkcyde

Hi I've had a few boot issues with no Web GUI loading, so have tried replacing my USB key. I originally purchased this key in March 2021, and have not used the USB replacement service in that time. When I boot into Unraid, it tells me The Regisitered GUID does not match the USB Flash boot device GUID, and tells me to Fix the error, but when I go to Replace Key, its greyed out and says its ineligible. Can anyone help?? My server is currently offline entirely!

Hi all I run an Unraid server (v6.9.2) on a HP Proliant DL180 G6 filled with 11 x 3TB HGST SAS Drives. (dual parity, 9 data). The drives are second hand refurbished drives bought in bulk, they are cleared and checked before sale, and I also preclear them on receipt. Been running absolutely fine for months, if not years, with just a few drives failed every so often....maybe 3 drives failed in 2 years. I use HGST drives as these are the most reliable according to BackBlaze stats. In the past week, I've had 7 drive failures.....is this just the drives coming of age, and is purely coincidence, or should I look at a possible backplane issue, or an issue with the HBA, which is a H220?

So if I drop the parity disk, I should get a massive speed boost?

I've been running Unraid now for several years using enterprise hardware, and recently bought a new (old) server for archiving purposes which is 2 gen up on what I already had. I was expecting some major speed improvements, but in reality it's not much faster at read/write speeds. On both machines (1 x HP Proliant DL180 G6, 1 x HP Proliant DL380e G8) both running SAS 7.2k drives, on my main machine I have 2 x parity 1 x cache, 9 x SAS drives, and the array is Encrypted, and 1 x Parity, 10 x SAS drives on the archive machine, not encrypted. I have dual 1GB network cables for both machines, running in a Gigabit switch, again enterprise grade. On average I get around 80MB/s read/write speeds on an individual drive when writing to the main array on the main machine, but it can reach 1GB/s reading for parity across the entire array, so I know it's not bottlenecking apart from individual drive writes. Have I got a major issue, or have I just got a config problem? I read others getting 600MB/s or more!!

Install the app on a smartphone, such as android, and then set up a camera via that, and then the GUI becomes available

I couldn't even get a decent camera connection going....I admit my IP camera is a Foscam on the older side, but it wouldn't give me much control over it, like tilt and pan, etc....I had to keep dropping back to the camera UI to make adjustments.

I'm running dual Xeon E5270s (i think that's the right number) and it uses about half a percent at maximum.

It does work....what you have to do is run the docker, then install the Xeoma desktop software, access the server via the desktop, create a camera, and then you can access the web UI. Unfortunately tho, Xeoma is a terrible product and you get much, much more functionality with Zoneminder, its looks dated.

I'm trying to transition away from ZoneMinder....it works but it feels a decade old...plane text links, zero icons, etc....and it breaks up my motion detected videos into small chunks rather than just record an entire video with motion.

At least its not just me then....let me know if you manage to sort it? Dev seems to be quiet on here and the github, so not sure what to do. I did consider learning how to make Dockers and create one myself for xeoma

Hi I've installed the Docker, but I just get a 404 error on the 10090 port....nothing substantial in the logs expect for this.... Password set successfull *** Booting runit daemon... *** Runit started as PID 48 [Jan 21 10:22:40 AM] Starting the server in 5 seconds. See the log directory in your config directory for server logs. Jan 21 10:22:40 f23f404389f9 cron[53]: (CRON) INFO (pidfile fd = 3) Jan 21 10:22:40 f23f404389f9 cron[53]: (CRON) INFO (Skipping @reboot jobs -- not system startup) I would be grateful for any assistance. Kind regards, Leo

Yeah, you could be right there....looking at the specs on the original SSD, they have the speeds as 180MB/s read, and 133MB/s write, whereas the new drives are upwards of 530MB/s, so it's probably the backplane not handling the throughput very well. I will just disable the error reporting and see how things go.....as longs as it doesn't go back to the whole thing crashing down like it did before, I'll stick with the latest drive and just disable the CRC error report. Thanks for your help!

Thanks for the reply. If it were the backplane or cables, surely the other mechanical drives, or the original SSD would also be showing errors? When I swap back to the original SSD, there are no errors, its just with these two new SSDs. There is nothing mission critical on the cache, and anything that might be lost can just be either redownloaded or recovered from the previous days back up, so I'm not overly concerned about disabling the erroring....I can always check it manually periodically to see how it's doing, I just don't really want my phone chirping every few hours when something is downloading with a notification telling me what I already know

Hi I have a HP DL180 G6 with 18TB (9 x 2TB) of SAS Drives, 2x 2TB Red NAS SATA drives, and a SanDisk 120GB SSD Cache drive. I have AppData set to the cache drive, as well as the downloads share (which is just a temporary intermediary location until the various apps file the downloads away to their correction locations), and I have the system drive on the Cache too. This has been running fine for several weeks, but I found the 120GB SSD Cache drive to be too small, so I decided to upgrade it. I got a Kingston 480GB SSD, installed it and got everything back up and running, but I got tons of UDMA CRC error notifications when I was downloading something. Also, over time I noticed the AppData CA Backup/Restore backup wasn't running correctly, dockers wouldn't start up again in the early hours after scheduled maintenance, and the docker log would fill up to 100%, and then after about a week of this, this whole thing would require a reboot to get running again, after which everything ran fine again till the next morning, all the time with constant CRC error notifications on the Cache drive. The errors are only clicking up 1 at a time, so a total of about 100 errors over a week. So I reverted to the original SSD, and everything worked fine again, no CRC Errors, no docker log filling up, etc, so I figured the new SSD was faulty, so I returned that one and got another one, this time a Crucial 500GB SSD. Installed this one and I'm getting UDMA CRC Errors again, but not to the same extent as the last SSD, and none of the server/docker errors, so far anyway. The CRC error count is currently at about 25. So, what could be the problem here? I can't change any cables which seems to be the usual culprit of CRC errors as all the drives are on the same backplane connected to the controller via SAS cables....none of the other drives are giving CRC errors. If the server continues to run fine with the second SSD, albeit with the CRC errors, can I just ignore the errors? Is there any way to disable the constant CRC error notifications without masking other errors that might arise in the future, or do I just have to live with them? Is this possibly a hardware incompatibility with my drive controller in the server and the drives themselves, and the SanDisk original SSD was fine, but the Kingston and Crucial are not? Should I get a 500GB SanDisk SSD and try that instead of the Crucial and Kingston? Thanks in advance! Leo

Hi I currently have two NICs, one is a 4 port assigned completely to a VM for pfSense, and the other is an on-board 2 port for UnRaid. They are currently configured as two separate ports with a unique IP, but I would like to bond them together to spread the bandwidth across both ports, but I can't seem to configure it....at some point I seem to have created two Bond groups and now each port is assigned to a Bond group of its own and I can't change this....can anyone help? I've attached a screenshot of my network config page below...