Leaderboard

Hello everyone, I am running Unraid 6.4.0. I just got a used APC Smart-UPS specifically a APC Smart-UPS SMX1500RM2U X 1200W/1500VA LCD 120V 2U/Tower UPS System https://www.amazon.com/APC-Smart-UPS-SMX1500RM2U-1500VA-System/dp/B002TIR2Z2. I have it connected with USB to my server. I have tried ever setting and can not get it to connect. I have also tried Network UPS tools but that didn't work either. Any help would be greatly appreciated. Mark

The syslog shows that you are having trouble communicating with the SSD. This is probably why the system is not shutting down as it cannot successfully unmount the cache drive. The error looks as if it is probably related to the SATA cabling for that drive. The drive has a large number of CRC errors and that type of error is nearly always cable related.

The one thing you must NOT do is accidentally assign a disk with data on it as the parity drive as that will lose its contents! Also do NOT check the box that offer to format any unmountable disks during the procedure below. The procedure to follow if you are not certain which is your parity disk is: Assign ALL drives as data drives Start the array. One drive should show as unmountable. That will be your parity drive as the parity drive has no file system, so make a note of its serial number If more than one drive shows as unmountable stop and ask for advice. stop the array Use Tools->New Config to reset the array Assign your data drives and now since you know the parity drive serial you can assign that as well. The data drives can be in any order as with a single parity system the order does not affect parity Check the box to say parity is valid and start the array Check the contents of some of the drives to make sure they are what you expect. All your user Shares will also be present but with default settings (assuming you have User Shares enabled in your settings). It would be a good idea to do a correcting parity check at this point as you ticked the box to say parity was valid so it is time to ensure that is true.

OK guys, I'll rebuild

Answer to No. 1--- If you can mount the drives, there is a file browser built into the the GUI on the Main page. (It is the 'file folder' icon at the right of each of disk# line. As I recall (I am also 79) , you can assign a 'New Configuration' via the Tools >>> New Config utility. That spreadsheet of yours has all of the Information that you need in the 'Label' and 'Serial #' columns. You will be assigning hard drives by their serial numbers to a Disk slot on the Main page. I personally would only assign that drives that seem to have data on them. i.e., Parity and Disk 1 through 8. (see note below) I seem to recall that you can 'Trust parity' when you start it up. This is the only point at which you have a choice to make. Personally, I would trust parity at this point. This will allow you to check each disk to see that it is readable before you commit to a parity rebuild. Then you start it up. And let's see where we are at that point. NOTE: You have a Disk 9 and a Disk 10 in the table. I see that both of those disks are 3TB and your parity drive is a 2TB drive. So neither of them could have been part of the array. Disk 9 is listed as cleared and seems to have no files on it. I am assuming that you had not added it to the array prior to this time. Disk 10 is apparently new. One reason for my questions is that both of these drives appear to be seven to eight years old. The reason for this question is that you don't want to assign the HD with serial number YAHLP75W as parity if you previous replaced this parity disk with one of the 3TB drives and converted this 2TB drive to a data disk!

@188pilas For 6.7.0-rc you need to install the beta version plugin from here: http://sdevel.de/ProFTPd.plg Once 6.7.0 is released, I'll work on a new version of the plugin which should be available as normal update.

you are mistaken, this is not correct, its the HOST ports that cannot be the same, the container ports can (and in most cases should be) the same if you are deploying multiple containers for the same image.

I don't have remote access to my unraid box cause I can't get openvpn working properly, when I get a chance to, I will post. For the dockers on the dashboard, it's just a setting somewhere. Don't recall where.

Won't affect this at all Post the diagnostics when it starts going up.

Post all files up. If you have multiple files that look similar sort them by date and post up only the recent ones which appear to be related to the problem. One (or more) is probably a zipped file. Do NOT unzip.

No problem, do you mind confirming if the controller you were using looks like this one: https://www.amazon.de/dp/B07MVYN6X9/ref=cm_sw_em_r_mt_dp_U_5kzZCbKDS7ZGC So I know for the future, as in the syslog it appears the same as this 10 port one: https://www.amazon.de/Informatique-Controller-Professionelle-Komponenten-vorinstallierten/dp/B01ENKHLS6/ref=sr_1_fkmrnull_3?__mk_de_DE=ÅMÅŽÕÑ&keywords=asmedia+10+port&qid=1557240379&s=computers&sr=1-3-fkmrnull

Yep.

How much of that storage capacity do you actually need now? I would recommend just using the larger spinners in the parity array and leave those small ones out, at least for now. Fewer disks means fewer opportunities for problems. The 2 SSDs won't make a good mirrored cache due to their different sizes. You can use them both in the cache pool but with no redundancy.

Hi There, I have done a bunch of searching here and elsewhere and can't seem to find an answer on this. 1. I have OpenVPN AS setup in a docker with ports 943 Web and 9443 TCP VPN port open 2. I am looking to use letsencrypt to redirect 443 for domain vpn.duckdns.org to local server 192.168.1.5:9443 for vpn connections Does anyone have any idea how i would set this up in the letsencrypt docker. Reason for this is work is blocking anything but HTTP/HTTPS so need to be accessing on one of these open ports. Help would greatly be appreciated. Thanks!

hey @CHBMB, tried the latest LibreELEC build 6.7.0-rc8, but it failed. i'm on a Digital Devices card (TVHeadend recognizes the tuners as: Sony CXD2854ER). might it be, that the DVB drivers are missing and so no tv-card gets recognized? it results in no /dev/dvb directory to be created and so the tvheadend docker won't start. 6.7.0-rc7 worked fine.

You can add it as an extra domain. Read the Readme in the githublink in the first post.

I would suggest that you post up the Diagnostics File from this server. If you lose access with the WebGUI, login via the console and type diagnostics on the command line. That will write the Diagnostic File to the logs directory/folder on your flash drive. Upload that entire file with your next post.

Really nice How do you change the color for the bar under the banner? How do you get those icons for the dockers? All my icons for dockers and plugins are just blue ones. And how did you get that layout on the dashboard with the dockers and everything else? Looks nothing like my layout

This feature has been already requested for the project (https://github.com/jc21/nginx-proxy-manager/issues/58).

In the syslog, search for a line similar to this: May 1 08:09:02 Tower7 kernel: mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)

Yeah, we've got an issue on our Github, we're looking at it.

The Parity disk contains only the result of a parity calculation which can be used to reconstruct the contents of a single data disk should that disk fail. The order of assigning data disks makes no difference in single parity systems. No. In Unraid, each data disk is formatted with a standard Linux formatting system. Each data file is stored on a single disk and that disk can be read in a Linux computer. So once we know exactly which disks are the data disks, your data should now be readable. In fact, you can actually run Unraid without assigning a PArity disk. Just for appearance and often a COD condition that many people want to have things neat and orderly. Having an empty hole in the middle can induce a moment of panic to many of us... If you are talking about the MB SATA port numbers, you could do that. I personally put a little 'Disk X' sticker on the outside of each drive housing so I can quickly locate them. By the way, once you assign them, you could move the SATA cables to do the same thing. Remember Unraid tracks disks by serial numbers and you assign each disk to a particular Disk slot by those serial numbers.

Assign all five disk as data disks. Start the array. One (and ONLY one disk) should show up as unformatted. The disk that shows up as unformatted will be your parity disk. (If you have more than one disk showing up as unformatted, STOP and ask for help!) Stop the array again. Reassign the unformatted disk to the Parity Disk slot. You may want to reassign one of the other data disks to fill the slot that the parity disk was in. Now, start the array and rebuilt parity

Hi - I have been using this for the past year or so, any plans to update the container to the latest release 20190417? Thanks!

I am running the Asrock taichi x399 with 4 GPUs and have had no real issues. I started with 4x 960s but have since replaced the 2 bottom cards with RTX 2070s and couldn't be happier. Getting within 3% of bare metal performance even with the 8x slots. The bottom card gets the best airflow so I have a nice overclock on that card. I use the top card for unraid unless all 4 gaming workstations are in use- then it takes over the top card on boot. It shouldn't matter where your favorite GPU sits, since 8x and 16x slots perform very close to the same. My preference is to have the GPU with the best airflow- be the primary for my VM. I use web gui or ssh to manage the array after the 4th machine boots.

Here are a series of questions for you. 1-- How many parity disks did you have? 2-- How many data disks did you have in your parity protected array? 3-- How many cache drives did you have? 4-- Did you have any disks mounted with Unassigned Devices plugin? 5-- Did you have any other drives in the server that were simply not being used? IF you did, can you figure out which disk that may have been? (You said you had a precleared disk. Do you have a preclear report from that disk that you could get the serial number from?) Now, let me state something you may not know. Unraid uses the serial number of the drive to keep track of where is is assigned. Thus, for example, you assign a hd with the last three numbers of serial number of 'BQD' as Disk 3, when Unraid boots up, it looks for a HD with that serial number and assigns it as Disk 3! If it does not find a HD with that serial number, the Disk 3 'slot' will not have a drive assigned to it. Parity and Cache disks are also tracked using their serial numbers. Even if you don't have answers to all of these questions, we can get you back to a working array without data loss. It just may take a bit longer.

While it's up on the bench, can I make a small UI request please? Can the link to the Unraid site from the header logo open in a new tab/window? And/or could a link to the forum be made available from the interface again (unless I've lost it)? It's how I usually get here.

I would like to upvote that too. A feature to backup the folders sequentially would also be nice. In that way small services can be started again and not all of them have to be down just to wait for the large Plex database do finish backing up.

It would appear that that drive is total toast. Do you have the key file? If you don't I would start by reading this webpage: https://lime-technology.com/replace-key/ You will probably have to contact LimeTech using the e-mail address at the bottom of the page to get a new copy of your original key file. The purchase a quality brand name flash drive (preferably USB2) of less than 32GB. Download the version of Unraid that you want to use. Install it on that flash drive. Now tell us what you remember about your server. How many parity drives did you have assigned? How many data drives? How many cache drives. You might also mention the size of the various drives. Did you do a screen capture (or webpage printout) of the drive assignments?

I've got this in my nginx config (in proxy-confs/gitlab-ce.subdomain.conf): server { listen *:80; server_name registry.subdomain.duckdns.org; server_tokens off; return 301 https://$http_host:$request_uri; access_log /config/log/nginx/gitlab_registry_access.log; error_log /config/log/nginx/gitlab_registry_error.log; } server { listen *:443 ssl; server_name registry.subdomain.duckdns.org; server_tokens off; include /config/nginx/ssl.conf; client_max_body_size 0; chunked_transfer_encoding on; access_log /config/log/nginx/gitlab_registry_access.log; error_log /config/log/nginx/gitlab_registry_error.log; location / { include /config/nginx/proxy.conf; proxy_pass http://gitlab:9381; } location /v2/ { include /config/nginx/proxy.conf; add_header 'Docker-Distribution-Api-Version' 'registry/2.0' always; proxy_pass http://gitlab:9381; } } and this as the container's extra parameters (minus setup for email, backups and container registry): --env GITLAB_OMNIBUS_CONFIG="external_url 'https://git.subdomain.duckdns.org';registry_external_url 'https://registry.subdomain.duckdns.org';gitlab_rails['gitlab_ssh_host']='git.subdomain.duckdns.org';nginx['listen_port']=9080;nginx['listen_https']=false;nginx['hsts_max_age']=0;registry_nginx['listen_port']=9381;registry_nginx['listen_https']=false;registry_nginx['enable']=true;registry['enable']=true;" If you want to use ssh rather than https for cloning/pushing, you'll need to add a port to the container for it: host port 9022 (or whatever you like that isn't being used), container port 22. I then add this in ~/.ssh/config: Host gitlab HostName git.subdomain.duckdns.org Port 9022 User gitlab although I have to say that, while this works for Mac and Linux/BSD, I have no idea what the equivalent is for Windows!