nexusmaniac

Hi, I'm really quite concerned tbh! 19th May, I came back to a completely crashed Web GUI... Everything seemed to have gone back to default settings... Turns out the USB had overheated because my Asrock board decided it didn't need fans spinning to cool anything!! I was greeted with /dev/sda undetected and a load of warnings. I rebooted and everything was fine though... So I deleted my post on here I was wrong. Disk 3 had 1.48TB of data on it... From after that reboot it only reported 1.28TB!! I was worried, it almost exclusively contains Plex media files, none of which seemed to be missing however. So I'm super confused with unRAID! Moving onto what's happened today though! (2 diag files attached, one for just now and the other for the 19th) I tried to stop my array and got a crap ton of errors along the bottom of the web GUI Error, couldn't stop array, couldn't unmount disk. That went on and I eventually had to hold the power button down Which I hated! I couldn't get to the web GUI, SSH or even ping it. I used the IPMI and grabbed the diag file from the USB If someone could help me figure out what's going on that would be immensely appreciated I've got nothing out of the ordinary going on AFAIK, 2 dockers, couple of users accounts and a handful of SMB shares - Pretty basic in the grand scheme of things raptor-diagnostics-20160521-1535.zip raptor-diagnostics-20160519-2238.zip

Yeah... Memtest 5.01 is pretty old and buggy tbh We use it at work, leaving it Single threaded works 100% and always catches errors (Leaving it on for 72hrs per server) Multithreaded / SMP however... On our lowest end servers it works alright, but move up to Hexcore Xeons with DDR4 etc.... Memtest doesn't get along with that hardware haha Single threaded mode should be more than ample at catching memory errors though

Seems odd! Definitely got the Xeon E3-1275v5 and not like a 1245 somehow?

Make sure CPU turbo is enabled in the supermicro BIOS

Just run this: cat /proc/cpuinfo |egrep -i mhz SSH in, or use a monitor and keyboard hooked up to your unRAID server It'll give you a readout of frequencies that the raw system is reading Make sure you're doing something to push the system too Spin up a VM or something so the CPU is actually doing something I.e. if you're just idling, the CPU will never need to hit 4GHz

Disable the p_state driver. Just in case you don't know how to do that ... label unRAID OS menu default kernel /bzimage append intel_pstate=disable initrd=/bzroot ... Alter your syslinux setup (go to the 'main' tab in unraid, click Flash and scroll down) Just add "intel_pstate=disable" to the append line under the first block of text (example above )

Hey, did you ever get any word on Transmission being updated, to 2.92 from 2.84, by anyone over at lyricist?

Yeah? And it's exactly what I said a few post ago All of those settings pertain to USB 3 ports Means if I'm plugging into a USB 3 port I can enable legacy mode (some USB 2 devices don't play nicely with some USB 3 ports) but as I'm using a USB 2.0 drive in a 2.0 port - I don't have any settings to mess with

Different USB ports haven't made a difference And the only BIOS settings pertaining to USB are for USB 3.0, xhci settings etc. Have you tried changing the BIOS USB settings from 3.0 to Legacy, or whatever other options are presented to you? I haven't because that's unnecessary I'm already using a USB 2 port for the USB - None of my USB settings affect the USB2 ports

Different USB ports haven't made a difference And the only BIOS settings pertaining to USB are for USB 3.0, xhci settings etc.

Could you try another Flash Drive and see if you have the same problem? Just to see if it boots. With two of you having virtually the same problem, I can't believe it is cockpit error! The issue is the cruzer fit. I have the same thing. Here's how to manually test it. When it scans for the UNRAID label, remove/reinstall the USB key. You'll see it picked up right away and it'll boot normally. That's obviously not a longer term solution, but it will allow you to boot manually. Hmm that's really unfortunate if that's the case! Strange though, that it works perfectly fine until 6.2 betas I guess if this is truly the fault of the USB then the guys over at LT should probably not have it as a recommended USB boot device haha I'll try to give this a go at some point - But I'm pretty happy with 6.1.9 right now Try this: http://lime-technology.com/forum/index.php?topic=48193.msg464526#msg464526 I saw this It's in my Google Keep - I really want to get round to trying this! But I don't get much room in the way of taking my unRAID server offline haha

Could you try another Flash Drive and see if you have the same problem? Just to see if it boots. With two of you having virtually the same problem, I can't believe it is cockpit error! The issue is the cruzer fit. I have the same thing. Here's how to manually test it. When it scans for the UNRAID label, remove/reinstall the USB key. You'll see it picked up right away and it'll boot normally. That's obviously not a longer term solution, but it will allow you to boot manually. Hmm that's really unfortunate if that's the case! Strange though, that it works perfectly fine until 6.2 betas I guess if this is truly the fault of the USB then the guys over at LT should probably not have it as a recommended USB boot device haha I'll try to give this a go at some point - But I'm pretty happy with 6.1.9 right now

I had the same issues on every beta I've tried for 6.2 I'm now steering clear of the betas for a while haha Just scans for LABEL=UNRAID and then fails to find it somehow Bus 003 Device 003: ID 0781:5571 SanDisk Corp. Cruzer Fit

I'm yet to try - Going to try tonight if I get the chance... I've tried updating my unRAID server (spec in my sig) to beta, 18, 19 and 20 with no success Hopefully beta21 will work out (I made a post in a previous thread, errors when I update - keeps scanning for label = UNRAID and gives up)

Thanks for clearing that up haha - It'll still bug me! But at least there's nothing majorly wrong going on haha

Current figures Interface Receive eth0 Errors: 0 Drops: 53076 Overruns: 0 Interface Receive pkts Transmit pkts eth0 885970752 1011850698 Sure, it's not every packet, or even every other packet But it's surely not a healthy amount Bear in mind that I had 0 on 6.1.8 - And nothing has changed network wise, any cable swap has been reverted to the original cable

Hello, Been running unRAID for a couple of months now - loving it btw - All has been fine and dandy until the other day... I updated from 6.1.8 to 6.1.9 on the day of release (4th March) and since about a week and a half ago I glanced at the error count for the network! Interface Receive Transmit eth0 Errors: 0 Drops: 52752 Overruns: 0 Errors: 0 Drops: 0 Overruns: 0 If I hit refresh on the dashboard I'll get 1 drop about ever 2 seconds! Not sure what's causing this. Steps I've tried: Swapping cables, different ports on a switch, rebooting switch, rebooting router, rebooting unRAID - None of these have done anything I'm running unRAID on an Asrock E3C226D2I board, which has 2x Intel i210 ports onboard - It's setup with a static IP, nothing fancy at all in terms of bridges or link aggregation Also, running the latest available BIOS (3.30) with the latest IPMI update (00.22.00) Any ideas?

That suggests that the USB stick is not mounted at /boot as it should be! Are you sure it has a label of 'UNRAID' (all in capitals) as the first messages you mention suggests it is not being found. What happens if you login on the console and use the command ls -l /boot ls -l /boot/syslinux These should show the files on the USB stick - I suspect they will not. In particular the second one will not show the contents of the syslinux folder as the error message implies it is not there. Hi, 10000% sure that it's labelled UNRAID Well this is fun lol - I've already reverted to my 6.1.9 backup and for some reason it started a parity check - So I'll leave it to get on with that, upgrade to b19 again and get the results of those commands - Pretty sure its' gonna return nothing at all (which makes very little sense to me... It boots so far into unRAID anyway... I can sign in as root to tower when I get past the waiting (but there's none of my settings, no web GUI access - Only SSH and local access))

I've had this issue on b18 + b19, I've also seen it mentioned a couple of times in each of the beta threads The whole "waiting for /dev/disk/by-label/UNRAID (will check for 30 sec)..." I'm running 6.1.9, tried updating via the plugin update and saw this! (attached screenshot) That's what happened as soon as I tried to update the plugin

I've been looking for ages for this fix! Thanks (Sorry, I can't confirm if it's working on the 6.2 beta, not managed to get the beta running on my server yet haha)

How long has it been out? Once the lackeys lyricist releases it, my plugin should pick it up. Usually takes a few days for them to upload it. It's been out since the 6th March 2016 Aha ok cool - I'll keep an eye out for an update haha

Hi PhAzE Been using your Transmission plugin for a while now - Just wondering if you had any plans to update it to the latest version? 2.92

Hey guys Just had a scary moment! (Thank god for UNRAID/previous)!! Upgraded to 6.2 Beta via the manual plugin update - Booted fine, got past a bunch of bootup stuff... Then, I got to "searching for /dev/...... label UNRAID (Looking for 30 seconds) over and over again Until it fails, unable to find label = UNRAID Then it says tower login: root / no pass works But I can't get to the IP of the server - I can SSH in and I can access it locally / IPMI But I've thankfully rolled back to 6.1.9 By copying the contents of /previous - on the USB - back into the root directory of the USB and booting it back up