tucansam

Members
  • Posts

    939
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

tucansam's Achievements

Collaborator

Collaborator (7/14)

14

Reputation

  1. OK I'm just doing them in the order that the GUI is popping up the options........
  2. Just did this with Disk 16.... It is not working. Formatting and rebooting had zero effect, although it fixed Disk 15. I have added four more disks, all of which were previously used (its been years) in this server, all of which are now clearing. I will update shortly, I presume I will need to format all of them and then I will have five disks which refuse to add to the array because "Unmountable: Volume not encrypted"
  3. That worked. But now the disk is showing up as added, and not added.....
  4. Do the LSI cards with the four external ports, and no internals, need to be flashed to IT mode also? I picked up a Dell branded LSI and it sees no disks attached... But the old card (that was giving CRC errors) saw them. Is this a firmware issue that is easily fixed?
  5. Wow, I really appreciate that!!! Thanks!
  6. The disk existed in the array long ago, like maybe a year or two ago. Its been sitting on a shelf since. How do I get the disk to add? And will I have this problem with subsequent former disks that I add?
  7. I did format it....... Diags attached. ffs2-diagnostics-20210915-1955.zip
  8. No. I just stopped the array, selected one of the disks from the drop down list of the next empty slot, and started the array.
  9. So I physically added four drives. All were mountable via the new "mount" button (used to use unassigned devices) except one drive, for some reason it wouldn't mount but was recognized. I added one of the drives to the array after stopping it, and then restarted. That's when I got the format error. Formatted it, and now am getting the not encrypted error. The disk is showing up in the list of array members, however it is not mounted. Yet I am getting green balls and assume parity is valid. So I'm not sure what is happening.
  10. All my disks are XFS, encrypted. I added a disk, it belonged to the array a while ago and has been sitting on a shelf after an upgrade. After adding the new disk, I started the array. Unraid said it was unmountable because it wasn't formatted (it was, I mounted it and read files just fine). So I clicked the format box and now it says its unmountable because its not an encrypted volume. But if I click on the disk it clearly says its "XFS encrypted." I've added or upgraded disks on this system dozens of times and have never had this happen.
  11. Dammit. I've got a 650w PS with those 5-way SATA splitters, and cables I've used in other servers with no issue. I suppose its the LSI controller card. I've eliminated everything else, essentially.
  12. OK. I got rid of the expander and all cables. I now have the LSI with four external ports, an 8088 -> 4x SATA cable, and my drives. Just plugged four drives into said cable, and one immediately threw 14000 CRC errors. In addition, two of the four drives connected show up as "Dev 4" and "Dev 6" and show all SMART attributes. The other two are "sds" and "sdt" and show no SMART attributes and will not let me run a SMART test. I'm curious if the CRC error reporting is because unraid has noticed the drives... that is to say, I am hoping the error count does not climb. I'm not going to add them to the array. Should I mount them individually and move some data around to test them, to see if the error counts rise? Is there a way to reset the CRC error count?
  13. I am re-evaluating the setup and am going to try an 8086 -> 4-port SATA cable directly connected to the external port of the LSI controller. The expander, the cable from the expander to the drives, and the cable from the LSI to the expander can all be eliminated as variables.
  14. As in replace each one, one at a time, until I figure out the bad part?
  15. As a matter of fact, I do have an expander. However, the first time this problem occurred was before the 2nd HBA for the expander was installed. Right now nothing is connected to the expander. I have an LSI HBA and all of the array members, except the parity disks, are connected to that HBA. I have a second LSI that will eventually connect to the expander. The expander is reserved for when I get a JBOD completed for expansion.