January 16, 20188 yr I have now tried to upgrade to 6.4 twice now. I have attached Tower_SystemProfiler.pdf which is my system specs. On 6.35 I have no issues in the fix Problems log Tower_FixProblems.pdf and attached are also the tower-diagnostics-20180115-1735.zip and my tower-syslog-20180115-1735.zip of the system working perfect under 6.35. Once installing 6.4 upon reboot I get stuck for like 2-3 min on the line RIP: isci_task_abort_task+0x18/0x334 [isci] RSP: ffffc900051efce8 CR2: 0000000000000000 ---[ end trace 900111f6f3aaeddd ]--- Finally I am able to get into the web ui via 192.168.1.200. Once in I am missing my parity drive and my SSD Cache drive. Attached are both the tower-diagnostics-20180115-1820.zip and the tower-syslog-20180115-1820.zip Later started looking and going through my BIOS I stumbled upon a setting for a SAS controller which was "Enabled" Device 0: was my Adata SSD (Cache Drive) Device 4: was my WD Gold 10TB (Parity Drive) Told the system to shut down but it gets hung on the force shutdown and never shuts off. I have to force it off If I disable the controller the system booted up right away without hanging up on the lines above. But both drives are still missing. Attached it tower-syslog-20180115-1834.zip. Told the system to shut down and it shuts down without issue. Once I enable the controller system agin got hung up on RIP: isci_task_abort_task+0x18/0x334 [isci] RSP: ffffc900051efce8 CR2: 0000000000000000 ---[ end trace 900111f6f3aaeddd ]--- For about 2 min then finally got to Tower Login: Went through the shutdown via CLI and got hung up and would not shut down again. Forced it off and reflashed the USB drive on MAC tool and installed 6.35 and restored all the config and docker items booted up and checked BIOS for SAS Controller "Enabled" and then proceeded with boot no issues. System back online with Parity and Cache. The only item that seemed to get lost was the actual parity check, so it is currently doing that before I am willing to attempt to make any changes again Approx 23 hour... Any help or anyone know how to correct? tower-syslog-20180115-1735.zip
January 16, 20188 yr Do you have a CD-ROM attached (syslog seems to indicate this). If so try disconnecting it and see if your HDD's on that sas controller show up again.
January 17, 20188 yr Author Okay I removed the CD drive and magically the parity and cashe were back! But...... Something was still off, I could not get to the dashboard without waiting and it never did show my System info or CPU info. It showed all my dockers as running after a couple min but I could not access plex from apple tv or from the pc via unraid gui. I could not download the diagnostic file as it just said it was downloading for a few min. I was able to grab the syslog though. tower-syslog-20180116-2015.zip I did not get the snappy response everyone was talking about. Mine was very slow. Could not get the array to stop or shutdown. CLI got hung on the shutdown also and I had to force off. Went back to 6.35 I t is restarting the parity now again. in 24 hours I'll be ready to try something else. Is there anything anyone can suggest?
January 17, 20188 yr The S3 plugin is known to cause problems in 6.4.0, recommend uninstalling it. And you mention no CPU stats, guessing you are using Safari? Switch to Chrome or Firefox. Also see this new sticky
January 19, 20188 yr Author Thanks ljm2! The instructions in the thread helped me and upgrade in now complete! Thank you. I was using chrome previously when I could not see stats but after following the new sticky thread it upgraded perfectly and all is well.
Archived
This topic is now archived and is closed to further replies.