Jump to content

MichaelHawk

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

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

MichaelHawk's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Oh, I see.. Well that probably messed up my emulated disk. But one thing I don't understand though, when my disk first crashed everything became unreadable instantly. As I stated earlier, I first tried restart the array but the disk wouldn't mount. At that point, shouldn't I still have been able to access my files from the emulated disk? Either way. Is there a way fix my failed drive? I found this thread with almost the same issue: Difference is that I can't mount my drive with UD. The drive is listed under /dev as sdb but without the partition. Whats the next step here? Is it possible to clear the disk log without mounting?
  2. I'm sorry, but I don't understand what you are referring to. I never formatted the old drive. I formatted the new drive before adding it to the array and starting the rebuild. I don't see how that is relevant. Please help me understand.
  3. Yeah, I formatted the new disk before adding it to they array and starting the rebuild. But that shouldn't matter right? Since it's a completely new drive. The old disk is not formatted.
  4. The diag is from before I inserted the new disk. t30-diagnostics-20190828-1718.zip
  5. Are you suggesting I should try and repair the failed drive? If so how? My array is currently rebuilding a faulty parity. So if I were to connect my old drive to the old slot, wouldn't the parity delete my old data (if it still exists). Or should I connect it to a new slot, or would that mess up my array? I'm sorry. I'm not nearly smart enough for this. But I appreciate all help I can get!
  6. My array looks like this: Parity drive - 4tb Drive 1 - 1tb Drive 2 - 4tb (failing) So this happened two days ago. All of a sudden most of my files became unreadable from shares. So naturally i logged on unraid and noticed a bunch of error messages (i only have browser notifications enabled. I know iknow..). Apparently one of my disks had a bunch of read errors and some write erros aswell. At first I tried to restart the array and the failing disk had a big red cross over it and there was a messages saying something like ”unrecognized file format”. Oh well. At this point 90% of all my data was missing from the share. I stopped the array once more and went out and bought a new disk. After preclearing and formating the new disk I added it to the array, same spot and everything. Unraid noticed it as a replacement disk and would start a rebuild when starting the array. So I did. At this moment the rebuild is in progress, it states that my files are emulated but my files are still missing. What did I do wrong? t30-diagnostics-20190826-2052.zip
  7. So my boot drive died and I lost all my configs along with it. How do I proceed with restoring the array? I have 4 drives in total, 2x 4TB HDD, one 1TB HDD and a 120gb SSD Cache. I'm pretty positive on which one was setup as parity, but I'm not 100% on the order on the other two drives. Also, all my drives except the cache drive are encrypted. Does that complicate things? I created a new usb boot device and booted up the server, and all my disks are there. What's my next step? Is it safe to start the array in the order i'm somewhat sure about? I'm new to unraid, this community and homeservers in general, so please be gentle! :)
×
×
  • Create New...