coherent

Members
  • Posts

    30
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

coherent's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks Johnnie, I was kind of afraid of that. Would UFS Explorer standard edition work for me? I'm not entirely sure how I will do this- I suspect I will have to pull out the drive into an external case and then search it using UFS on my laptop.
  2. I'm wondering if someone can help me out. I rebooted my unraid array after upgrading and my disk 3 came up as unmountable. I made the mistake of saying that I wanted to format that disk, which I thought would cause the array to rebuild what I had missing. It did not, instead what it said was that the drive was empty. I then took the array offline unassigned disk 3, reassigned it, then started it. It asked if I wanted to write to drive 3 based on the parity and I said yes. I waited 8 hours and when it finished I could see that I had 8 million writes to disk 3 but yet the data is still missing. Is there a way to get that data back based on the parity disk? I can tell that during the rewrite, that I only had 30,000 writes to the partity, disk 1 and disk 2 each while the disk 3 had the 8 million number. I'm attaching my diagnostics below. Thanks! Stephen alaska-diagnostics-20190401-0021.zip
  3. Thanks guys! I think I did the correct procedure. I didn't explicitly format the drive, but I removed the drive from the array and then started it up. I could see the contents of that removed drive so then I stopped the array and added back the disk (without a format). When I started it back up it says that it's doing a data rebuild and after letting it go for a few hours I can see that the disk in question has about a million writes to it. Hopefully I just have to wait for it to finish and I'll be in good shape. Thanks guys!
  4. Sorry for the confusion Johnnie, I moved everything off the drive and then formatted it. So it sounds like I should format the disk and then use the parity to reconstruct whatever was on that disk, right? What are the steps to do that? I want to make sure that if I format the disk that unraid will use the parity to reconstruct the data that was on there instead of just updating the parity drive to reflect an empty drive there.
  5. I did not reformat the disk. The original error occurred because I upgraded unraid version and there was an issue with permissions on one disk ( because I copied stuff manually onto the disk, most likely.) The solution which allowed me to upgrade to the latest unraid, was to use unbalance and move everything off the drive in question and only once it was all off, format that disk and then upgrade. I am getting the same error now even when I use the old version, which I previously was able to use unbalance with.
  6. Sorry about that, here are my diagnostics. Was I correct following up on my older post instead of making a new one since it is related? If I violated a forum guideline, sorry about that! alaska-diagnostics-20180324-1405.zip
  7. Sorry to resurrect a dead post but I was able to successfully upgrade to the latest unraid and run for a month. After shutting down the system to move it, I am getting the same error again "unmountable: Unsupported partition layout unraid". This persists even if I downgrade to the unraid version that previously worked. Could anyone help me figure out what is going on? Thanks so much!
  8. Thanks, I tried using unbalance and I received an error that recommended I run the "docker safe new permissions" command. I ran Tools => Docker Safe New Params a few times but I still get the same unbalance error. Is there more forceful way to run it this? I can tell that they are folders I manually copied stuff to about 6 months ago so I bet I was responsible for the permissions being a little screwy.
  9. Sure this is what I saw: Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 3D911163-D53C-43C3-9EE3-FE9CD80ABDEA Device Start End Sectors Size Type /dev/sdb1 64 5860533134 5860533071 2.7T Linux filesystem
  10. Okay that's good to know, I'll hold off on any updates for now. Thanks so much for taking a look, here they are! alaska-diagnostics-20180210-0909.zip
  11. Ha, you are amazing- downgrading now shows all my drives as mounted. I can tell that I went from 6.3.5 -> 6.4.1. Should I just avoid this upgraded version? Do you think that I'd likely get the same problem if I upgraded a second time? Thanks!
  12. I unfortunately upgraded over the internet by clicking the upgrade banner that showed upon the website. I can't recall which version I had before, but it was likely the previous version of the software. Is there a way I can downgrade since I did it that way instead of copying over files?
  13. I just upgraded to unraid version 6.4.1 and after installing, I now have 1 drive that is unmountable unsupported partition layout. I know that I recently did a parity check that passed (8 days ago), so hopefully I can just restore but before I do something potentially stupid, could someone please give me advice on what to do next? Thanks! alaska-diagnostics-20180209-2153.zip
  14. Oh that's good to know, I'll have to keep an eye out for that.
  15. Thanks so much, that allowed me to log into the web portal!