voidburn

That must be it, I will make another attempt once 6.9 is out since I'm waiting for the ability to setup SSD pools anyway. Thanks for the input, I should've thought of looking at difference in the flash between my existing install and the fresh one. Cheers!

@ChatNoir No hardware passthrough, there are no VMs on the setup (only docker containers) @itimpi The EFI folder has a dash in it:

Hello there, I was looking into refreshing my unraid server's hardware, so I went about putting together a new server, current and new specs below: [ Current HW ] HP Proliant Microserver G8 Intel® Xeon® CPU E3-1220L V2 16 GB ECC Single Bit DDR3 LSI SAS2008 based controller 2x3TB Seagate drives 1x500GB Cache drive [ New HW ] Intel i7 6700k 32 GB DDR4 @ 3000mhz Asus Maximus VIII Gene LSI SAS2008 based controller (migrated from the old HW) same disks and configuration (migrated from the old HW) What I'm experiencing when plugging in the usb boot drive is an immediate boot loop just after the bzimage is loaded, and can't see what happens there because no error is shown or logged. I also tried upgrading from 6.8.3 to 6.9 RC2, but the same thing happens. If I do a safe boot WITH gui it starts, if I do a safe boot WITHOUT gui it boot loops, which confuses me even more, the non gui safe boot should be even lighter/more compatible than the gui version. Now what's puzzling, if I install a 6.9 RC2 from scratch and install a trial license everything works (no other changes to either bios/config). It feels like my usb boot drive was set up in a different way when it was created, and this is causing a problem. Can anyone guess what's going on? Is there a way to go about doing a brand new install on my existing usb boot drive without compromising the license? Is this something that can be fixed without redoing a full install? Any help/insight is greatly appreciated! For the time being I just moved all the hardware back to the old server and rolled back to 6.8.3. Thanks in advance

I am sick and tired of dumping north of 300 bucks on replacement hard drives which regularly fail after 2 years (despite being enterprise seagate ones). Since my data hoarding is mild (< 1TB) I am going to wing it and simply spin up 4x500GB SSDs array without parity until official support lands. Even if trim is disabled I think I'll survive for plenty of years (don't remember the last time I actually deleted something from the array, for frequent changing data I rely on SSD cache drives anyway). The reason I'm doing this is purely out of longevity issues with mechanical drives and the specific use I make of my storage space. As for parity, well I'm going to risk it, based on the fact that in > 8 years of SSD usage I had zero bit rot and zero failures. So, thanks for confirming that you had no trouble with an SSD array without parity, that's all the reassurance I needed to get rid of the anxiety of expensive mechanical drives failing on me yet again!

Funny thing is: with the anniversary update your license would be bound to your Microsoft Account, and you wouldn't need to do much to reactivate your copy, beside logging in with your MSA and do the equivalent of the old phone reactivation. That is, if you have a retail copy, since OEM copies go in the trash if a massive hardware change is detected. So if you have retail, go with whatever makes the update work first so it can bind your license to the MSA, then you can start fresh.

That did it! Thanks, I never fiddled with the terminal-type before, always left it unchanged. To be honest I've never looked into how terminal emulation is accomplished, hence my ignorance in solving this problem. Thank you very much for your help!

I didn't, the only other time I dropped down to the shell before was to partition and format the cache ssd with btrfs. I currently have an ubuntu 16.04 LTS server installed, and my TERM is putty there too. Also: 1) I had a login where everything was working, but I exited before thinking about looking at the TERM var 2) Using putty Release 0.67

Hello guys, I'm currently in my month of trial and have just finished the first parity sync and started bringing up some docker apps. At some point I wanted to edit directly some config files, and I thought to go and edit directly via the shared "appdata" folder in SMB, no luck, files there cannot be read. Second stop was logging in via ssh to edit them, but to my surprise I couldn't use either nano or vi, the first reporting a "Error opening terminal: putty." and vi starting but having big issues. I thought at first I had somehow created a putty session with some wrong configurations, but I tried cloning another working session and while every other machine works, on unRAID I just cannot edit files via ssh (or telnet). Since I haven't been able to find anything on the forums about this, I'm forced to create a new thread, I've never had anything like this happen to me and cannot find a way to fix it. root@Tower:~# echo $TERM putty root@Tower:~# echo $SHELL /bin/bash root@Tower:~# nano dead.letter Error opening terminal: putty. root@Tower:~# vi dead.letter skipping 1 old session file reading dead.letter Read dead.letter, 21 lines, 312 chars ** nothing shows unless I scroll down by pressing enter until the EOF ** Any ideas? Cheers