Jump to content

Dissones4U

Members
  • Content Count

    144
  • Joined

  • Last visited

Community Reputation

16 Good

1 Follower

About Dissones4U

Converted

  • Gender
    Male

Recent Profile Visitors

1035 profile views
  1. Well, this explains a lot! I've had a similar issue but it was more of an annoyance and so I ignored it. Now that I understand this I've tweaked some settings and should be able to avoid any overflow onto the array moving forward. Thanks!
  2. Have you read the FAQ - What can I do to keep my Ryzen based server from crashing/locking up with Unraid?
  3. Really, I'd love to know how? Fan noise is my only complaint with this server, even in my closet it is extremely loud. Anyway, I appreciate you posting details, I'd found this thread because I have decided to install Kali and pen-test my network so that I can better understand security and hardening techniques but I can't seem to get the docker working. I see you're using a VM, I may have to go that route if I can't get this sorted. Anyway, if you know a trick to quieten the fan I'd love to hear it!
  4. You can also find it here
  5. According to this bug report I know this may be too simple BUT I had a similar situation and realized that after a recent move I'd plugged everything into the surge side of the UPS and not the backup side (because I did it blind due to space). This resulted in the exact situation you show above, zero load on the UPS, I noticed it a few weeks later and plugged everything into the other side.
  6. It looks like there is no SMART data for any of the disks, normally I'd say check the power and data cables first but maybe the controller is either loose or bad. Check and re-seat what you can, especially if you were either in the box or moved it recently, then power up and post new diagnostics.
  7. I've never created a USB from anything other than windows...honestly I was never able to get the "creator tool" to work and have had to do the manual method every time. I've never used any information other than what was provided in the links from my first post. Lol, yeah...manual Great news, just to manage your expectations a little.... unRaid is not the easiest thing to troubleshoot because it runs on so many different hardware configurations (which is also its beauty). Start hanging around the forum and reading about other peoples' troubles, within a few months your ability to troubleshoot will grow exponentially. I'm glad that it all worked out for you.
  8. According to your posts, your original USB is bootable in your array, therefore that same USB is in fact bootable from virtually any modern PC. While there could be extenuating circumstances the fact that you can't get a known to be working boot device to boot from your HP suggests, at least the possibility, of operator error. I suspect one of two things, either you're not configuring the HP BIOS correctly or you're not taking action during the boot sequence The BIOS on many computers have the USB boot option as USB or Removable Devices but some also might list it as a Hard Drive choice. So, if you’re having issues finding your device, you may have to look around a little bit. Sometimes, USB drives might deliver a message to press a button before the PC will boot from your USB device. If this occurs and you don’t do anything in response, your PC will look to the next boot option in the sequence order of the BIOS. In most cases, the next option would be your hard drive. Most modern PCs will boot from USB assuming you have set it correctly in the BIOS. See this article from the HP store on booting from USB. Focus on getting that original USB booting in your HP first, there is no good reason it won't. Then we'll focus on your new USB. If you absolutely can't get anything to boot from USB on the HP you will need a third machine before anything further can be done.
  9. Considering Midnight Commander is built in, is there an advantage to using Krusader? Honestly I've never used it because I was using the Dolphin docker for a long time. Dolphin is pretty good too if you need the GUI but MC seems easier somehow once you get used to the basic operation.
  10. @germericanish your image is from the dashboard, have you tried going to the docker tab and using the force update option? For example from my dashboard filezilla has no update available and in fact from the docker tab it says up to date BUT there is a force update link. see below, I have no idea if this will help but it might...
  11. Something appears to be wrong with your cache, I'm not well versed with the cache functionality yet so I could be way off base here, if nobody else chimes in then check that your cables and cards are properly seated, change cables if you have spares. Also, I can't really tell but your cache looks like it's RAID 1 and maybe full but I'm not positive.
  12. It sounds to me like you're saying that you have not yet tried the initial recommendation of booting the new drive in another machine? Ultimately, you MUST create a new drive that boots in another machine in order to move forward. If you're convinced that you're preparing the replacement drive according to the links provided above then you need to try a third machine, because the replacement drive MUST boot. Once you have a new drive that boots follow the steps above for changing your flash device.
  13. @CDLehner Here is my current understanding of your situation: Old USB still works fine, you just can't update OS due to lack of disk space (If yes, then post zip from Tools ==> Diagnostics with your next response) You've tried to create a new USB without success, it won't boot in any machine (If correct, then likely you're not preparing the USB as suggested) Old USB will not boot in any machine other than your array (this stumps me, if it boots in the array it should boot anywhere, make sure boot from USB is selected in the BIOS of your Win10 Home test machine, also don't boot from USB3) Anyone please feel free to help me with this process as I'm thinking that the USB may be the issue and so eliminating that seems to be the first step. I feel like there may be a more efficient way to do this but unfortunately nothing comes to mind.... I'd setup a brand new flash drive by reading all of these links ==> (see USB recommendations) and load the latest trial version of unRaid onto it as instructed on the getting started page Put the newly created trial USB in a box that is not your server, enable USB boot in BIOS, and boot to GUI mode. (You'll need peripherals attached) If it works then great, if not you may not be preparing the USB correctly. this step takes only a few minutes and should be relatively easy Once you've booted with a working USB: (Here is where I'm not sure how best to proceed, better overly cautious then not I think) For safety I'd remove the power from all of the hard drives in your NAS so as not to accidentally lose data. Although I suspect that the trial version should pick up your array exactly as it was, I'm just not certain and I wouldn't want you to do anything that might affect parity. Boot your NAS with the trial version of unRaid in GUI mode with peripherals attached If it boots then great, move on to the changing the Flash Device Wiki If it doesn't boot (it should since you got it to boot in another machine) we've at least ruled out the USB at this point (boot failure) I'd probably plug in a rescue USB I have no idea if a rescue USB would write to disk and invalidate parity so I'd definitely unplug disk here if you didn't earlier. Get as much hardware info as possible such as CPU / Board / Memory / Controllers / NICs etc save to text and come back to the forum. Also, keep in mind that being calm when trouble shooting something as complex as your array is of the utmost importance. Getting frustrated will generally lead to mistakes...
  14. So if they went in at the same time then look at how they are connected (I'd guess they are using the same connection), loose/bad cables, check the controller etc. Once you re-seat or replace cables and check other connections then: Once you run the extended SMART then post new diagnostics