youngnapoleon

Members
  • Posts

    14
  • Joined

  • Last visited

youngnapoleon's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I know this is old, but just wanted to thank you because I was really stressing out & this saved me big time. God/Allah/Bob Dylan/all of them bless you.
  2. Yeah, this is a problem for me, too. As I correctly assumed (though desperately tried anyway), creating "DATA_PERM" variable as 770 (as stolen from DeezLoader) didn't help... surely there's a way? For now I'm just setting New Permissions nightly & editing the next day. Did you get this working? Have you tried forcing an update? I know they're making fairly constant changes & I was having some issues even with the non-docker version that I'd intermittently have to reinstall/redownload to fix.
  3. Probably worthless advice, but have you cleared the cache?
  4. Sorry to take so long! It was something I actually already posted on here about: https://forums.lime-technology.com/topic/58394-drives-randomly-missing-cant-rebuild/ Serial Number: WD-WCC4E2ZZFYAH 5 Reallocated_Sector_Ct 0x0033 133 133 140 Pre-fail Always FAILING_NOW 1963 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 24 tbh I haven't really turned it on since & am yet to arrange for the RMA. Starting a new job on Monday & am gonna just buy a new 4TB to take its place before I send it away. Direct link to diag if you're still interested https://forums.lime-technology.com/applications/core/interface/file/attachment.php?id=28757
  5. Luckily I'm asking this one in advance - my unRAID is currently out of commission due to a near-instant failure of a drive during my trial run haha I'll definitely check out that drive cage, thanks
  6. Great! Well, thanks a lot for your help, I think I've been set straight
  7. Okay, that makes sense. Can the data be moved to the remaining drives from the emulated state?
  8. Thanks for the response! What would my options be then? Obviously, if a disk with 1TB of data had to be removed due to damage etc, the whole point of the parity is to be able to reconstruct it on a replacement disk. Is there no way to redistribute the data around the already-present disks without having to physically install another?
  9. Hey guys, so I just wanted to 100% confirm, say I have 5TB of data total in the array, & a mashup of disks (for this example, 3x 2TB & 1x4TB), if I removed the 4TB disk (which does have at least 1TB of data on it) & then followed the removal instructions at https://wiki.lime-technology.com/UnRAID_6_2/Storage_Management#Removing_disks ...this is doable, right? The data just redistributes itself to the other disks? TL;DR: As long as you have enough total disk space for your data, after removing a disk, a parity-sync will redistribute the data without issue? Thanks guys!
  10. First time it's been used, but unfortunately bought them last September, not thinking it would take so long to get the rest of the hardware
  11. Damn, thanks for the heads up. Both disks were brand new. I've never RMA'd a disk before, guess it's time to start Thanks again trurl!
  12. Yeah, yesterday when I originally built it, it took about 8 hours. I can't remember the speed, but I think it was well over 100mb/s. Now it is going very steadily ~36mb/s. Having said that, over an hour in & no errors.
  13. Thanks for your reply! I didn't read too much about preclearing, so I for some reason assumed it was similar to formatting After the successful boot with the cache I tried unassigning/reassigning once more, & despite it being ridiculously slow, it's been running for more than an hour now Diagnostics attached, thanks again! illmatic-diagnostics-20170628-2214.zip
  14. Hi guys! This is my first post & apologize a) for the length & b) for the likely large amount of mistakes I committed today. The main one being multiple reboots without saving syslogs – I’ve since read that this is probably my demise. I got unRAID up & running last night & was happy with it, just threw on a few gigs of test stuff in a few different shares & created the primary users. Today was going to be spent doing The Big Transfer, buuuut I’ll sum the issue up in dot point: (2x WD Red 4TB drives, one parity, one disk. 120GB SSD for cache & Sandisk Cruzer USB connected directly to the motherboard as recommended.) While moving files from an external HDD (using Unassigned Devices & Krusader), I paused the transfer with the Krusader GUI. Krusader froze, & then the unRAID GUI also became unresponsive. I waited over half an hour but could get no response from either. Fearing the HDDs may be encountering errors & leaving it longer may be damaging them (plus feeling hopeless after half an hour of nothing), I force restarted the PC. Back up, Disk 1 had the red cross next to it & was being emulated. I was fairly sure the data was still there. I removed Disk 1 & tried attaching it as an unassigned device & also to a Linux VM on my main machine – neither would read. This turned out to be due to my cheap ‘SATA to USB’ cable I’m pretty sure, but I’ve included this step just in case. With the parity seemingly fine & all files still accessible, I tried rebuilding by unassigning & reassigning Disk 1, stopping & restarting the array in between. This kicked off alright, but at ~0.6 percent, hit a read error on Disk 1 & aborted itself. I tried this a couple of times. I found a forum post saying to check the SATA cable – though it had failed before this, I HAD played with it, so made sure everything was snug. Same result. I tried rebooting a few times, beating my head against a wall. Weird things were happening. Both Disk 1 AND the parity drive would randomly appear as unassigned devices as if they were external. The mount option was there, but did nothing. After awhile, it got to the point where both Disk 1 & parity were simply not recognized. The flash & cache drives were both fine. Note that despite the parity acting up in different ways, I had never really done anything with it. Frustrated as all hell, I unplugged the SATA & power cables from the cache SSD & plugged them into the parity drive. Booting up, the parity is now apparently fine & dandy, AND Disk 1 is being recognized again, but still with the red cross. The cache is currently not connected at all. I’ve gone from working happily to seemingly having lost the ability to read the 2 hard drives & everything in between today, so figured with the parity alright & Disk 1 at least being recognized, I should turn to the forums. I imagine all the fooling around I did was dumb before asking you guys, but I’ve never really had trouble I couldn’t fix myself until now. Every time I rebooted (except for that one fateful hard boot), I stopped the array & used the proper shutdown procedure. Also note the machine is headless – I can SSH into it, so I guess it’s not a problem. I just really really don’t want to have to pull the GPU out of my main PC & stick it in this one again, so hopefully it’s nothing in the BIOS haha. Anyway, sorry for the long post, thanks a lot for reading! Let me know if you have any suggestions Edit: Couldn't help myself, rejiggered the cabling & attached the cache SSD. All drives showing fine except Disk 1. Would possibly the easiest way of fixing this/determining whether there's something wrong with the HDD itself just be to format it using Preclear or something?