WonderfulSlipperyThing

Hi, I've had my unraid setup using HTTPS for a while now using Settings>Identification>Management Access' settings. It works well for the most part, however if the internet connection goes down the web UI is inaccessible. I don't think this is a bug - obviously things like Let's Encrypt are dependent on an internet connection. However, I was wondering if there was a way around this for when the internet connection goes down? I've tried connecting using http://x.x.x.x:80, but that just redirects me to the HTTPS version. Right now the only way around this that I can tell is to SSH into the system and changing USE_SSL auto to no, then restarting the server, but that's fairly cumbersome. Does anyone have any nifty solutions to this issue or am I stuck being dependent on an internet connection for smooth operation of the server's web UI? Thanks!

That worked, thanks!

I'm getting the same thing - hit the button and nothing happens. I just emailed the dev about it then realised I could just check the forums. Out of interest what device are you using? I'm using a Galaxy S9+

Thanks for the writeup. Presumably auto in the future will use turbo write if all the drives happen to be spinning already. All of my drives are currently spinning but auto is still using read/modify/write which is why I came to this post, didn't realise that feature wasn't actually implemented yet. It's a great feature and works very well but I'm really looking forward to being able to get better control over it. If all the drives are spun up already it would be great if it just used reconstruct write. Also I think for many people they don't really care that much about write speeds unless they're actually actively doing something themselves so having it just enabled for SMB shares or something would also be really useful. Either way thanks for the explanation, makes a lot of sense and seems to make a huge speed difference!

That's a good idea. Looked around and found the command (b2sum), you can specify the hash algorithm (running b2sum with no args even gives you something to copy paste into a shell script for loop). So I gave it a go with an 11GB file and these are the results I got: blake2b - 1 core: 93MB/s blake2s - 1 core: 167MB/s blake2bp - 4 cores: 315MB/s blake2sp - 8 cores: 620MB/s Judging by those stats the plugin is using standard blake2b. All of them maxed out whichever cores they were using (except for blake2sp which seemed to use around 85% of each). It would be great to have the option to use a different blake2 algorithm as it clearly makes quite a large difference, at least on my system (which I believe is fairly popular). Of course I'd rather not make writing files to the array quite that intensive so I'd probably use the blake2bp just so there's a little CPU wiggle-room left for other tasks, but it's always nice to have options!

Interesting, probably just a quirk of my processor then. I did a quick Google search for "C2750" and "BLAKE2" and came up with this https://github.com/minio/blake2b-simd/issues/11 Not sure if that's the blake2 algorithm this is using (or if the problems posted there are related to my slow speeds) but I would guess that it's something to do with the "Seems to indicate that there's some kind of performance penalty on Atom when executing SSE with 64-bit operands" comment. Thanks for the benchmarks, always useful to have. So I guess for most people, BLAKE2 is probably the best option but for us Atom users, probably best stick with MD5.

To anyone in the future interested in this, I did some very basic testing of this by creating a user share with a few files in and excluding every other share, then doing a build in order to find out which was fastest on my processor. Interestingly it doesn't seem like any of them are multi-core optimised (and I guess the build only does one file at a time, at least if they're all on one disk). I got 100% CPU load on one core of my processor whichever algorithm I used. At the end, the build gives you an average speed. I ran all the tests a couple of times with all different files and this is what I got: SHA1: Was around the 90 MB/s mark (unfortunately can't remember the exact results) BLAKE2: 93 MB/s MD5: 323 MB/s So if anyone wants to install this plugin and their primary concern is speed, at least on the C2750 8 core atom, MD5 is by far the fastest to use. I find it crazy that BLAKE2, which is supposed to be the fastest, is less than a third of the speed of MD5, but this may well just be a quirk of the C2750 processor.

Thanks for all the input guys. Just a quick update here but I have now moved over to unRAID and I'm loving it - it's such a user friendly OS and really it's perfect as a home NAS solution. The thing I love about it is that it can be as simple or as complicated as you want it to be and the learning curve isn't particularly steep. When I used it before I always thought it was pretty good but it has improved so much in the past couple of years. Then yesterday I saw that 6.2 final is out and it looks fantastic (haven't updated yet though). I love that there's now an officially supported turbo write option as for many people the ONLY disadvantage to unRAID is the (relatively) slow write speeds. Now that it can saturate gigabit, write speeds aren't going to be much of an issue for most home users. Now I'm just debating whether to move some disks over to my Marvell controller so that I can spread the bandwidth a bit more equally. Currently my only disk on the Marvell controller is my SSD cache disk (that I'm not using as a cache disk, just using it for docker etc). I have looked around and I see that there's a thread about Marvell issues... it seems reports are somewhat conflicting as some people say that doing a firmware update doesn't fix the issue. But maybe that's just for other boards. dmacias said that all that's needed is to update the controller and mobo to latest so I guess I'll give that a go. Haven't spotted any issues on the SSD but that's not hit as much as the array disks. Either way, incredibly happy with it all, and all of my dockers run really well. The community applications makes life so much easier and I like that they all actually update properly (and issue I had on FreeNAS was that many of the plugins, of which there weren't very many, had various issues with things like updates).

I have a basic license so 6 devices. I understand why it's happened it just seemed a bit silly to me that something like an external USB drive is limited by your license. I didn't realise that USB disks were allowed to be part of the array so that makes a little more sense, but the fact is, while the device was present, it wasn't set to be part of the array or a cache drive, it was just connected to my system (and preclearing but not doing anything array-ey). It was a bit alarming when I stopped the array only to find I couldn't restart it! In the end I just stopped the preclear, disconnected the USB disk, and started the array again. I imagine this is a bigger problem for people who have a 6 drive array (or 5 drive array and a cache disk) then have a failing disk as they can't preclear a disk at all if they want to start their array.

This is awesome! What a great list of features to suddenly (from my perspective) arrive so shortly after I've started using unRAID again. I was hoping some kind of vlan functionality would be added and as I've only recently set up unRAID I hadn't really looked into the 6.2 RC or anything so all of these features are a nice surprise to me. Quick question - the post says "If you are using plugins, please see this thread regarding plugin support." I see no mention of any changes between 6.1 and 6.2 so I assume I'm OK to just go ahead and update from 6.1 (6.1.9..) straight to 6.2 without affecting my existing setup?

This looks like it'll be a great plugin and I've installed it but not set it up yet (as my server is currently doing some fairly intensive stuff and I don't want to complicate matters). As this plugin has been out a little while now, I was just wondering if anyone had any experience with which hashing algorithm to use on an Atom processor with the least performance impact? I have an Intel C2750D4I - it's not the most powerful processor ever but it's perfect for my usage scenario. The last thing I want, however, is for something to start writing to the array while I'm watching or transcoding something in plex and for it to interfere with that so it's pretty important to me that I use the hashing algorithm with the least performance impact. I see that blake2 is supposed to be the fastest of the bunch, but I also saw somewhere that you have to make sure your processor is compatible (plus sometimes things are fast on some processors but not on others). If anyone has any input on this, especially if they've used it with an Intel Atom C2750, I'd really appreciate it as obviously hashing all of my storage 3 times to find the fastest one would take a long time when someone's probably already got some information available!

Ah thanks, that's basically the answer I was looking for. So technically it's not locked to the original repository it was installed from, and the developer has the option to allow the update to use the non-beta repo. Good to know!

Hi, I have an array set up (without a parity disk currently, that's fine, I'm aware of the risks etc. it's just that the parity disk is large and takes a while to preclear, plus copying data to the array is way quicker pre-parity). I have had it all up and running just fine for a while, however, yesterday I decided to attach a faulty disk via a USB dock to preclear it and force some sector reallocations before it's RMAd. Earlier, I stopped the array, only to find that now I can't start it again as I've gone over the limit of "attached devices". I understand that the license is about how many devices arr attached before the array starts but surely it's a little over the top to prevent additional devices that aren't part of the array from being attached, especially if it's a USB disk that I'm preclearing? Effectively this means this - if you're at the device limit and you get a failing drive you want to replace, if you decide to attach a USB disk to pre clear it, whatever you do DON'T STOP THE ARRAY while it's pre clearing as it'll count as an attached device, preventing you from starting the array again until it's precleared. FYI this is the only bad thing I've actually had to say about unRAID since installing it - I used to use unRAID before until a couple of years ago and I'd forgotten how much I loved it, very glad I came back. There have been a lot of noticeable improvements since I last used it.

Thanks, didn't realise that existed. Will check it out. Although looking on unRAID, Nextcloud on unRAID is also in beta so my question still applies.. will it automatically update to the non-beta version when that's available or will I have to set everything up again? If I do have to set it up again, is it as simple as just deleting the docker, getting the new one, and using the same appdata config directory?

I've just set this up because without it, Headphones is painfully slow... anyway, it completed it's stuff (from what I can tell) within a couple of hours and I can access the server's web interface just fine. But Headphones is still taking absolutely ages to actually get anything out of it. Just a few questions... When the web interface is available, databases searchable etc., is it done? Or is it still doing stuff in the background? Do I have to manually enter any commands to get the database to optimise or to build a search index? Is there any way to easily test API calls into it? ...or is it just that Headphones is insanely slow and there's nothing anyone can do about it? These are the last few lines I see in the log, and there hasn't been anything since: Mon Sep 12 13:53:41 2016 : Creating search indexes ... (CreateSearchIndexes.sql) Mon Sep 12 14:09:33 2016 : Setting up replication ... (ReplicationSetup.sql) Mon Sep 12 14:09:33 2016 : Optimizing database ... VACUUM Mon Sep 12 14:11:09 2016 : Initialized and imported data into the database. Mon Sep 12 14:11:09 2016 : InitDb.pl succeeded INITIAL IMPORT IS COMPLETE, MOVING TO NEXT PHASE LOG: received fast shutdown request waiting for server to shut down...LOG: aborting any active transactions .LOG: shutting down .........LOG: database system is shut down done server stopped [cont-init.d] 30-initialise-database: exited 0. [cont-init.d] 40-config-redis: executing... [cont-init.d] 40-config-redis: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [614] 12 Sep 14:11:20.992 # Server started, Redis version 2.8.4 [614] 12 Sep 14:11:20.993 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. Thanks in advance. All of your plugins for unRAID are awesome by the way!

Hi, I've almost finished setting up all the apps etc. that I want running on my unRAID server and it's all going pretty well but I have a fairly simple question regarding beta applications. If I install a beta application, what happens when it comes out of beta? Does the beta move into a separate kind of "dev" branch so it keeps updating to bleeding edge or will it just automatically update to the final once that's released? I'm looking at installing the linuxserver.io ownCloud plugin. All of my other plugins are linuxserver.io and so far I've found them to be consistently good, reliable and, importantly, updated/maintained, which is why I was planning on installing the linuxserver.io version rather than the other non-beta ones (no discredit to the other plugin devs, they've all done a great job and I have used the other ones, but right now linuxserver.io ones seem to be the most up to date).

Wow that's surprisingly fast uncached write speeds for unRAID! I guess my old hardware was generally really slow and maybe some optimisations have also been made in unRAID too. Either way, sounds very promising. A couple more questions come to mind... 1) You mentioned using an SSD for the cache disk (as did I) but obviously I'm worried about degrading performance, especially for something that's mostly transitory and will get a lot of writes. Do we know if/when some form of TRIM will be implemented for cache disks? 2) Anyone else have the C2750D4I or a motherboard with Marvell SATA ports? I'm currently only using the Intel SATA ports on my mobo but if I add a 7th disk (SSD) I'll need to use one of the Marvell ports, which were apparently somewhat problematic on FreeNAS (hence why I avoided them).

Thanks for the info guys! In terms of question 2), I know that my processor (despite being atoms!) can easily handle multiple 1080p streams as I've been using it in FreeNAS for a while, and I have seen reports online of people using it to transcode 3 simultaneous 1080p streams, it was more about whether running in Docker in unRAID would have a significant performance impact vs FreeNAS but it sounds like that won't be an issue at all. Similarly (although I didn't mention this) I was a little worried that if I didn't have a cache drive in, there might be a storage bottleneck for transcoding but it doesn't look like that would be the case (but I have just found a post on these here forums that it's possible to move transcoding storage to the RAM, which is definitely something have plenty of!) Anyway all great stuff and that pretty much answers all my questions! If anyone has anything else to add, especially question 3, I'd really appreciate it as it looks to me like unRAID has actually come a fairly long way since I stopped using it.

Hi guys, I used to run unRaid until a couple of years ago and actually really loved it, however I moved to FreeNAS for write performance speed reasons (at the time I couldn't fit a cache drive into my box as there was no space and I kinda stuck with it). I do like FreeNAS and it's very good for certain things, but I'm leaning towards going back to unRAID because: It's way of using parity without striping as I feel less nervous about my data - if 2 drives go, I can still access the rest It's much more flexible in terms of drive sizes etc. The community, from what I recall, is awesome (though just to be clear that's not a slight against FreeNAS as they have a pretty responsive and intelligent community too) As far as I can tell, unRAID would likely reduce my electricity bills slightly and may (*may*) result in longer lasting hard drives as they don't need to be spun up all the time. Then again, spinning up and spinning down may be more damaging than just leaving them permanently spun up so I'm not sure about that point Anyway, I'm considering coming back to the unRaid camp but just had a few questions. Firstly my hardware: Motherboard - ASRock C2750D4I Processor - SoC on the mobo - it's an 8 core Atom C2750 RAM - 32GB ECC RAM (needed ECC for FreeNAS) - 4x8GB sticks Hard drives - 6x3TB WD Reds Cache drive - I'll probably see if I can fit in a 500GB SSD - apparently it is possible to mount a 2.5" SSD on the outside of the HDD brackets in my case, even though technically the case says it'll only hold 6 drives. I'll likely use the cache drive to run all of my applications from (e.g. Plex) Chassis (not that this is relevant but hey!) - Fractal Node 304 1) Does anyone have any recent performance benchmarks for unRaid? The user benchmarks page on the wiki has a lot of pretty old data and it would be great to see some updated info, esepcially with 3TB WD Reds. I'm talking write speeds once the cache has been filled - my old server used to write at about 15MB/s, it was incredibly slow. I'm just curious as to what kinds of speeds people get with writing data as chances are I'll have a few scenarios where I'm writing more data than the cache can hold. 2) How is Plex on unRaid these days? When I used to run it I think it ran just normally on the OS, however now I see that a lot of unRAID stuff is in Docker. Has this had any negative impact in terms of performance? I never used to be able to transcode but that's because I had an old N40L. Now on my FreeNAS setup with my current I can transcode pretty much anything just fine. Can I expect the same on unRAID? From what I can tell, I think FreeNAS maybe has more of a CPU/memory performance overhead than unRAID but just wanted to check. If anyone else has similar hardware with unRAID running Plex, I'd really love to hear your experiences. 3) Has much else changed in the past 2-3 years that I'm missing? I did a very simple setup of unRAID a year ago when I gave my Dad my old N40L and it seems like a lot has changed - all of it good, but I didn't have much time to delve too deep into it. The UI looks way better (and no more installing SimpleFeatures after the fact which is nice!) and it has docker but I could easily be missing loads of stuff. 4) Not a biggie but does unRAID make any use of ECC RAM? I have ECC so would just be nice to know that it's being used! EDIT: Wow, completely forgot I had such a weird username on here. Guess I was listening to a lot of Guthrie Govan at the time but it just makes me sound like a fancy snake.

Oh also - does setting plugins to "enable" mean that they're installed on startup, or that they're started on startup (with them being installed whether or not they're enabled). Because again obviously I could put a delay in the go script to run the program with a delay, but I'd need to know: a) if setting it to disabled still installs it, then I'd just need to put the run command in the go script with a delay b) if setting it to disabled does not, I assume I'd need to do "installplg", in which case, does it automatically start when unRaid starts?

I've seen a few people mention that you need to get unRaid to delay the starting of some things otherwise they lock up the array on startup and it never finished starting (I have experienced this myself). I was just wondering how you go about this? My array doesn't start up automatically when I boot up the system for some reason so that makes it somewhat inconsistent. I guess what I'm really asking is: 1. How do I get my array to auto-start on boot? 2. Where do I add delays for installation of plugins (.plg)? I see that packages are installed in the go script, so I guess I could easily just add a sleep to the go script, but see no mention of where plugins are installed. 3. Is there a script which runs once the array has finished starting which I could append the installation commands to? This seems like it would be the best solution as it would mean that if the array doesn't start on boot (which, as I said, mine does not) then it won't run these scripts until the array has finished starting. 4. This is more of a general question, but why does the cache drive need to be started as part of the array? Can't it just be automatically mounted on boot?

Sorry to triple post but they're all significant updates. So now I just had the exact opposite problem in that the array would not finish starting. It was of course plugin related again - just curious as to how I go about adding a delay on plugin initialisation on startup? The general advice I've heard is simply "add a delay" with no indication as to how. I looked in the /boot/config/go script and there was no mention of plugins. Or better still a way to get whatever program/script tells emhttp "the array is now started" (it goes in the syslog so there is clearly some kind of signal) to also say "now is probably a better time to start plugins than when we start starting the array".

It seems even my server is now bored, all drives except the cache drive have now spun down. I assume the cache drive is still spun up because I had to kill a few things that run from it a little while after. Though here's a thing - why does the cache drive even need to be unmounted when the array stops? Maybe I should just remove it as the cache drive and have it permanently mounted for my apps. EDIT: It eventually stopped. I went through trying a load of different things, including killing the cache_dirs process, and even doing a ps for "bash". Saw that there were a couple of notify things running (including a sickbeard one for some reason, a command telling sickbeard that the array is shutting down despite the fact that sickbeard was already dead), and killing that was the final straw that eventually lead to the array shutting down properly. Either way, it seems that it's caused by a load of random things, half of which I can't even remember, needing to be killed. I'd mark this as solved but really it's not..

When stopping the array, the web UI says: Stop SMB...Spinning up all drives...Sync filesystems... And just sits there. I've had this once before and I got fed up and just powered off, but of course it had to parity check on the next startup so I'm somewhat reluctant to do that again. Plus it's hardly a healthy solution. Anyway, the HDD indicator light doesn't even blip which implies it's not touching the HDD.. All my apps are stopped (plex, sickbeard, transmission, couchpotato, sabnzbd) although occasionally on the cache drive I see root@Tower:~# lsof /dev/sdd1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME find 14465 root cwd DIR 8,49 432 67882 /mnt/cache/.custom/plexlib/Application Support/Plex Media Server/Metadata/TV Shows/f/6aee27ae8da036af1f7d07b83ba669fc433cc27.bundle/Contents/com.plexapp.agents.thetvdb/seasons/2/episodes/8/thumbs . It's intermittent and I don't know what's causing it to run but most of the times I try lsof /dev/sdd1 it doesn't list it. unMenu says that the array is still started but SMB is down (obviously as that's the first step). It seems to kill the WebUI and also for some reason becomes inaccessible by its name and instead I have to contact it by its IP address. lsof returns nothing (quite literally): root@Tower:~# lsof /dev/sda1 root@Tower:~# lsof /dev/sdb1 root@Tower:~# lsof /dev/sdc1 root@Tower:~# lsof /dev/sdd1 I'm currently trying just disconnecting the network cable for 5 minutes but I doubt it'll do anything Syslog: Mar 7 22:36:44 Tower emhttp_event: stopping_svcs Mar 7 22:36:44 Tower emhttp: shcmd (133): ps axc | grep -q rpc.mountd Mar 7 22:36:44 Tower emhttp: _shcmd: shcmd (133): exit status: 1 Mar 7 22:36:44 Tower emhttp: Stop SMB... Mar 7 22:36:44 Tower emhttp: shcmd (134): /etc/rc.d/rc.samba stop |& logger Mar 7 22:36:44 Tower emhttp: Spinning up all drives... Mar 7 22:36:44 Tower emhttp: shcmd (135): /usr/sbin/hdparm -S0 /dev/sdd &> /dev/null Mar 7 22:36:44 Tower emhttp: Sync filesystems... Mar 7 22:36:44 Tower emhttp: shcmd (136): sync Mar 7 22:36:44 Tower kernel: mdcmd (43): spinup 0 Mar 7 22:36:44 Tower kernel: mdcmd (44): spinup 1 Mar 7 22:36:44 Tower kernel: mdcmd (45): spinup 2 Mar 7 22:36:57 Tower emhttp: shcmd (137): /usr/local/sbin/emhttp_event unmounting_disks Mar 7 22:36:57 Tower emhttp_event: unmounting_disks Mar 7 22:37:12 Tower transmission-daemon[20708]: Saved "/mnt/cache/.custom/transmission/conf/settings.json" (bencode.c:1721) Mar 7 22:37:12 Tower transmission-daemon[20708]: DHT Saving 156 (156 + 0) nodes (tr-dht.c:366) Mar 7 22:37:12 Tower transmission-daemon[20708]: Saved "/mnt/cache/.custom/transmission/conf/dht.dat" (bencode.c:1721) Mar 7 22:37:12 Tower transmission-daemon[20708]: Port Forwarding Stopped (port-forwarding.c:181) Mar 7 22:37:12 Tower transmission-daemon[20708]: Port Forwarding (UPnP) Stopping port forwarding through "http://192.168.0.1:80/WANIPConnection", service "urn:schemas-up np-org:service:WANIPConnection:1" (upnp.c:169) Mar 7 22:37:12 Tower transmission-daemon[20708]: Port Forwarding State changed from "Forwarded" to "Not forwarded" (port-forwarding.c:93) Mar 7 22:37:12 Tower transmission-daemon[20708]: Closing session Mar 7 22:37:14 Tower plex-rc.plex: Stopping Plex... Mar 7 22:37:15 Tower plex-rc.plex: PMS is still runnig Mar 7 22:37:15 Tower plex-rc.plex: PMS with PID 10670 killed Mar 7 22:37:15 Tower plex-rc.plex: PMS is still runnig Mar 7 22:37:15 Tower plex-rc.plex: PMS with PID 20462 killed Mar 7 22:42:05 Tower unmenu-status: Starting unmenu web-server Mar 7 22:43:36 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:44:18 Tower last message repeated 100 times Mar 7 22:44:29 Tower last message repeated 51 times Mar 7 22:45:17 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:45:32 Tower last message repeated 38 times Mar 7 22:45:37 Tower dhcpcd[941]: eth0: carrier lost Mar 7 22:45:37 Tower kernel: tg3 0000:02:00.0: eth0: Link is down Mar 7 22:45:48 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:46:17 Tower last message repeated 100 times Mar 7 22:46:25 Tower dhcpcd[941]: eth0: carrier acquired Mar 7 22:46:25 Tower kernel: tg3 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex Mar 7 22:46:25 Tower kernel: tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX Mar 7 22:46:25 Tower dhcpcd[941]: eth0: rebinding lease of 192.168.0.2 Mar 7 22:46:26 Tower dhcpcd[941]: eth0: acknowledged 192.168.0.2 from 192.168.0.1 Mar 7 22:46:26 Tower dhcpcd[941]: eth0: checking for 192.168.0.2 Mar 7 22:46:30 Tower dhcpcd[941]: eth0: leased 192.168.0.2 for 3600 seconds Mar 7 22:46:30 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:46:42 Tower last message repeated 75 times Mar 7 22:46:47 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:47:18 Tower last message repeated 134 times Mar 7 22:47:18 Tower last message repeated 24 times Mar 7 22:47:22 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:47:56 Tower last message repeated 167 times Mar 7 22:48:03 Tower last message repeated 67 times Mar 7 22:48:09 Tower dhcpcd[941]: eth0: carrier lost Mar 7 22:48:09 Tower kernel: tg3 0000:02:00.0: eth0: Link is down Mar 7 22:48:12 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:48:55 Tower last message repeated 100 times Mar 7 22:50:05 Tower last message repeated 168 times Mar 7 22:50:19 Tower last message repeated 66 times Mar 7 22:50:27 Tower dhcpcd[941]: eth0: carrier acquired Mar 7 22:50:27 Tower kernel: tg3 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex Mar 7 22:50:27 Tower kernel: tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX Mar 7 22:50:27 Tower dhcpcd[941]: eth0: rebinding lease of 192.168.0.2 Mar 7 22:50:28 Tower dhcpcd[941]: eth0: acknowledged 192.168.0.2 from 192.168.0.1 Mar 7 22:50:28 Tower dhcpcd[941]: eth0: checking for 192.168.0.2 Mar 7 22:50:33 Tower dhcpcd[941]: eth0: leased 192.168.0.2 for 3600 seconds Mar 7 22:50:34 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:50:44 Tower last message repeated 65 times Mar 7 22:50:50 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:51:26 Tower last message repeated 167 times Mar 7 22:51:48 Tower last message repeated 120 times Mar 7 22:51:52 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:52:28 Tower last message repeated 167 times Mar 7 22:52:51 Tower last message repeated 139 times Mar 7 22:53:32 Tower sshd[15163]: Accepted password for root from 192.168.0.9 port 49454 ssh2 Mar 7 22:53:32 Tower sshd[15217]: lastlog_filetype: Couldn't stat /var/log/lastlog: No such file or directory Mar 7 22:53:32 Tower sshd[15217]: lastlog_openseek: /var/log/lastlog is not a file or directory! Mar 7 22:53:32 Tower sshd[15217]: lastlog_filetype: Couldn't stat /var/log/lastlog: No such file or directory Mar 7 22:53:32 Tower sshd[15217]: lastlog_openseek: /var/log/lastlog is not a file or directory! Mar 7 22:53:34 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:54:10 Tower last message repeated 143 times Mar 7 22:54:40 Tower last message repeated 158 times Mar 7 22:54:46 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:55:16 Tower last message repeated 169 times Mar 7 22:55:21 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:55:58 Tower last message repeated 167 times Mar 7 22:56:19 Tower last message repeated 118 times Mar 7 22:56:26 Tower plex-rc.plex: Nothing to Stop Mar 7 22:56:58 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:57:28 Tower last message repeated 129 times Mar 7 22:57:34 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:58:04 Tower last message repeated 156 times Mar 7 22:58:10 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:58:42 Tower last message repeated 134 times Mar 7 22:59:07 Tower last message repeated 126 times Mar 7 22:59:15 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:59:15 Tower last message repeated 29 times Mar 7 22:59:22 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:59:57 Tower last message repeated 167 times Mar 7 23:00:07 Tower last message repeated 72 times Mar 7 23:00:14 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M

Solved. In the end I just powered down due to the apparent lack of HDD activity (although the powerdown script wasn't completing so I just hard reset). All came up just fine after that. If this does happen to you thought, just make sure you check that there definitely is no hard drive activity.