extrobe

And annoyingly, the 'unassigned devices' plugin is one of those being unresponsive on the main tab, so can't get in to cancel it. The download link should definitely come with a health warning if a pre-clear might block it, esp as that can be 24hrs+ Can I cancel the pre-clear via ssh? Edit: May have found the culprit - the littleun is watching Paw Patrol over Plex, so the array can't be stopped (at least, that's what I'm inferring from the unregister_netdevice: waiting for lo to become free message on the ipmi terminal)

thanks Garycase - previous backups have only have 10 mins or so, and don't think I have a way to check whether it's done or not (the web gui tries to load, but ultimately fails), but will sweat it out. Not precious about the pre-clearing - chances are I'll leave a reboot until afterwards, but I'd not long started them, and not in a rush. Quite agree - unfortunately, this was my first upgrade, and that 'download' link doesn't forewarn you that it will also attempt to apply the update. That was in fact why I was running the backup - because I was getting prepaid to run the update, and wanted a recent backup of the usb drive & appdata. Some sort of warning / confirmation would certainly be useful for noobs like me

Hi, I've use the 'download' link to upgrade to 6.3.4, but unsure if it's progressing. It had been on the 'syncing - please wait' step for about 30 mins, but I then closed the window so not sure what the current status is. The web gui in very unresponsive, although SMB shares are still online I was running an appdata/usb backup at the time, as well as various preclear activities - this probably hasn't helped, but wasn't aware unraid would attempt to perform the update at the same point as downloading it (if indeed that's what it's doing) Should I just sit & wait it out, or is there an action I need to take? plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.3.4-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.3.4-x86_64.md5 ... done Archive: /tmp/unRAIDServer.zip inflating: /tmp/unRAIDServer/bzimage inflating: /tmp/unRAIDServer/bzroot inflating: /tmp/unRAIDServer/bzroot-gui inflating: /tmp/unRAIDServer/changes.txt creating: /tmp/unRAIDServer/config/ inflating: /tmp/unRAIDServer/config/ident.cfg inflating: /tmp/unRAIDServer/config/network.cfg extracting: /tmp/unRAIDServer/config/go creating: /tmp/unRAIDServer/config/plugins/ creating: /tmp/unRAIDServer/config/plugins/dockerMan/ extracting: /tmp/unRAIDServer/config/plugins/dockerMan/template-repos extracting: /tmp/unRAIDServer/config/docker.cfg extracting: /tmp/unRAIDServer/config/domain.cfg inflating: /tmp/unRAIDServer/license.txt inflating: /tmp/unRAIDServer/make_bootable.bat inflating: /tmp/unRAIDServer/make_bootable_linux inflating: /tmp/unRAIDServer/make_bootable_mac inflating: /tmp/unRAIDServer/memtest creating: /tmp/unRAIDServer/syslinux/ inflating: /tmp/unRAIDServer/syslinux/ldlinux.c32 inflating: /tmp/unRAIDServer/syslinux/libcom32.c32 inflating: /tmp/unRAIDServer/syslinux/libutil.c32 inflating: /tmp/unRAIDServer/syslinux/make_bootable_mac.sh inflating: /tmp/unRAIDServer/syslinux/mboot.c32 inflating: /tmp/unRAIDServer/syslinux/mbr.bin inflating: /tmp/unRAIDServer/syslinux/menu.c32 inflating: /tmp/unRAIDServer/syslinux/syslinux inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg- inflating: /tmp/unRAIDServer/syslinux/syslinux.exe inflating: /tmp/unRAIDServer/syslinux/make_bootable_linux.sh inflating: /tmp/unRAIDServer/syslinux/syslinux_linux inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg syncing - please wait...

hi, I'm having a spot of trouble getting this working. I can get everything setup correctly (I've gone with a bit of file shares and a bit of files in existing shares), but as soon as I start the service, I get told I'm under attack and immediately shuts down the SMB service. It looks like one of the shares is triggering, but unsure why - I've tried a couple of times now. If I only use the file bait service, it seems to run fine. May 18 13:12:34 DEMETER root: ransomware protection:Creating bait files, root of shares only May 18 13:12:34 DEMETER root: ransomware protection:Creating Folder Structure May 18 13:12:35 DEMETER root: ransomware protection:Total bait files created: 40 May 18 13:12:35 DEMETER root: ransomware protection:Starting Background Monitoring Of Bait Files May 18 13:12:43 DEMETER root: ransomware protection:Creating Bait Files May 18 13:13:25 DEMETER root: ransomware protection:Bait Files Created: 54350 (1294/second) Completed: 16% May 18 13:13:59 DEMETER root: ransomware protection:Bait Files Created: 108500 (1427/second) Completed: 33% May 18 13:14:37 DEMETER root: ransomware protection:Bait Files Created: 163000 (1429/second) Completed: 50% May 18 13:15:13 DEMETER root: ransomware protection:Bait Files Created: 217250 (1448/second) Completed: 66% May 18 13:15:47 DEMETER root: ransomware protection:Bait Files Created: 271100 (1473/second) Completed: 83% May 18 13:16:25 DEMETER root: ransomware protection:Bait Files Created: 325300 (1465/second) Completed: 100% May 18 13:16:26 DEMETER root: ransomware protection:Starting Background Monitoring of Baitshares May 18 13:16:51 DEMETER root: ransomware protection:ATTRIB,ISDIR May 18 13:16:51 DEMETER root: ransomware protection:.. May 18 13:16:51 DEMETER root: ransomware protection:Possible Ransomware attack detected on file /mnt/user/xFileBater-fell/ May 18 13:16:51 DEMETER root: ransomware protection:SMB Status: May 18 13:16:51 DEMETER root: ransomware protection: May 18 13:16:51 DEMETER root: ransomware protection:Samba version 4.5.7 May 18 13:16:51 DEMETER root: ransomware protection:PID Username Group Machine Protocol Version Encryption Signing May 18 13:16:51 DEMETER root: ransomware protection:---------------------------------------------------------------------------------------------------------------------------------------- May 18 13:16:51 DEMETER root: ransomware protection:23510 extrobe users 192.168.0.93 (ipv4:192.168.0.93:50187) SMB3_11 - partial(AES-128-CMAC) May 18 13:16:51 DEMETER root: ransomware protection: May 18 13:16:51 DEMETER root: ransomware protection:Service pid Machine Connected at Encryption Signing May 18 13:16:51 DEMETER root: ransomware protection:--------------------------------------------------------------------------------------------- May 18 13:16:51 DEMETER root: ransomware protection:backups 23510 192.168.0.93 Thu May 18 13:14:53 2017 BST - - May 18 13:16:51 DEMETER root: ransomware protection: May 18 13:16:51 DEMETER root: ransomware protection:No locked files May 18 13:16:51 DEMETER root: ransomware protection: May 18 13:16:51 DEMETER root: ransomware protection:Deleting the affected shares May 18 13:16:51 DEMETER root: ransomware protection:Deleting /mnt/user/xFileBater-fell/ May 18 13:17:15 DEMETER root: ransomware protection:Starting Background Monitoring of Baitshares May 18 13:18:54 DEMETER root: ransomware protection:Resetting SMB permissions to normal per user selection May 18 13:19:52 DEMETER root: ransomware protection:Stopping the ransomware protection service (15743)

Interesting, as that thread also mentions dimm slots being deactivated. Certainly will give it a go - I'd actually already taped one of them up, as I was trying to flash it from another pc, but was having none of it, even with the tape added.

Interesting, thanks - I'll check that out - was up until 3am getting the replacement board + flashing the new H200 (made a right ballsup of the flashing!), so will probably give it a day or 2 before I do that, but will certainly check it out, thanks.

Thanks bman - it will always post fine (unless only A1/A2 is populated), and it will still recognise 4 slots in a different combination (eg, I'm using something like C1,C2,D1,B1) - just ignores the very presence of A1 & A2

I have 3x H200's. I'll try pulling them out in the next couple of days, see if it makes a difference.

Correct, except A1 doesn't work

Hi, I've been having a bit of an issue with the memory in my new-build. I'm using an Asus X99-WS/IPMI, which has 8 DDR4 slots. However, nothing gets recognised in slots A01 & A02. I did the usual trouble shooting, swapping ram around, trying known good ram from my other system etc, but it just wouldn't recognise it. The system would boot (unless only these slots were populated), but anything in those slots would just be ignored. So I returned the motherboard thinking it must be a mobo fault. But the new board has the same issue. Could it be a processor issue, or some other compatibility issue I've not spotted? It's a Xeon E5-2603v3 - which support 4 channels of DDR4. I'm using 4x 4gb Crucial Ballistix DDR4 2400 16-16-16-39 1.2v (non-ECC) ram If I put the 4 sticks in any other combination of slots, it works fine - but nothing from A01 or A02 So could it be a processor issue instead, or am I unlucky enough to get two faulty motherboards (from different vendors)?

Excellent, thank you

Thanks for the extra info HellDiverUK. You'd think by now we'd have sussed out reading a temperature accurately Is there a way to get the temp warning disregarded for the single ssd? The flashing hot/burn icon is getting a little annoying

Thanks - I guess I've just never paid that much attention to the temps of SSD's - and had assumed they'd run much cooler (and it certainly felt cool). Once I fiddle around with the case in a few days' time, I'll mount it somewhere where it gets a bit of airflow, see if that helps. I'll also be adding another ssd (kingston fury) from my decommissioned system in the next few days, which has been crammed in the HP Microserver for the last year or so, so it'll be interesting to see how the temps compare - but at least I'll know the kingston one is very hardy, so I'll worry a little less about the Drevo

I've added a 128gb ssd as a cache drive. I'll admit to scrimping and going for a bit of a cheapo option (DREVO Zeus SSD) as the sandisk one I was going to use was not available for a few days, and was keen to get my dockers onto an ssd! (*same-day amazon prime has made me very impatient) However unRaid keeps reporting the temperature at 50c+. Even when there's little activity on the server it says 40-45 I've felt it, and feels cool (even cold) - there are no fans on it directly, but the main HDDs are all 28-32, and it's a huge case, so nothing near it giving off heat either. Is this likely to be a fault with the ssd?

I have 12x Chenbro HDD Caddys/Trays. All in used, but perfectly good, condition. SKU is SK33502-10A Will fit a variety of Chenbro systems. Have most of the screws - might be missing a few. £5 each inc postage (to UK mainland), but will take offers to take them all. Standard Paypal payment is fine. (They're also listed on eBay - please forgive me if they go I manage to update this post!) Update: Ok, I need to get rid of these, as we move home soon and taking up room. So... happy to post them for cost of postage to anyone who can use them. UK only though I'm afraid. They're not that heavy, so don't see postage being more than in the £7-£10 region for all of them.

That would have probably saved me 24 hours, but I'll just let it get on with it now! (Plus, unsurprisingly, the new system is running at a much faster pace than the original one!)

Not a very good reason - only that I was having odd issues with slot 4 failing (even with different disk in different bays - thought I'd play it safe / try and rule out/confirm a disk issue whilst I built the new system. I'll be adding more drives post parity-sync, so will have a disk 4 again!

That seems to be doing the job - parity sync has started, and a cursory look through the drives suggests they're intact etc! thanks for the prompt help again! (ps, I'm going to be changing the heatsink - bizarrely, it's too tall for use with my new Lian Li D8000W! Gets in the way of the centre divider which I want to use to mount a fan to cool the controllers)

Correct - I'll give that a go, thanks!

Hi, after a bit of support again! I've moved to a new system - all new hardware (including new raid controllers), but bringing the disks with me. (Old controller was an Adaptec 51245 in JBOD mode)/ New controllers are H200s, though all disks are connected to only one of them) On the old system, I screenshotted the current array config, stopped the array, disabled 'autostart' & shut down I moved all the disks to the new system, ensured the controllers were configured correctly (IT mode v20) and boot was to the usb drive. unRaid starts up fine, but even though it seems to have correctly identified each disk, it's not allowing me to start the array as there are too many 'wrong' drives. Have I missed out a step?

Thanks, I'll do that tomorrow when I build the rest of the system, thanks for the heads-up

Thanks both. I tightened the nuts down to finger tight - the heatsink doesn't budge. ran the motherboard without any other components except ram for about 15 mins and temps etc seemed stable. Perhaps you're right, and this is the intended setup - just seemed to be an awful lot of space in there. And thanks for the tips jonathanm - first time I've ever had to remove a HS after initial setting - harder than you'd think to remove haha! (Ended up twisting & pulling)

Need a bit of help... Installing a heatsink for my 2011v3 Xeon E5 into my Asus X99-WS board. The heatsink is is a Silverstone SST-AR01 , which I bought because OCUK specifically lists socket 2011v3 as being compatible (whereas the Evo 212 had conflicting information) It comes with two sets of standoffs - one set for when you use the rear bracket, and one (smaller) set specifically for screwing into the existing lga2011 screw holes. Only the smaller ones fit, so there doesn't seem to be any room for confusion there. I then install the mounting brackets across the standoffs. Again, these only go on one way, and I screw them down with the thumb screws. I then pop on the heatsink, and thread the cross-bar through and onto the mounting brackets. There are then two nuts for screwing the cross bar onto the brackets. And this is where I have a problem. There's about 4mm of additional clearance between the mounting bracket and the cross-bar. Is this right? Should it not be fairly flush? The other standoffs are taller, but won't thread into the screw-holes.

Managed to this this on Asus's website, and seems to be the only official word I could find on the matter - but suggests the 2nd is only for very heavy usage scenarios, and 1 should be fine. I'll go with the PSU as-is i reckon - thanks for the help getting to the bottom of it!

because using the same cable would be too easy