rxnelson

When? Sorry, had to. [emoji16]

It was there earlier today. Like $115.96 or something like that. Back up now. Sent from my iPhone using Tapatalk

Just a general question with all the "faster" comments. Is it the improvements or the browser? I've noticed when I use chrome and there are a ton of webgui notifications it lags like hell almost to the point of being unresponsive. If I refresh the whole tab or open a new window it feels quicker and starts acting "normal". I assumed that it was a chrome eating memory thing.

I see what you did there.

Heh heh Good, glad you took it in good fun as that was the intent.

I thought you were pretty dedicated to this thread.$$$ Just poking a little fun here---$15k for in your words throwing a box of grenades as a troubleshooting method? I'm sorry just having a little fun. I'm glad there are people like you that have the time to buy the bleeding edge stuff. I don't do it anymore. I just expect issues and I need stability just from a time perspective. I'll admit I have an ulterior motive in hoping you figure it out. This frees up Limetech for other enhancements while also potentially bringing more customers and growth and giving me a constantly improving product. Carry on! [emoji3]

I'm going to post this here as it seems related. I think you guys are taking about a web browser in this thread. I'm seeing an issue in Tapatalk where taking me to the "First Unread" typically takes me to the latest post regardless if that's where I should be or not. Any way to fix that? Sent from my iPhone using Tapatalk

I haven't investigated too closely to be honest. I was just a little surprised in the difference in temps between that and the identical [looking] istar units. Maybe the istar have more steel or aluminum in them for heat transfer and these are more plasticy? I'm not sure. Flipping the fan may not be a bad idea. I'm just preclear if drives right now so maybe I'll even just send it back and try the pricier istar unit. I'm still in my return window. Sent from my iPhone using Tapatalk

I bought one of these off amazon since it seemed like a cheap knock off of the istar units. So far it hasn't been able to keep the temps down on my drives during a preclear. I have it mounted in a P4000 Intel chassis. The istars are in an Antec 1200. Maybe that is the difference but maybe you get what you pay for. Anyway, I didn't see any threads on this particular model and wanted to warn or have someone chime in that they work great and I must have a bad unit. https://www.amazon.com/dp/B01BMJ1WD6 Sent from my iPhone using Tapatalk

Saw this other thread. Guy was able to get his working near the end. LSI Controller FW updates IR/IT modes https://forums.lime-technology.com/topic/12114-lsi-controller-fw-updates-irit-modes/?do=findComment&comment=541151 Sent from my iPhone using Tapatalk

Hmmm....I am not sure. I've done 4 of these without major issues. Did you use an old version of sas2flash.efi as your quote suggests? Sent from my iPhone using Tapatalk

I uninstalled and reinstalled the plugin per another thread and that worked. Sent from my iPhone using Tapatalk

This worked. Thanks. Sent from my iPhone using Tapatalk

Anyone run the preclear plugin yet? I just put in a 5-in-3 and I can see the drives in unassigned device but when I click preclear nothing happens. I don't get the next window. Yes I double posted http://lime-technology.com/forum/index.php?topic=39985.msg541613#msg541613 but I wasn't sure which thread was appropriate. I thought it more likely someone with 6.3.2 would see it here and be able test. It could be the cage. Like I said I just got it but the lights are one and the fan is spinning and I can see the drives in the bios and unassigned devices. Thanks.

Is this working on 6.3.2? I just put in a 5 in 3 cage and it I can see the drives in unassigned devices but when I click preclear nothing happens. When I go to the tools menu and click preclear I get this with the spinning animation. Please wait... retrieving information! Thanks

I believe the black/red cable is the hard drive activity lights. The H310 will need to be flashed? Pretty sure that stepping SR0KQ had VT-d. There is a thread in the good deals section that verifies this. Sent from my iPhone using Tapatalk

There is a plugin called fix common problems or troubleshoot or something like that. I found that rootfs was 100% full which turned out to be low memory (1gb) with no dockers only preclear plugin as extra. I thought I was ok as the webgui said I was only using 83% of the memory but it would go for 2 sometimes 4 days before crappie out. You may want to run that plugin in troubleshooting mode. Sent from my iPhone using Tapatalk

Round 2 at the bottom. Are the attributes useful to post? Round 2 ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 24 24 - # # 9-Power_On_Hours 97 201 Up 104 # # 184-End-to-End_Error 0 0 - # # 187-Reported_Uncorrect 3 6 Up 3 # # 190-Airflow_Temperature_Cel 36 37 Up 1 # # 197-Current_Pending_Sector 8 0 Down 8 # # 198-Offline_Uncorrectable 8 0 Down 8 # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # # # ############################################################################################################################

I don't recall the disc packaging looking abnormal. Standard Newegg packaging, sealed drive with black holders in an small box and that box inside another. I don't think it was bubble wrapped like I think the WD 8TB reds are. So you think another preclear and see what happens? Sent from my iPhone using Tapatalk

New disk. I don't think I've had pending sectors go up before. Any recommendations? Preclear ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdi # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [35:52:11 @ 61 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [12:22:15 @ 179 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [43:42:25 @ 50 MB/s] SUCCESS # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 92:08:13 | Total elapsed time: 92:08:14 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 24 Up 24 # # 9-Power_On_Hours 0 92 Up 92 # # 184-End-to-End_Error 0 0 - # # 187-Reported_Uncorrect 0 3 Up 3 # # 190-Airflow_Temperature_Cel 28 39 Up 11 # # 197-Current_Pending_Sector 0 8 Up 8 # # 198-Offline_Uncorrectable 0 8 Up 8 # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear finished succesfully. Attributes # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 077 064 044 Pre-fail Always Never 227500304 3 Spin up time 0x0003 098 098 000 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 1 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 24 7 Seek error rate 0x000f 075 060 045 Pre-fail Always Never 29453291 9 Power on hours 0x0032 100 100 000 Old age Always Never 95 (130 214 0) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 1 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 097 097 000 Old age Always Never 3 188 Command timeout 0x0032 100 100 000 Old age Always Never 0 0 0 189 High fly writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow temperature cel 0x0022 064 059 040 Old age Always Never 36 (min/max 27/41) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 941 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 0 193 Load cycle count 0x0032 100 100 000 Old age Always Never 15 194 Temperature celsius 0x0022 036 041 000 Old age Always Never 36 (0 27 0 0 0) 195 Hardware ECC recovered 0x001a 032 005 000 Old age Always Never 227500304 197 Current pending sector 0x0012 100 100 000 Old age Always Never 8 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 8 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 92h+36m+50.052s 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 15628053320 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 31872235519

I think this may be solved. I only had 1 gig of ram in the server but I don't think that is enough for a NAS even though that is what the recommendations say. I found through the fix common problems app that rootfs was 100% full. I threw in another 2 gigs of ram and now rootfs is at 25% and the server has been up and acting normal for a week or so.

Network access went down again. Not much to go on in the log. It looks like the drives spun down and that was about it. Also, intermittently windows will ask for my user/pass on this server even though nothing is set. Dec 8 21:02:48 Tower root: plugin: running: anonymous Dec 8 21:02:59 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove dynamix.system.stats.plg Dec 8 21:02:59 Tower root: plugin: running: anonymous Dec 8 21:03:20 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove ca.backup.plg Dec 8 21:03:20 Tower root: plugin: running: anonymous Dec 8 21:03:29 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove ca.cleanup.appdata.plg Dec 8 21:03:29 Tower root: plugin: running: anonymous Dec 8 21:03:35 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove community.applications.plg Dec 8 21:03:35 Tower root: plugin: running: anonymous Dec 8 21:09:30 Tower kernel: mdcmd (50): spindown 0 Dec 8 21:09:31 Tower kernel: mdcmd (51): spindown 1 Dec 8 21:09:32 Tower kernel: mdcmd (52): spindown 2 Dec 8 21:09:32 Tower kernel: mdcmd (53): spindown 3 Dec 8 21:09:32 Tower kernel: mdcmd (54): spindown 4 Dec 8 21:09:33 Tower kernel: mdcmd (55): spindown 5 Dec 8 21:09:34 Tower kernel: mdcmd (56): spindown 6 Dec 8 21:09:34 Tower kernel: mdcmd (57): spindown 7 Dec 8 21:09:35 Tower kernel: mdcmd (58): spindown 11 Dec 8 21:59:28 Tower kernel: mdcmd (59): spindown 4 Dec 8 21:59:29 Tower kernel: mdcmd (60): spindown 6 Dec 8 22:06:03 Tower kernel: mdcmd (61): spindown 3 Dec 8 22:06:03 Tower kernel: mdcmd (62): spindown 5 Dec 8 22:20:34 Tower kernel: mdcmd (63): spindown 8 Dec 8 22:20:34 Tower kernel: mdcmd (64): spindown 9 Dec 8 22:20:35 Tower kernel: mdcmd (65): spindown 10 Dec 8 22:20:35 Tower kernel: mdcmd (66): spindown 12 Dec 8 22:20:36 Tower kernel: mdcmd (67): spindown 13 Dec 8 23:30:24 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Dec 8 23:30:56 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

Hmmmm....not sure if you are telling me to search better or you pointed me to the fix. Tricky!!! I had already uninstalled the stats. I'll wait and see if somehow that was related to the shares dying before reinstalling.

I am on another thread where after 4-5 parity checks with correction the server finally decided that it corrected parity. I don't want to combine the two issues if it isn't really the same thing but on a basic level they seem to be. Webgui reports errors which should have been corrected? I ran it again and it said there were 2 synch errors. I ran it again and the pushbullet update says the errors were corrected but the final report and webgui still state 2 synch errors. Are these two new synch errors or is the report on the webgui just faulty? See the 11:28 entry reports two but the 00:20 entry says two were fixed. This is from archived notifications. 08-12-2016 11:28 unRAID Parity check Notice [TOWERTEST] - Parity check finished (2 errors) Duration: 17 hours, 58 minutes, 45 seconds. Average speed: 123.6 MB/s warning 08-12-2016 00:20 unRAID Status Notice [TOWERTEST] - array health report [PASS] Array has 7 disks (including parity & cache) normal Parity - WDC_WD80EFZX-68UW8N0_VLG09Y0Y (sdf) - active 36 C [OK] Parity2 - WDC_WD80EFZX-68UW8N0_VKKTZG6Y (sdb) - active 35 C [OK] Disk 1 - HGST_HDN724040ALE640_PK2334PCKJT1JB (sdg) - active 38 C [OK] Disk 2 - HGST_HDN724040ALE640_PK2334PCKH8JJB (sdh) - active 38 C [OK] Disk 3 - WDC_WD80EFZX-68UW8N0_VKJ9E38X (sde) - active 32 C [OK] Disk 4 - WDC_WD80EFZX-68UW8N0_VK0BB1NY (sdc) - active 31 C [OK] Cache - MKNSSDRE1TB_MK160906100224D46 (sdd) - active 28 C [OK] Parity check in progress. Total size: 8 TB Elapsed time: 6 hours, 51 minutes Current position: 3.40 TB (42.5 %) Estimated speed: 106.1 MB/sec Estimated finish: 12 hours, 3 minutes Sync errors corrected: 2

Sorry to keep bumping my own thread but I just noticed a ton of these "dynamix.system.stats" entries in the log. This doesn't look normal to me? It has an entry about every minute for literally days. ec 6 19:31:08 Tower kernel: mdcmd (51): spindown 1 Dec 6 19:31:08 Tower kernel: mdcmd (52): spindown 2 Dec 6 19:31:10 Tower kernel: mdcmd (53): spindown 11 Dec 6 19:32:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:33:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:34:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:35:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:36:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:37:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:38:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:39:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:40:02 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:41:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:42:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:42:23 Tower kernel: mdcmd (54): spindown 7 Dec 6 19:42:25 Tower kernel: mdcmd (55): spindown 4 Dec 6 19:42:26 Tower kernel: mdcmd (56): spindown 6 Dec 6 19:42:31 Tower kernel: mdcmd (57): spindown 3 Dec 6 19:42:32 Tower kernel: mdcmd (58): spindown 5 Dec 6 19:42:38 Tower kernel: mdcmd (59): spindown 8 Dec 6 19:42:38 Tower kernel: mdcmd (60): spindown 9 Dec 6 19:42:39 Tower kernel: mdcmd (61): spindown 10 Dec 6 19:42:39 Tower kernel: mdcmd (62): spindown 12 Dec 6 19:42:40 Tower kernel: mdcmd (63): spindown 13 Dec 6 19:43:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:44:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:45:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:46:01 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Dec 6 19:47:16 Tower crond[1456]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null