moose

Upgraded from 6.5.2 to 6.5.3-rc2. No issues!

Thanks trurl! Update: After removing and reinstalling, I was delighted to see that all my previous custom plex settings were maintained. All I had to do was uninstall the existing plex docker (also selected the remove image option), then install a new plex docker from the Apps tab and remap my previous share and transcode paths. All previous user detail and custom settings were maintained with the new plex install, awesome! Easy fix!

I renamed my plex container name from "plex" to "Plex" in the container configuration, now the configuration (conf file) is missing. I can't go back and rename the container from "Plex" to "plex", cannot perform any updates. I searched hte /mnt/cache/appdata/plex folder and its empty (no conf file). Is there anyway to get the conf file back or do I need to remove and reinstall plex? Or can I just reinstall without deleting plex and will it recreate a conf file and preserve the existing settings?

Thank you LimeTech and team. Smooth easy upgrade, all is good! p.s. - noVNC is very nice! I like this enhancement.

Thanks SSD. bonienl's, steps worked in my case, but I think I've done your brief power button step before to get a clean shutdown. All good tips!

Thank you Frank1940, I already had the array stopped before I upgraded unRAID OS via the plugins page. I'll note what you stated for future use if necessary.

Thank you bonienl. Those commands worked. I was able to identify the ipmifan process and kill it. Immediately after killing it the reboot completed and 6.4.0 is showing as the OS. All is good!

I'm stuck with v6.3.5 not shutting down to reboot, reboot is hung. If the server would shutdown and then start the reboot process I could chose safemode from the boot menu, but I can't get to that step. How do a force a clean shutdown from the hung condition?

Upgrading from v6.3.5, I stopped all dockers and VMs, stopped the array, upgraded the unRAID OS from the plugins tab, zipfile downloaded and extracted successfully, got message that reboot was required for unRAID OS update. Went to main tab and clicked Reboot button, webGUI displayed system reboot. I waited ~ 5 min and webGUI wasn't showing reboot. Went to console window and I see this line repeating over and over (scrolling) in the console window: "Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/ipmi/scripts/ipmifan on line 322". The reboot process is hung and if I open a new webGUI window I see that v6.3.5 is still showing. What should I do next?

Great that SuperMicro RMA'd your MB! Hopefully you'll be back in business for a long time after you receive the new MB.

See this article. I have a SuperMicro c2758 board running my pfSense box. I was able to get SuperMicro to swap out the board for free back in March 2017. Not sure if this is what happened to you talkto_menow. http://www.theregister.co.uk/2017/02/06/cisco_intel_decline_to_link_product_warning_to_faulty_chip/

I've searched the forum but cannot find a clear answer to this question. Is the LSI 3008 supported in unRAID 6.3x+? I'm considering this MB (X10SRH-CLN4F) but need to know if the LSI 3008 is supported.

Thank you!

Upgraded from v6.24 via unRAID built-in Plugin with no issues. Thank you LimeTech and team!

Not sure what router you are using. If you were using pfSense you could setup a rule to block an IP address, series or range of IP addresses. I'd look at your router and see if you can block WAN IP address(es).

Good deals! I wish I was in Oregon. (I'm in Indiana.)

Thanks kode54! Not sure how, why NCQ was set to "No" Perhaps I had it set this way in a v5.x release? Anyway will test the defaults, including NCQ = Auto. Perhaps Tom or bonienl should insert a "default" button for that section in Disk Settings.

Could someone please indicate (post) the default disk tunables for v6.2.2 (or 6.2.x)? The screenshot below is what I currently have set. Some are set to default and some are user-set. I'd like to know the default values to set a baseline. Since I've been upgrading from earlier unRAID versions, I don't know the 6.2.x default disk tunables. I think I may be able to get better performance from setting to all to default values or at least start there and tweak. Thanks!

Thank you! The rebuild has managed to get past the point where disk #11 started having read errors, so perhaps it was the cabling and/or disk drive seating into the 5-in-3 cage. Edit: Disk #6 successfully rebuilt!

Hi, I have the following situation, not sure on the next step: 1. I received a notice that disk #6 (WCC4E5AYDP0C) was disabled. I didn't collect the syslog and shut down the server. I thought it might have been from bumping one of the SAS-to-SATA cables, since I had the cover open and was plugging in/unplugging on-board usb flash drives to upgrade my IBM M1015 device. I re-seated the cables and hot-swap drive bays. 2. I rebooted the server and ran smart tests on disk #6, everything reported fine, no reallocated sectors, read errors, etc. I chalked it up to bumping one of the SAS-to-SATA cables while upgrading the IBM1015. 3. I unassigned disk #6, started the array, stopped the array, reassigned disk #6 (WCC4E5AYDP0C) started the array and the array and disk #6 started automatically rebuilding the data. 4. After a few minutes of rebuilding disk #6, disk #11 (1CH164_Z1E9G6AP) started reporting read errors. I stopped the array and exported the attached diagnostics file. 5. I re-seated the cables and hot-swap drive bay for disk #11, booted the unRAID server and ran a few short smart tests on disk #11 (passed). Not sure if this was due to another loose cable/drive. 6. I haven't started the array. Not sure what to do for the next step. I believe the contents of disk #6 might be corrupted since I previously started a rebuild of disk #6 and canceled. What would be the next step to (hopefully) prevent data loss and get back to a healthy array? Thank you. diagnostics-20161023-2008.zip

The original preclear_disk.sh has to be patched in order to work with unRAID 6.2 Just to be clear....by "patched" do we mean the following: Patched = download the original preclear script by Joe L (here) and place that preclear script in "/boot/config/plugins/preclear.disk/"? Here is the info on the patch for Joe L's original preclear script http://lime-technology.com/forum/index.php?topic=13054.msg464653#msg464653. According to gfjardim, his script is 6.2 compatible out of the box. No patch required. https://lime-technology.com/forum/index.php?topic=39985.msg504465#msg504465. Thank you. I tried several times but had trouble with gfjardim's script on v6.2.1. I installed, uninstalled, re-installed, etc, many times but had issues with my syslog filling up, webGUI becoming unresponsive and the zeroing (write cycle) was ~ 5MB/s. Then I had tried to run Joe L's original preclear script in v6.2 via telnet and couldn't the preclear script to run, but.... with the "sed..." command modification Joe L. lists at the 1st link you provided, it works via telnet, although the pre-read cycle does seem slow... It seems preclear isn't playing well with v6.2 for me... FYI - here is the syslog detail from the preclear operation....this keeps repeating over and over while preclear runs filling up the syslog. I ended up canceling the preclear I had running in telnet. Oct 13 22:41:08 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 7b 4b 04 d8 00 00 01 00 00 00 Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(11) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(114688) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(16384), sc->result(0x00000000) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:09 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 2f 00 00 00 01 00 00 00 Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(9) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(131072) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(0), sc->result(0x00000000) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:10 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 32 00 00 00 01 00 00 00 Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(9) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(130560) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(512), sc->result(0x00000000) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:11 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 42 00 00 00 01 00 00 00 Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(11) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(130560) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(512), sc->result(0x00000000) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:11 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 43 00 00 00 01 00 00 00 Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(11) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(130560) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(512), sc->result(0x00000000) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312)

The original preclear_disk.sh has to be patched in order to work with unRAID 6.2 Just to be clear....by "patched" do we mean the following: Patched = download the original preclear script by Joe L (here) and place that preclear script in "/boot/config/plugins/preclear.disk/"?

Change the VMs bridge to br0. I don't have a "br0" selection in the network bridge area of the VM configuration GUI. I just have "virbr0" as a selection/option. I tried editing the XML file for one of the VMs but then I get a execution error message ("Cannot get interface MTU on 'br0': No such device") when the VM attempts to start. Is there anyway to make "br0" an available choice in the network bridge area of the VM configuration GUI? First thing to do is to enable bridging in the network settings of unraid. Then you can set the default bridge in VM manager to br0. After that, you will always get the br0 as the default interface in a VM template. To get your existing VM to use br0, just go to the VM template and choose br0 after you enable bridging in network settings. Yes, that was the problem. Bridging was not enabled in Network Settings. After enabling bridging, I was able to select br0 in each VM and get the correct 192.168.0.x IP assigned. Thank you dlandon and saarg!

Change the VMs bridge to br0. I don't have a "br0" selection in the network bridge area of the VM configuration GUI. I just have "virbr0" as a selection/option. I tried editing the XML file for one of the VMs but then I get a execution error message ("Cannot get interface MTU on 'br0': No such device") when the VM attempts to start. Is there anyway to make "br0" an available choice in the network bridge area of the VM configuration GUI?

I upgraded from 6.1.9 to 6.2, that step worked fine. I also migrated (2) Win7 VMs from 6.1.9 to 6.2, however I noticed I couldn't Windows Remote Desktop into either of the Win7 VMs. I can open up a VNC Remote window within the unRAID GUI and access each VM just fine. I noticed each VM is assigned a 192.168.122.x IP, but my DHCP server is 192.168.0.x I also noticed the Network Bridge in each VM is set to : virbr0 Again the problem is that the VMs are being assigned 192.168.122.x IPs instead of 192.168.0.x IPs, all else is good/stable with v6.2 Not sure if there is something I missed or need to check in v6.2...any ideas/thoughts?