anthropoidape
Members-
Posts
96 -
Joined
-
Last visited
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
anthropoidape's Achievements
Apprentice (3/14)
1
Reputation
-
[support] Vaultwarden (formerly Bitwarden_rs)
anthropoidape replied to Roxedus's topic in Docker Containers
Thank you this worked for me on unraid 6.11.5. I can now update VW. -
DiskSpeed, hdd/ssd benchmarking (unRAID 6+), version 2.10.8
anthropoidape replied to jbartlett's topic in Docker Containers
Just following on though, this is something I don't think I have seen before when running diskspeed: The drive is an old 2TB platter type, is it correct that it is trimming? Also it looks to be stuck on 0%. This drive has not benchmarked, either. Edit: this drive seems to be getting detected as a SSD... -
DiskSpeed, hdd/ssd benchmarking (unRAID 6+), version 2.10.8
anthropoidape replied to jbartlett's topic in Docker Containers
Hi, I was getting the "unable to benchmark" error, nothing to do with NVME though. It previously benchmarked as recently as 18 December as you can see. I added the variable suggested above to the docker, and now this drive is available to benchmark. Just thought I would let everyone know in case others hit the same problem. -
Advice on rectifying failure please
anthropoidape replied to anthropoidape's topic in General Support
Okay rebuilding parity as all data drives seem to be intact. After that I'll do the disk swap that was the original plan. I am not really clear on what went wrong, still scratching my head a bit. -
Advice on rectifying failure please
anthropoidape replied to anthropoidape's topic in General Support
To reply to myself again - I have mounted both the old disk 4 and the old disk 7 in unassigned devices and they both seem to be perfectly readable with no data loss. Therefore it seems like I should recreate the old array, disks 1 to 7, and then rebuild parity based on the actual disk contents. Is that right? I am not going to do anything just now as I have to do some other stuff. Would appreciate suggestions. Sorry about the multiple posts, you know how initially you kinda panic right -
Advice on rectifying failure please
anthropoidape replied to anthropoidape's topic in General Support
Apologies, the precise error is: "Unmountable: Wrong or no file system" -
anthropoidape started following newznab + unRAID integration? , Advice on rectifying failure please , Set up USB, then add existing array... can I do this? and 6 others
-
Hi all, I have just had an unexpected failure. I had this array, all good: When I recently replaced disk 6 (successfully, no problems at all) I noticed that Disk 7 is not only old but slow. Therefore I bought a new 4tb drive to gain speed and some more space. I added that drive just now, in place of disk 7. I did this while unraid was shut down of course. I will call that shut down Timepoint A. As I commenced the array rebuild, disk 4 failed, with unraid stating that it doesn't have a readable file system. SMART attributes show UDMA CRC error counts, so I have replaced and reseated cables etc. The problem I have is that since I did start the rebuild on the new disk 7, unraid now thinks that both disk 4 and disk 7 are new disks. Even if I put the old disk 7 (the 2tb drive) back on, it sees that as a new disk as well. So now it tells me I have too many wrong/missing disks. It seems to me like I should be able to put the array back as it was and rebuild disk 4, as nothing should have been written to any of the drives since Timepoint A, except for maybe some attempted writes to the new disk 7 that is not involved in the rebuild I want to do. Am I right, and if so how do I make unraid accept the disks as correct (ie specify parity, d1, d2, d3, d5, d6, and d7 as good and treat d4 as new)? Otherwise, what's my best bet here? There is over 3tb on disk 4 that I'd rather not lose if possible.
-
[Support] Linuxserver.io - Calibre
anthropoidape replied to linuxserver.io's topic in Docker Containers
Thank you very much for this. I have working calibre again... -
I can confirm that (a) QSV encoding also broke for me in a recent update, and that (b) reverting to v1.23.2 rectified this.
-
I have spent the last few days tinkering with my unraid server, and it prompted me to see how old this thing is. So it turns out I bought my pair of unraid licences back in June 2010, more than eleven years ago. Since then I've updated the motherboard/cpu, case and PSU once each, and had to update the usb sticks one time as well. I've gone through a few hard drives but there are still a couple of WD Green 2TB drives that I think are from my original setup. One has over 10 years of power-on time recorded in SMART. The newest drives are 2 x 4TB Iron Wolf as parity and disk 1, along with a bunch of older 3TB and 2TB drives. Originally all I wanted was a cheapskate NAS, storing files and serving up video to a Popcorn Hour, then later to a XBMC PC. But since dockers became available.... totally different beast. The last few days we've been in yet another Covid lockdown with dismal weather as well, and then I got this message that lastpass is going to be either costly or useless. So I just puzzled my way through setting up SWAG and Vaultwarden. Then I added a calibre docker (I was previously running calibre on a VM, which can now retire in favour of the docker.) Then I added LazyLibrarian, and set it up so a few family members can log in and email books directly to their own kindles instead of asking me to do it. And then a friend wanted to grab some files from me so I added Nextcloud (not that there aren't other ways to flick a file over). So here is what my tween-aged unraid server does. Radarr -> Sab -> Plex for movies Sonarr -> Sab -> Plex for tv series NZBHydra2 (with NZBGeek, OzNZB, NZBFinder) Plex for a few other videos like some guitar lesson vids, family home videos etc Handbrake, set up to resize video files automatically as they are often unnecessarily large for my purposes Calibre just to download a magazine every week and email it to my e-reader LazyLibrarian so a couple of family members can locate and send books to their e-readers Vaultwarden for self-hosted passwording Pihole (one of two, the other instance is on an OrangePi for redundancy) Nextcloud (not sure what actual use I will have for this, but whatever) Also installed are diskspeed, speedtest, and a few other purely local utilities. It's impressive how very easy almost all of these were to set up. There was a bit of a learning curve with reverse proxy and a bit more fiddling with LazyLibrarian than with most dockers to get the functionality I wanted (automatically converting ebook file types in particular) but mostly it is a walk in the part. So I really think that my unraid licence is one of the best investments I've ever made. Now putting on SWAG was the first time I've opened up a port to the wider universe. I am a little apprehensive about it. It serves up only LazyLibrarian, Vaultwarden, and NextCloud. For security I have enabled and tested fail2ban for VW and NC (but not LL, which has inbuilt ip banning after three user/password attempts and at last check didn't log IPs for failed login attempts) and geoblocking to confine access to my own low-risk country. SWAG also runs on an odd port, rather than port 80 or 443, so it's relatively obscure. Still, I am not that well informed on security. Should I be doing more?
-
Lost disk assignments after power failure
anthropoidape replied to anthropoidape's topic in General Support
I am running 6.1.9. It seems there's no harm done. Most of my array is 2TB WD drives, but parity, cache, and non-array drive all happen to be distinctive so it was easy to reassign drives and get going. The array drives other than parity are presumably not in the same order as before, because I couldn't find my printout of the assignments (I usually do keep one). -
Lost disk assignments after power failure
anthropoidape replied to anthropoidape's topic in General Support
Well, I just assigned the disks including parity, cache and non-array drive, and all is well - doing a parity check just like a new config, but dockers and VM are all fine which was my main concern. Odd. -
I have been UPS-less for a while, unfortunately, and a power drop out today created a problem. On power up, I simply have a big list of unassigned disks and unraid not running. I am afraid I rebooted before grabbing a syslog. But where is the disk assignment info recorded? I for some reason thought it was in disk.cfg but it doesn't seem to be. What could have caused unraid to lose this info? I can't see any signs of corruption on the memstick. Jason
-
Much the same here. I have a small VM running XP that handles a number of tasks that I really like to leave running 24/7, but that I can't yet find a docker for, or that just happen to be easier to run this way. It has Calibre downloading some periodicals for me, a gmail pop3 checker running in chrome, and a few other things. I am about to set up a selective dropbox sync on it as well, and I will probably set up google drive at the same time. I would like to have a google drive docker but since I need the VM running, this is a pretty reasonable solution.
-
Has this been explained yet? I have been getting this message the last few days. I just got it with no dockers running. It doesn't seem to have any effect other than to mess up the display on Midnight Commander if I happen to be using it.