Jump to content

Frank1940

Members
  • Posts

    10,204
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by Frank1940

  1. @PoppaJohn, the reason that @johnnie.black is saying this is that a CRC error is that when data on a SATA cable is being sent to-and-from a hard drive, it is encoded with an error detecting protocol. A CRC error is triggered when that code detects an data error. (The data will be resent until if is received without error.) As a complete aside, I have never quite figured out why CRC errors have been flagged out as being such a big issue. They really don't endanger data unless you are getting thousands of them per second! In that case, they would significantly slowly down data transfer rates and, perhaps more importantly, there is a possibility that an error could slip through undetected as all error detecting protocols can fail if the number of errors in a data block exceeds the number that the protocol can detect in a single block.
  2. OK--- My recommendation is to add the cache drives as cache drives. Then add all of the Data and Parity Drives as DATA drives! Then start the array. Two (and ONLY two) of the drives will be unformatted and not mounted as DATA drives. These are your parity drives. If there are more or fewer than two drives in this condition, STOP! and ask for more help!!!! If there are exactly two drives unformatted, stop the array and assign one drive as parity 1 and the other drive as Parity 2. Start the array and a parity rebuilt will start. It should finish without a problem and you will have a protected array again. (The reason, you don't want to assign a drive as parity to begin with is that as soon as the array starts, a parity rebuilt will begin and if that drive happens to be a data drive, you will lose all of the data instantly!) EDIT: (Order of the parity drives are unimportant as parity will have to be rebuilt in any case. This is specfically true with Parity 2 as its calculations are based on data location in the data matrix.)
  3. Take a deep breath and decide to try things slow and easy. First, you have not lost any data. You may lose your plugin setups, Dockers setups and VM setups. These will most likely have to be rebuilt. First, what luck did the data recovery firm have? The most important directory that would be needed for recovery is the config directory/folder. But even without that we should be able to get the server back running with all of its data intact. So begin by telling us what you remember. How many parity drives, how many cache drives and how many data drives? You can usually figure which drives are the cache drives as most folks uses smaller capacity drives or ssd's for them. If you have purchased your Unraid license, do you have the .key file saved somewhere where you can find it. If you don't have the file, you can start here to get a replacement key: https://wiki.unraid.net/UnRAID_6/Changing_The_Flash_Device#Manual_Method_.28Legacy.29 At the bottom of the page, you will find a link to LimeTech support to discuss getting a replacement key file if none of the options on this page are applicable.
  4. Just a SWAG--- But could the plugins be adjusting the hardware settings on the MB? That would account for the plugin settings having a residual effect...
  5. You will need to move to the Next branch as it is a feature of 6.7.0-rc series.
  6. Any time something like this happens, try to get a Diagnostics report. Tools >>> Diagnostics Without that report, the Gurus have nothing to even start to troubleshoot your problem. If you have already purchase your key, you would not have to purchase a new license if your flash drive is defective. (You have purchased a licence for life.)
  7. I am much more familiar with SAS to SATA connector cables but I believe you are looking for one like this: https://www.amazon.com/CABLEDECONN-SFF-8087-SFF-8482-Connectors-Power/dp/B010CMW6S4/ref=sr_1_4?ie=UTF8&qid=1548874809&sr=8-4&keywords=mini+SAS+to+SAS Problem is that with the SAS to SATA, you have to be concerned with which end the SATA connectors attach to (MB or SATA drive). I am not sure if this is an issue with SAS to SAS...
  8. A piece of cardboard for days like this... 😈
  9. Model numbers for the LSI cards are found in this thread: https://forums.unraid.net/topic/69018-sata-controller-replacement-question-and-advice/?tab=comments#comment-630097 To get the model numbers for the 16 port cards you replace the -8i with a -16i Let me at this point interject this factor. Apparently, LSI never made many of the 16 port cards and I suspect when they did, they were OEM cards (Dell, IBM, Etc.). (They tend to be a full height card and often won't fit in the half-height server cases.)
  10. There are no twelve port cards. Eight, sixteen and twenty four are available from LSI but the cost of the 16 and 24 make the eights very attractive for most of us. Most of us use SATA drives. (I think mostly because they are cheaper!) Many of us have gotten LSI based cards off of E-Bay. Many folks have gotten the used cards (Dell, IBM, Hp) as they are almost always genuine. Avoid Marvell based solutions as they sometimes have problems when used with Unraid. (When the big server farms upgrade their servers, they apparently replace everything...) If you purchase 'New' from E-Bay, vet the vendor carefully as there are counterfeit cards out there. I would purchase only from a US based vendor with a proven track record. (Since you are in the SATA controller thread, you do realize that Unraid requires cards that are in the 'IT Mode' not RAID.)
  11. @Arcaeus --- Why don't start by reading the Section 1 of the UnRaid manual and other sections that pertain to your questions. The manual can be found here: https://wiki.unraid.net/index.php/UnRAID_Manual_6 I want to point out that Unraid is not RAID in the formal sense. It does use either single or dual parity in its protected array (and raid is a part of its name) but that is where the similarity ends.
  12. What I suspect may have happened is the the caret is black so you would see it! Just try clicking in a number of places to see if this is the case (or switch to an Lighter 'Theme' ).
  13. try left clicking at the right side of the Motherboard 'Box'. My display has either an 'up' or 'down' caret that opens and closes the box there. See here:
  14. @StrandedPirate, What variety (Home, Pro, ...) version of Win10 (1803, 1809, ...) did you find this a solution worked on? @PiZZaMaN, A reply from you would be helpful also!
  15. Another solution to Win10 Issues in the ongoing saga of MS security upgrades: Many thanks to @StrandedPirate for this solution!
  16. Monthly is a good choice. Doing a parity check verifies that all of the disks can be read and has often detected minor issues which can be easily corrected before they become major ones which might result in data loss. (Think of it like finding high blood pressure during a routine physical as opposed to a heart attack!)
  17. Try creating a banner with a horizontal width of (say) 3000 Pixels. This might give a banner that won't look too distorted at the extremes. I did some light overlay boxes for my banners and had to adjust the width to sure that the box always allowed the text to be visible. (I was working in Photoshop Elements and put the overlay boxes in a separate layers which made adjusting them much easier.)
  18. I did a little playing on my 2560X1600 monitor. It would appear that the image is 'stretched' horizontally as the width of the browser changes. So my best assumption would be (if you want everything to geometrically correct) is to use a solid color banner with no images. On further reflection, you could also use a banner that transitions across the color spectrum as the geometric stretch would not be apparent. (By the way, the geometric distortion is not too bad when a 1920 banner is stretched to 2560...) What I am not certain about is whether the folks discussing this issue are using the GUI boot option and viewing the banner on the console (which I imagine would be full screen) or if they are viewing the GUI on an remote device (PC, Smartphone, Tablet). If they are using the console GUI, they could edit an existing banner to be the proper pixel size for any resolution monitor.
  19. The Problem with a darker shades of Blue on Black is the 'Brightness' setting of the individual monitor. What is fine contrast on one monitor will be virtually black on another monitor. Looking at the above screen capture, the "COMPLETE" lacks contrast and not easily read but the larger blue 'squares' are fine. (Disclosure: I personally dislike black backgrounds. I am 'old school' and want black ink on a white/off-white page!)
  20. While I am not @Jerky_san, This is what I see on the Dashboard: While I know I can grab my calculator to do the simple multiplication, I can't believe anyone is truly interested in knowing the percentage load.
  21. Go to Tools >>> Update OS Change 'Branch' from "Stable" to "Next"
×
×
  • Create New...