gloory91

it is fully updated, and it was there before. now i need to go trough the plugins page and into the preclear plugin to see whats happening

try moving the usb stick to another usb port and reboot button

oh and just a quickie, my preclear progress button in the lower right corner have been gone for a while is this removed?

absolutely lovely, no issues on my good ol server! also i love the added wifi support, but i cant find a way to make wifi as active-backup. will that work in the future? also the gui now is super fast! thank you very much for this update you great people!

the consuption i dont care about either, its the amount of hours they are powered on per year rating im talking about

understand, here the laws are i can just return it no matter what within 60 days anyways. for the array i only use server disks, these are simply just for a backup of the array in the rare event multiple disks in the array die at the same time or something.. lets just say the case is they are new and all that, would they be trustworthy of this task given their low power on rating and the low actual usage they will have?

brand new. it is a reputable local store so i doubt there is anything wrong with it. even if, i have full warranty etc on it

can do after next parity check, because when i restart server it resets and dont come back until next check

those ones

errors here, the parity check is 0 errors btw

found a good price on these "ST24000DM001", and want to have a backup of the server on a couple of these but im a bit worried about the yearly power on hours rating? will they be good as a sort of cold storage only being connected for backup once a month or so or does the power on rating not really matter if they are connected but not spun up?

what could be the reason for this? is the drive safe? a disk i had this problem with before and removed from the array and precleared ended up not doing this when i put it back in the array and have worked since. but that was a 3 tb, this is a 6tb and i dont have time right now to do this. any ideas?

btw does these cards have a temp sensor?

i guess i could put it back in there and pull some diagnostics but it does get detected and listed in the device list etc

yea no bad disks or cables, the replacement came in the mail today and it works with that.. so it must be something with the hba

i started a parity check before bed and the next day i log into unraid and see all disks missing. i have tried everything and in different machines but still not showing any disks.. i get it listed in device list and all, and can go into the cards bios but it doesent show the disks there aswell.. what could be wrong with the hba ?? it is a lsi 9305-16i btw in IT mode

totally correct, it works now!

yea thats what i tought, hope they fix it in next update or at least if there was a workaround someone knew

it does that, thats what i tried first. but it didnt want to connect still after i entered it manually

yes correct, only when i hide it again it disconnects and not connecting again

hi, dont know if this is the right place to ask but when i tried to use the new wifi coneection on my unraid tower but i have a hidden wifi i want to connect to. but it is not connecting to the hidden ssid... i tried to make it visible and then connect to it, but as soon as i hide ssid it disconnects and will not connect to hidden ssid.. is there a way to fix this or will it be implemented later?

oh didnt know i had it, but i uninstalled it now and will see if it does anything!

i could just remove the card next time it reboots, or i reboot it if im able to rebuild the disk on this time. also, here is what looks like a problem, it is eth0 which is the port on my motherboard that is in use.. again, it does this all by itself at a random time ### [PREVIOUS LINE REPEATED 1 TIMES] ### Feb 17 18:20:44 Tower kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Feb 17 18:20:44 Tower kernel: TDH <17> Feb 17 18:20:44 Tower kernel: TDT <90> Feb 17 18:20:44 Tower kernel: next_to_use <90> Feb 17 18:20:44 Tower kernel: next_to_clean <17> Feb 17 18:20:44 Tower kernel: buffer_info[next_to_clean]: Feb 17 18:20:44 Tower kernel: time_stamp <101e941e7> Feb 17 18:20:44 Tower kernel: next_to_watch <18> Feb 17 18:20:44 Tower kernel: jiffies <10204bbc4> Feb 17 18:20:44 Tower kernel: next_to_watch.status <0> Feb 17 18:20:44 Tower kernel: MAC Status <80083> Feb 17 18:20:44 Tower kernel: PHY Status <796d> Feb 17 18:20:44 Tower kernel: PHY 1000BASE-T Status <3c00> Feb 17 18:20:44 Tower kernel: PHY Extended Status <3000> Feb 17 18:20:44 Tower kernel: PCI Status <10> Feb 17 18:20:44 Tower kernel: e1000e 0000:00:19.0 eth0: NIC Link is Down Feb 17 18:20:44 Tower kernel: BTRFS info (device loop3): last unmount of filesystem 8e17c87d-08a7-4c10-8d21-50858b08015b Feb 17 18:20:44 Tower kernel: bond0: (slave eth0): link status definitely down, disabling slave Feb 17 18:20:44 Tower kernel: e1000e 0000:00:19.0 eth0: left promiscuous mode Feb 17 18:20:44 Tower kernel: e1000e 0000:00:19.0 eth0: left allmulticast mode Feb 17 18:20:44 Tower kernel: bond0: now running without any active interface! Feb 17 18:20:44 Tower kernel: br0: port 1(bond0) entered disabled state Feb 17 18:20:45 Tower rc.docker: Unraid managed containers stopped. Feb 17 18:20:45 Tower rc.docker: Stopping network... Feb 17 18:20:45 Tower kernel: bnx2x: [bnx2x_timer:5810(eth1)]MFW seems hanged: drv_pulse (0x1c8) != mcp_pulse (0x7fff) Feb 17 18:20:45 Tower rc.docker: Network stopped. Feb 17 18:20:45 Tower rc.docker: Stopping Docker daemon...

i do have a dual 10G pcie card in the server that i currently not using for anything, but it has been there forever. could this card suddenly start making this problem, is that what you say? or did you mean it would not initiate shutdown or reboot?

this is that it spams before the reboot as far as i can see Feb 17 18:16:05 Tower kernel: bnx2x: [bnx2x_timer:5810(eth1)]MFW seems hanged: drv_pulse (0xb7) != mcp_pulse (0x7fff) Feb 17 18:16:05 Tower kernel: bnx2x: [bnx2x_acquire_hw_lock:2022(eth1)]lock_status 0xffffffff resource_bit 0x1 Feb 17 18:16:05 Tower kernel: bnx2x 0000:03:00.0 eth1: MDC/MDIO access timeout Feb 17 18:16:05 Tower kernel: bnx2x: [bnx2x_timer:5810(eth2)]MFW seems hanged: drv_pulse (0xb4) != mcp_pulse (0x7fff) Feb 17 18:16:05 Tower kernel: bnx2x 0000:03:00.0 eth1: MDC/MDIO access timeout Feb 17 18:16:05 Tower kernel: bnx2x: [bnx2x_acquire_hw_lock:2022(eth2)]lock_status 0xffffffff resource_bit 0x1 Feb 17 18:16:05 Tower kernel: bnx2x 0000:03:00.1 eth2: MDC/MDIO access timeout