Leaderboard

Popular Content

Showing content with the highest reputation on 08/23/18 in all areas

  1. You might have a drive with the 3.3v reset issue. These drives will work fine if connected via USB or with a molex—>SATA adapter but connected directly to SATA they don’t power up due to reset loop. The solution is to put kapton tape over SATA power pin 3 on the drive. You can overlap 1 and 2, if you can't cut a piece small enough for just #3. Search for SATA 3.3v reset and you will get lots of info. It varies by drive. Some work, some don’t without the tape. UPDATE: I added a shucked 8TB Easystore to my array last week (all my 8TB drives are shucked from Easystore enclosures). It was a white label EMAZ drive and I assumed it would have the issue and was prepared to do the tape thing. Fortunately, the backplane on my hot-swap cage negated the 3.3v reset since it is powered by molex connectors, a fact I had forgotten. Many SATA drives manufactured from late 2017 on will have the 3.3v reset issue, especially WD white label 8TB EMAZ drives shucked from BB Easystore enclosures. 3.3v reset is a new standard, but, a lot of older power supplies don't support it, thus, the tape or other solutions like molex--> SATA adapters, snipping a wire on the SATA connector, etc. I prefer the tape as it is reversible and easy to do. Sent from my iPhone using Tapatalk
    1 point
  2. You should post up a diagnostics file (Tools >>> Diagnostics ) which shows the OS trying to install and mount this drive. Hopefully, one of the Gurus can see what is going on from the files contained within it. Be sure to include the last four digits of the drive's serial number to simplify the problem of diagnosis.
    1 point
  3. Just added note to the first post on how to resolve this.
    1 point
  4. Since a file's name is separate from its content I would expect nothing to be done when the name is changed. The content remains unaltered; therefore so does the hash. The name is part of the file's metadata and editing it actually affects the parent directory. So if directories were hashed as well as files, then it's the directory that contains the file that would have to be rehashed.
    1 point
  5. The better approach is to set NO addresses to interfaces br1 and br5 (stop docker+vm service and go to network settings page) This gives the ability to set your own subnet and gateway for those interfaces under docker settings.
    1 point
  6. It's always worth having a spare motherboard on the shelf... and a spare processor in the cupboard... and some spare RAM in the drawer... and a box of hard disks on the floor... and a spare power supply balanced on the box of hard disks... and a graphics card, but I've forgotten where I put that! I really like the Asus Prime X470 Pro - my only complaint is that one of the x1 PCIe slots is blocked if you fit a 2-slot graphics card in the primary x16 slot. If only they'd positioned it above the x16 instead of below, as Gigabyte do on the K5. The Taichi doesn't have that slot at all - just two x1 slots. I won't be buying ASRock again in a hurry. I have their Fatal1ty mini ITX B350 board with an R5 2400G and they just can't get the BIOS right. The first release that supported Raven Ridge APUs didn't recognise certain NVMe SSDs (Toshiba OCZ was ok, Sumsung 960 EVO was not ok). The next release fixed the NVMe problem but broke support for the built-in WiFi and the PWM fan controller. And so on. The latest release is usable but the fan controller calibration still doesn't work. In retrospect I should have bought the Gigabyte mini ITX board instead. I haven't bought an MSI motherboard for years but I understand their recent products are pretty decent. At the moment my preferred ones are Asus and Gigabyte.
    1 point
  7. all gone very quiet after the move. I hope everything is ok @limetech ?
    1 point