Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Ouze

Members
  • Joined

  • Last visited

Everything posted by Ouze

  1. Thanks again. Everything is good now. I reseated my cables. This reconnected the drive. I see a CRC errror count of 6. If this climbs, I will replace the cables and maybe plug into a different port. I ran the scrub and repaired corrupted blocks. I stopped docker, deleted my image, and restarted docker. Then, I reinstalled my apps from the "previously installed" spot. Very easy. I really appreciate your help.
  2. OK - I am going to go do that now. When I do the scrub, should I check the box for "repair corrupted blocks" or not? Thank you again for holding my hand through this, I really appreciate it. I have replaced disks in the array many time no problem but this is the first time I have had to deal with issues with the cache pool so I feel especially lost.
  3. I don't have anything important in the domains or system shares. I don't have any VMs. I'm not sure what a NOCOW share is, though? thank you
  4. Hello all, I got a weird email so I logged into one of my Unraid boxes and found that I think sdb, one of the cache drives, might have died. I honestly have no idea what my next steps would be. I am attaching what I have for logs here. Right now the server is up and seems fine. I am hesitant to take any steps without checking in because I don't want to make it worse - I'm not sure if the disk is just unmounted, or of it's dead, or... what. Thank you! min-syslog-20230509-0436.zip min-smart-20230508-2333.zip min-diagnostics-20230508-2345.zip min-smart-20230508-2349.zip
  5. Ok, mostly good news, some minor bad news: Before I rebooted I tried copying the syslog to disk1. It did so, but it doesn't seem to be useful: whatever broke seems to have broken prior to when the log went sideways, but attaching what I have anyway. The other minor issue: I rebooted dirty. I thought "poweroff" was safe from googling, but that clearly is not correct, as it's doing a parity check (Powerdown didn't seem to do anything). Is there a command I could be using in the future? Thank you again for the swift assistance, I really appreciate it! syslog.zip
  6. Thank you, crossing my fingers and rebooting now. 😨
  7. Hello all, At 0800 I got the following email from myself, as follows: When I went to check my server, every menu is blank. There is a warning about my license key missing. All shares are accessible and up. Plex via a docker is working OK. I can get in via SSH. I have re-seated the USB key, but have taken no other actions yet - I have not rebooted - for fear of making it worse. What should I do next? I'm not sure how to get diagnostics: root@Min:~# diagnostics Starting diagnostics collection... mkdir: cannot create directory ‘/boot/logs’: Input/output error done. ZIP file '/boot/logs/min-diagnostics-20211019-1130.zip' created. I don't have flash exported, so I have no way - that I know of? - to get to that path. Thank you!
  8. Ugh really sorry I didn't see this until now. I'm glad someone else showed up with that. The file he linked is what I used.
  9. Happened again - did a check, out the output: "bunker: error: SHA256 hash key mismatch, rnal.720p.bluray.x264-reward.mkv is corrupted" According to a search, that narrows it down to 125 files. There has got to be a way to get this plugin to output more useful (specific) information, right? Why are these error messages being truncated this way? I did an md5 check against all 125 files individual checksums and of course, they pass just fine. These files got dropped onto the server once and have not been touched since then. If this plugin is going to generate output vague as it is, and as prone to false positives as it seems to be; then ultimately it's just contributing noise, not value.
  10. I am doing a mass move from my old unraid server over to my new one. I expected some likely file transfer damage, so no surprise when I did a manual check and saw errors. What was a surprise was how... incomplete those errors were. I saw a few pages back someone else had a similar problem, and the instructions were to go into the hash log for the disk and find candidates, then run a b2sum (path) against each candidate. For some that is easy, but for like that first one and second one, there are a lot of candidates. Is there a less tedious way of configuring this output so I don't need to check 39 false positives to find the one I want manually? Also, that last one only has a single candidate, so I checked it. Those files have individual md5 checksums, one for each file. That directory passes an md5 check on both the source and the allegedly corrupt destination. I don't understand how that can be. I don't mean that I don't believe it, I just don't quite understand it.
  11. OK, I figured it out. Turns out there was nothing wrong with my process, I just wasn't waiting long enough. After the bin file is uploaded, it just sits there for about 8 minutes, but it did indeed then finally update and I have my issue fixed. 3500RPM fans now, much better!
  12. hello all, I bought a dell poweredge c2100 for my second Unraid build. I've built many PCs but this is my first actual commercial server - the other Unraid build was a Supermicro board in a Norco 4224. This server is 2u and it is very, very loud. It appears the fans run at 100%, all the time, which is like 5k rpm. They are not in a particularly warm room. With the Norco, I removed the 80mm screamers and replaced them with a 120mm fan plate and some nice quiet Noctuas, but this doesn't seem like a viable option here - changing to different fans would seem to cause lots of fan alerts, according to Google. What google said was that BMC firmware of 1.7.0 and below didn't have this problem, the fans idled at around 3k rpms. I'd like to downgrade as I am at 1.82. Here is where I am running into trouble: I don't know what I am doing. I enabled dedicated NIC for BMC and plugged in a cable. I set an IP in the bios, then logged into BMC, changed to a secure password. I am not clear exactly what to do now. When I go into the "firmware update" section of BMC, which seems very straightforward, I see an option to upload a new firmware. I tried getting the appropriate firmware from here: https://www.dell.com/support/home/ae/en/aebsdt1/drivers/driversdetails?driverid=hh9ww but... the files I see on here don't seem to actually contain the correct bin I need to upload, and the instructions included with the files are... very not clear to me. What is the easiest way to do this? Thanks!
  13. Well, I just feel dumb as all hell Thank you so much.
  14. I know this is a super stupid problem but I searched the forum and can't figure out the exact answer. I just set up Sonarr and sabnzbd and have them working on a fresh new share on my server. They talk to each other and it downloads files, no problem. The issue is that the files that it gets have incorrect permissions: I can't rename, delete, or move anything because they are owned by SERVER\nobody. I can copy or execute. When i run the tool to fix permissions, they are OK. However every subsequent download has the same issue. Did I screw up the share (which is new), the docker permissions for sabnzbd or sonarr or what? The share's SMB security is set to "public". In the docker paths for both sab and sonarr, they are all read\write. Neither of them is set to privileged. So there is some box I didn't check or fill out and I'm not sure which one it is. https://i.imgur.com/Ta6d7XT.png https://i.imgur.com/ingCSLi.png https://i.imgur.com/DwP8UUV.png https://i.imgur.com/yGfv3dd.png
  15. Hello everyone! I have 3 disks that I precleared over the last few days, which will the first entries into my new array (neither have yet done anything other then be precleared). Unfortunately, I think I screwed it up some. 2 disks are random ones I had extra, and I ran the command as normal. No problems. 1 disk is a new WD20EARS (they all will be when I'm doing this for realz) and I did the -a flag to toggle advanced format. This went through with no problems. However, my friend told me that I did it wrong, and that it should have been -A (in caps) and not -a in lowecase. 1.) Is this true, and what did I mess up - something about the partition? 2.) What's the best way to fix this? Do I need to preclear again?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.