ccsnet

Members
 View Profile  See their activity

  • Posts

    136

  • Joined

  • Last visited

 Content Type 

Report Comments posted by ccsnet

    Unraid OS version 6.10.0-rc2 available

    in Prereleases

    Posted · Edited by ccsnet

    25 minutes ago, Squid said:

    It was a clean shutdown (assuming that is the diagnostics immediately after it booting back up), so the system didn't crash or anything....

    Agreed but triggered by the VM and not the host hence the post here given that I am running the RC.

     

    If its not a glitch / bug thats fine but thought I would post just in case.

     

    BTW I think you can reproduce by changing the UUID.

     

    Thanks as ever Squid.

     

    T

    Unraid OS version 6.10.0-rc2 available

    in Prereleases

    Posted

    On 11/9/2021 at 11:32 AM, ich777 said:

    AMD cards up to series 6000 have the reset bug which prevents them from being properly reset if the VM is stopped or killed and the host have to be rebooted in order to get it working in a VM again.

    Here is the plugin from the CA App, keep in mind that if you restart the VM many times the plugin can also fail because this is only a workaround and there is no other real solution to this:

    grafik.png.95be45ee4d777fdd1e8b93410cd9fd5d.png

    Thanks... Card seems better in win 10 but still having issues firing up in win 11.

     

    Ill try a clean build out at the weekend and report back. 

     

    T

    • Like 1

    Unraid OS version 6.10.0-rc2 available

    in Prereleases

    Posted · Edited by ccsnet

    22 hours ago, ccsnet said:

    Hi... 

     

    Made the jump to rc2... Love it. 

     

    I did have an issue with win 11 when shutting down it seems to take the unraid ui down (ie tested with dockers still up) until I reboot. 

     

    Do I share diags here or on another thread? 

     

    Re the conversation about cloud... Can we tie key features / access to the 2fa of the forum ensuring if there is a security event that will stop any thing serious? 

     

    T

    So spent some of the day trouble shooting. 

     

    After a number of ui crashes and hard power offs I think it has some thing to do with either shutdown or when I do a force shutdown. 

     

    I've took all bar my graphics (amd 5700 xt) and a sata card out that I need in case it was device reseting issues. 

     

    I've tried with both Windows 10 and 11 fully patched and can replicate. 

     

    As the graphics card is new (borrowed so new to me) I'm not sure it is that or the rc but it was pretty stable before. 

     

    Any thoughts as to if this is a rc bug or a general problem?

     

    Ps hope to have an nvidia 1060 soon if it is a card issue. 

     

    Thanks

     

    T

     

    Unraid OS version 6.10.0-rc2 available

    in Prereleases

    Posted

    Hi... 

     

    Made the jump to rc2... Love it. 

     

    I did have an issue with win 11 when shutting down it seems to take the unraid ui down (ie tested with dockers still up) until I reboot. 

     

    Do I share diags here or on another thread? 

     

    Re the conversation about cloud... Can we tie key features / access to the 2fa of the forum ensuring if there is a security event that will stop any thing serious? 

     

    T

    Unraid OS version 6.7.0-rc6 available

    in Prereleases

    Posted · Edited by ccsnet

    Hi all,

     

    I think I have a bit of an odd one.

     

    Once I replaced my faulty usb many of my stability issues went away how ever after updating every so often I seem to loose my shares but every thing else seems to be working.

     

    Ie Dockers seem fine and dispite the attached image I know Emby is running as I am watching it right now.

     

    I can not get the syslog to show any thing (it is a blank page) and diags will not generate.

     

    Any thoughts ie is the the RC or another issue ?

     

    Thanks

     

    T

     

    Edit. Managed to get access to the syslog once I rebooted. That reboot had to be done from the console as it would not work from the web interface.

     

    Crfs uninitialised was in the log towards the end so I will have a look in the forum.

    Screenshot_20190330-192737.png

    Unraid OS version 6.7.0-rc4 available

    in Prereleases

    Posted · Edited by ccsnet

    22 hours ago, ccsnet said:

    Hi all. 

     

    Since I took the usb 3 card out I sent to have had a lot more stable machine although backups are still taking an age and Plex is not very responsive (network error when playing).

     

    As a result I have been looking at CA Advisor and mono-sgen seems to be holding on to the CPU about 28% of the time (or it may be using 28% not had chance to look then graph up).

     

    I did a quick search on the forum and found it had been an issue a few versions back.

     

    What does mono-sgen do and what should be the right stats so I can feed back if it's an issue with the RC ?

     

    Thanks

     

    Terran

     

     

     

     

    For any one following - I THINK the above relates to Duplicati (Emby unobody    2645  2642  0 16:35 ?        00:00:00 mono Duplicati.Server.exe --webservice-interface=any --server-datafolder=/configses it too)...

     

    nobody 2645 2642 0 16:35 ? 00:00:00 mono Duplicati.Server.exe --webservice-interface=any --server-datafolder=/config

     

    I hope that helps any one else following with the same question in relation to Unraid specifically.

     

    Terran

     

     

    Unraid OS version 6.7.0-rc4 available

    in Prereleases

    Posted · Edited by ccsnet

    Thanks for the suggestion... I did and know it relates to a garbage collector frame work however specific info as to how it relates to unraid except parts I found around emby seem hard to find. Unfortunately I do not run emby hence the question.

     

    Thanks

     

    T

    Unraid OS version 6.7.0-rc4 available

    in Prereleases

    Posted

    On 2/17/2019 at 3:16 PM, ccsnet said:

    Well mine didnt stay up long... very odd.

     

    Only update I did today was the CA Community Apps Plugin as I have been trying to keep it simple.

     

    Tried GUI safe mode but no web interface or shares came up.

     

    Diags taken about 20 mins before I found it hung plus some other logs from today.

     

    NB I'm going to try booting it in to Unraid no GUI mode to see if that makes a difference. 

     

    Thanks

     

    Terran

    tbmaindoma-diagnostics-20190217-1421.zip

    Hi all. 

     

    Since I took the usb 3 card out I sent to have had a lot more stable machine although backups are still taking an age and Plex is not very responsive (network error when playing).

     

    As a result I have been looking at CA Advisor and mono-sgen seems to be holding on to the CPU about 28% of the time (or it may be using 28% not had chance to look then graph up).

     

    I did a quick search on the forum and found it had been an issue a few versions back.

     

    What does mono-sgen do and what should be the right stats so I can feed back if it's an issue with the RC ?

     

    Thanks

     

    Terran

     

     

     

     

    Unraid OS version 6.7.0-rc4 available

    in Prereleases

    Posted

    Thanks Frank... i'll look at making that change in a bit - for now I have a second machine capturing it.

     

    That said I took out a USB 3 card (PCIE) that I think Unraid had issues with following the upgrade to RC4. Seems Ok but I need to monitor / reboot a few times to see how things are.

     

    I have how ever come to conclusion its time for a hardware upgrade so i'll be looking at that over the next few months once I know what I want to get out of it. (Current box is 6 years old).

     

    Thanks again

     

    Terran

    Unraid OS version 6.7.0-rc4 available

    in Prereleases

    Posted

    57 minutes ago, ccsnet said:

    So its hung twice since this AM with the HD seemingly busy so I have enabled local logging and installed Kiwi to be a remote syslog tool.

     

    Lets see what that brings.

     

    Terran

    syslog-20190217-124731.txt

    Well mine didnt stay up long... very odd.

     

    Only update I did today was the CA Community Apps Plugin as I have been trying to keep it simple.

     

    Tried GUI safe mode but no web interface or shares came up.

     

    Diags taken about 20 mins before I found it hung plus some other logs from today.

     

    NB I'm going to try booting it in to Unraid no GUI mode to see if that makes a difference. 

     

    Thanks

     

    Terran

    tbmaindoma-diagnostics-20190217-1421.zip

    Unraid OS version 6.7.0-rc3 available

    in Prereleases

    Posted

    On 2/11/2019 at 9:50 PM, ccsnet said:

    Not sure if this is any help but a positive from my point of view is that Docker to USB hard drive transfers seem quicker now in Krusader. I've yet to test again in Duplicati which was also giving me speed issues to USB but I can not do that until all my data is re added from my external drive.

     

    Thanks

     

    Terran

    So I logged in a couple of times last night to check on progress of a big copy using Krusader and the system felt a little sluggish - on the final log in I got the 504 gateway time out issue. 

     

    As a result I have managed to grab my diags and attach them here for review.

     

    powerdown did not work either so I ended up hard rebooting.

     

    Thanks

     

    Terran

    tbmaindoma-diagnostics-20190214-1853.zip

    Unraid OS version 6.7.0-rc3 available

    in Prereleases

    Posted

    Not sure if this is any help but a positive from my point of view is that Docker to USB hard drive transfers seem quicker now in Krusader. I've yet to test again in Duplicati which was also giving me speed issues to USB but I can not do that until all my data is re added from my external drive.

     

    Thanks

     

    Terran

    Unraid OS version 6.7.0-rc2 available

    in Prereleases

    Posted

    15 minutes ago, Squid said:

    I'd consider replacing disk 2 

    
197 Current_Pending_Sector  -O--C-   100   100   000    -    48
198 Offline_Uncorrectable   ----C-   100   100   000    -    48

    As for the flash, as mentioned try a different port, preferably USB2

    It sounded a bit off when I started it... Shame... Run really well for some time.

     

    In the mean time I've took your advice and moved the key to a usb 2.

     

    Thanks

     

    Terran

    Unraid OS version 6.7.0-rc2 available

    in Prereleases

    Posted

    24 minutes ago, Squid said:

    Looks like your flash drive is dropping offline.  Try a different port.  Ideally USB2

    Looks like your disk 2 is dropping offline, causing the read errors (and presumably it being disabled).  Could simply be a crappy connection to the drive / port / power

     

    As @Frank1940 said, we'd like to see your diagnostics.

    Thanks... Apologies as this is the first time... Do I upload the whole zip file that was generated to here ?

     

    I'll check disk 2.

     

    Thanks

     

    T

    Unraid OS version 6.7.0-rc2 available

    in Prereleases

    Posted

    19 hours ago, Frank1940 said:

    Any time something like this happens, try to get a Diagnostics report.   Tools    >>>    Diagnostics

     

    Without that report, the Gurus have nothing to even start to troubleshoot your problem.  If you have already purchase your key, you would not have to purchase a new license if your flash drive is defective.  (You have purchased a licence for life.) 

    Hi... Crashed again... Seemed to have been ok until the am.

     

    This extract is from the syslog. You will see that at 1830 ish I logged on.

     

    ""

    Jan 31 00:00:01 tbmaindoma Plugin Auto Update: Checking for available plugin updates

    Jan 31 00:00:03 tbmaindoma Plugin Auto Update: unassigned.devices.plg version 2019.01.30 does not meet age requirements to update

    Jan 31 00:00:03 tbmaindoma Plugin Auto Update: Community Applications Plugin Auto Update finished

    Jan 31 00:30:52 tbmaindoma kernel: mdcmd (43): spindown 3

    Jan 31 08:42:54 tbmaindoma kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

    Jan 31 08:42:54 tbmaindoma kernel: ata6.00: irq_stat 0x40000001

    Jan 31 08:42:54 tbmaindoma kernel: ata6.00: failed command: READ DMA EXT

    Jan 31 08:42:54 tbmaindoma kernel: ata6.00: cmd 25/00:00:f8:d8:e9/00:01:e4:00:00/e0 tag 22 dma 131072 in

    Jan 31 08:42:54 tbmaindoma kernel:         res 51/40:00:90:d9:e9/00:00:e4:00:00/00 Emask 0x9 (media error)

    Jan 31 08:42:54 tbmaindoma kernel: ata6.00: status: { DRDY ERR }

    Jan 31 08:42:54 tbmaindoma kernel: ata6.00: error: { UNC }

    Jan 31 08:42:54 tbmaindoma kernel: ata6.00: configured for UDMA/133

    Jan 31 08:42:54 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

    Jan 31 08:42:54 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#22 Sense Key : 0x3 [current]

    Jan 31 08:42:54 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#22 ASC=0x11 ASCQ=0x4

    Jan 31 08:42:54 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#22 CDB: opcode=0x28 28 00 e4 e9 d8 f8 00 01 00 00

    Jan 31 08:42:54 tbmaindoma kernel: print_req_error: I/O error, dev sdg, sector 3840530832

    Jan 31 08:42:54 tbmaindoma kernel: ata6: EH complete

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530768

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530776

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530784

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530792

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530800

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530808

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530816

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530824

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530832

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530840

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530848

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530856

    Jan 31 08:42:54 tbmaindoma kernel: md: disk2 read error, sector=3840530864

    Jan 31 08:42:58 tbmaindoma kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

    Jan 31 08:42:58 tbmaindoma kernel: ata6.00: irq_stat 0x40000001

    Jan 31 08:42:58 tbmaindoma kernel: ata6.00: failed command: READ DMA EXT

    Jan 31 08:42:58 tbmaindoma kernel: ata6.00: cmd 25/00:80:38:ee:e9/00:00:e4:00:00/e0 tag 25 dma 65536 in

    Jan 31 08:42:58 tbmaindoma kernel:         res 51/40:00:60:ee:e9/00:00:e4:00:00/00 Emask 0x9 (media error)

    Jan 31 08:42:58 tbmaindoma kernel: ata6.00: status: { DRDY ERR }

    Jan 31 08:42:58 tbmaindoma kernel: ata6.00: error: { UNC }

    Jan 31 08:42:58 tbmaindoma kernel: ata6.00: configured for UDMA/133

    Jan 31 08:42:58 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

    Jan 31 08:42:58 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#25 Sense Key : 0x3 [current]

    Jan 31 08:42:58 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#25 ASC=0x11 ASCQ=0x4

    Jan 31 08:42:58 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#25 CDB: opcode=0x28 28 00 e4 e9 ee 38 00 00 80 00

    Jan 31 08:42:58 tbmaindoma kernel: print_req_error: I/O error, dev sdg, sector 3840536160

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536096

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536104

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536112

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536120

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536128

    Jan 31 08:42:58 tbmaindoma kernel: ata6: EH complete

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536136

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536144

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536152

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536160

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536168

    Jan 31 08:42:58 tbmaindoma kernel: md: disk2 read error, sector=3840536176

    Jan 31 08:43:01 tbmaindoma kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

    Jan 31 08:43:01 tbmaindoma kernel: ata6.00: irq_stat 0x40000001

    Jan 31 08:43:01 tbmaindoma kernel: ata6.00: failed command: READ DMA EXT

    Jan 31 08:43:01 tbmaindoma kernel: ata6.00: cmd 25/00:10:b8:f3:e9/00:00:e4:00:00/e0 tag 28 dma 8192 in

    Jan 31 08:43:01 tbmaindoma kernel:         res 51/40:00:b8:f3:e9/00:00:e4:00:00/00 Emask 0x9 (media error)

    Jan 31 08:43:01 tbmaindoma kernel: ata6.00: status: { DRDY ERR }

    Jan 31 08:43:01 tbmaindoma kernel: ata6.00: error: { UNC }

    Jan 31 08:43:01 tbmaindoma kernel: ata6.00: configured for UDMA/133

    Jan 31 08:43:01 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

    Jan 31 08:43:01 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#28 Sense Key : 0x3 [current]

    Jan 31 08:43:01 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#28 ASC=0x11 ASCQ=0x4

    Jan 31 08:43:01 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#28 CDB: opcode=0x28 28 00 e4 e9 f3 b8 00 00 10 00

    Jan 31 08:43:01 tbmaindoma kernel: print_req_error: I/O error, dev sdg, sector 3840537528

    Jan 31 08:43:01 tbmaindoma kernel: ata6: EH complete

    Jan 31 08:43:01 tbmaindoma kernel: md: disk2 read error, sector=3840537464

    Jan 31 08:43:01 tbmaindoma kernel: md: disk2 read error, sector=3840537472

    Jan 31 08:43:05 tbmaindoma kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

    Jan 31 08:43:05 tbmaindoma kernel: ata6.00: irq_stat 0x40000001

    Jan 31 08:43:05 tbmaindoma kernel: ata6.00: failed command: READ DMA EXT

    Jan 31 08:43:05 tbmaindoma kernel: ata6.00: cmd 25/00:08:58:1a:ea/00:00:e4:00:00/e0 tag 2 dma 4096 in

    Jan 31 08:43:05 tbmaindoma kernel:         res 51/40:00:58:1a:ea/00:00:e4:00:00/00 Emask 0x9 (media error)

    Jan 31 08:43:05 tbmaindoma kernel: ata6.00: status: { DRDY ERR }

    Jan 31 08:43:05 tbmaindoma kernel: ata6.00: error: { UNC }

    Jan 31 08:43:05 tbmaindoma kernel: ata6.00: configured for UDMA/133

    Jan 31 08:43:05 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

    Jan 31 08:43:05 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#2 Sense Key : 0x3 [current]

    Jan 31 08:43:05 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#2 ASC=0x11 ASCQ=0x4

    Jan 31 08:43:05 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#2 CDB: opcode=0x28 28 00 e4 ea 1a 58 00 00 08 00

    Jan 31 08:43:05 tbmaindoma kernel: print_req_error: I/O error, dev sdg, sector 3840547416

    Jan 31 08:43:05 tbmaindoma kernel: ata6: EH complete

    Jan 31 08:43:05 tbmaindoma kernel: md: disk2 read error, sector=3840547352

    Jan 31 08:43:09 tbmaindoma kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

    Jan 31 08:43:09 tbmaindoma kernel: ata6.00: irq_stat 0x40000001

    Jan 31 08:43:09 tbmaindoma kernel: ata6.00: failed command: READ DMA EXT

    Jan 31 08:43:09 tbmaindoma kernel: ata6.00: cmd 25/00:08:b0:1f:ea/00:00:e4:00:00/e0 tag 25 dma 4096 in

    Jan 31 08:43:09 tbmaindoma kernel:         res 51/40:00:b0:1f:ea/00:00:e4:00:00/00 Emask 0x9 (media error)

    Jan 31 08:43:09 tbmaindoma kernel: ata6.00: status: { DRDY ERR }

    Jan 31 08:43:09 tbmaindoma kernel: ata6.00: error: { UNC }

    Jan 31 08:43:09 tbmaindoma kernel: ata6.00: configured for UDMA/133

    Jan 31 08:43:09 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

    Jan 31 08:43:09 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#25 Sense Key : 0x3 [current]

    Jan 31 08:43:09 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#25 ASC=0x11 ASCQ=0x4

    Jan 31 08:43:09 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#25 CDB: opcode=0x28 28 00 e4 ea 1f b0 00 00 08 00

    Jan 31 08:43:09 tbmaindoma kernel: print_req_error: I/O error, dev sdg, sector 3840548784

    Jan 31 08:43:09 tbmaindoma kernel: ata6: EH complete

    Jan 31 08:43:09 tbmaindoma kernel: md: disk2 read error, sector=3840548720

    Jan 31 08:43:12 tbmaindoma kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

    Jan 31 08:43:12 tbmaindoma kernel: ata6.00: irq_stat 0x40000001

    Jan 31 08:43:12 tbmaindoma kernel: ata6.00: failed command: READ DMA EXT

    Jan 31 08:43:12 tbmaindoma kernel: ata6.00: cmd 25/00:08:08:25:ea/00:00:e4:00:00/e0 tag 15 dma 4096 in

    Jan 31 08:43:12 tbmaindoma kernel:         res 51/40:00:08:25:ea/00:00:e4:00:00/00 Emask 0x9 (media error)

    Jan 31 08:43:12 tbmaindoma kernel: ata6.00: status: { DRDY ERR }

    Jan 31 08:43:12 tbmaindoma kernel: ata6.00: error: { UNC }

    Jan 31 08:43:12 tbmaindoma kernel: ata6.00: configured for UDMA/133

    Jan 31 08:43:12 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

    Jan 31 08:43:12 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#15 Sense Key : 0x3 [current]

    Jan 31 08:43:12 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#15 ASC=0x11 ASCQ=0x4

    Jan 31 08:43:12 tbmaindoma kernel: sd 8:0:0:0: [sdg] tag#15 CDB: opcode=0x28 28 00 e4 ea 25 08 00 00 08 00

    Jan 31 08:43:12 tbmaindoma kernel: print_req_error: I/O error, dev sdg, sector 3840550152

    Jan 31 08:43:12 tbmaindoma kernel: ata6: EH complete

    Jan 31 08:43:12 tbmaindoma kernel: md: disk2 read error, sector=3840550088

    Jan 31 18:27:08 tbmaindoma kernel: usb 4-2: Disable of device-initiated U1 failed.

    Jan 31 18:27:13 tbmaindoma kernel: usb 4-2: Disable of device-initiated U2 failed.

    Jan 31 18:27:18 tbmaindoma kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

    ### [PREVIOUS LINE REPEATED 1 TIMES] ###

    Jan 31 18:27:24 tbmaindoma kernel: usb 4-2: device not accepting address 2, error -62

    Jan 31 18:27:24 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    ### [PREVIOUS LINE REPEATED 1 TIMES] ###

    Jan 31 18:27:24 tbmaindoma kernel: usb 4-2: device not accepting address 2, error -71

    Jan 31 18:27:25 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    ### [PREVIOUS LINE REPEATED 1 TIMES] ###

    Jan 31 18:27:25 tbmaindoma kernel: usb 4-2: device not accepting address 2, error -71

    Jan 31 18:27:25 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    ### [PREVIOUS LINE REPEATED 1 TIMES] ###

    Jan 31 18:27:26 tbmaindoma kernel: usb 4-2: device not accepting address 2, error -71

    Jan 31 18:27:26 tbmaindoma kernel: usb 4-2: USB disconnect, device number 2

    Jan 31 18:27:26 tbmaindoma kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00

    Jan 31 18:27:26 tbmaindoma kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 88 0a 00 00 01 00

    Jan 31 18:27:26 tbmaindoma kernel: print_req_error: I/O error, dev sdb, sector 34826

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32778) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32779) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32780) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32781) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32782) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32783) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32784) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32785) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32786) failed

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32787) failed

    Jan 31 18:27:26 tbmaindoma nginx: 2019/01/31 18:27:26 [error] 9511#9511: *140727 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.65, server: , request: "POST /webGui/include/DashUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.10", referrer: "http://192.168.1.10/Dashboard"

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): FAT read failed (blocknr 3043)

    Jan 31 18:27:26 tbmaindoma php-fpm[9485]: [WARNING] [pool www] child 32643 exited on signal 7 (SIGBUS) after 54.009455 seconds from start

    Jan 31 18:27:26 tbmaindoma crond[1682]: exit status 135 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownc.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownl.cfg

    Jan 31 18:27:26 tbmaindoma rc.diskinfo[7688]: SIGHUP received, forcing refresh of disks info.

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownt.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/chrisw.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/downloads.cfg

    Jan 31 18:27:26 tbmaindoma sSMTP[1845]: Creating SSL connection to host

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/media.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/misc.cfg

    Jan 31 18:27:26 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/photos.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/shared.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/temp.cfg

    Jan 31 18:27:26 tbmaindoma emhttpd: Starting services...

    Jan 31 18:27:26 tbmaindoma emhttpd: shcmd (2500): /etc/rc.d/rc.samba restart

    Jan 31 18:27:26 tbmaindoma root: cp: cannot create regular file '/boot/config': Input/output error

    Jan 31 18:27:26 tbmaindoma kernel: FAT-fs (sdb1): FAT read failed (blocknr 3273)

    Jan 31 18:27:26 tbmaindoma kernel: ------------[ cut here ]------------

    Jan 31 18:27:26 tbmaindoma kernel: bdi-block not registered

    Jan 31 18:27:26 tbmaindoma kernel: WARNING: CPU: 1 PID: 1907 at fs/fs-writeback.c:2194 __mark_inode_dirty+0x151/0x1d2

    Jan 31 18:27:26 tbmaindoma kernel: Modules linked in: iptable_mangle xt_CHECKSUM ipt_REJECT xt_nat ip6table_filter ip6_tables veth ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod bonding x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_uncore intel_rapl_perf r8169 ahci libahci i2c_i801 i2c_core ie31200_edac realtek video thermal button fan backlight pcc_cpufreq [last unloaded: kvm]

    Jan 31 18:27:26 tbmaindoma kernel: CPU: 1 PID: 1907 Comm: cp Not tainted 4.19.17-Unraid #1

    Jan 31 18:27:26 tbmaindoma kernel: Hardware name: Dell Inc. Inspiron 660/084J0R      , BIOS A13 05/22/2018

    Jan 31 18:27:26 tbmaindoma kernel: RIP: 0010:__mark_inode_dirty+0x151/0x1d2

    Jan 31 18:27:26 tbmaindoma kernel: Code: e8 e7 e6 ff ff 48 89 c5 48 8b 00 f6 40 3c 02 75 1b 48 8b 55 08 80 e2 01 75 12 48 8b 70 30 48 c7 c7 4d 6b d4 81 e8 5f 9d ee ff <0f> 0b 48 8b 05 ed 11 ca 00 45 85 ed 48 89 83 c0 00 00 00 74 0e 48

    Jan 31 18:27:26 tbmaindoma kernel: RSP: 0018:ffffc900022b78e0 EFLAGS: 00010282

    Jan 31 18:27:26 tbmaindoma kernel: RAX: 0000000000000000 RBX: ffff88822396c358 RCX: 0000000000000007

    Jan 31 18:27:26 tbmaindoma kernel: RDX: 0000000000000000 RSI: ffff8882260964e0 RDI: ffff8882260964e0

    Jan 31 18:27:26 tbmaindoma kernel: RBP: ffff88820666a858 R08: 0000000000000003 R09: 0000000000020500

    Jan 31 18:27:26 tbmaindoma kernel: R10: 0000000000000431 R11: 0000000000014c80 R12: 0000000000000001

    Jan 31 18:27:26 tbmaindoma kernel: R13: 0000000000000000 R14: ffff88822396c3d8 R15: 0000000000000000

    Jan 31 18:27:26 tbmaindoma kernel: FS:  000014bd200ea740(0000) GS:ffff888226080000(0000) knlGS:0000000000000000

    Jan 31 18:27:26 tbmaindoma kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

    Jan 31 18:27:26 tbmaindoma kernel: CR2: 000014bd201e8170 CR3: 0000000221e5e003 CR4: 00000000001606e0

    Jan 31 18:27:26 tbmaindoma kernel: Call Trace:

    Jan 31 18:27:26 tbmaindoma kernel: fat_alloc_clusters+0x2db/0x3c7

    Jan 31 18:27:26 tbmaindoma kernel: ? kmem_cache_alloc+0xe7/0xf3

    Jan 31 18:27:26 tbmaindoma kernel: ? bio_free+0x30/0x4e

    Jan 31 18:27:26 tbmaindoma kernel: fat_add_new_entries+0x87/0x290

    Jan 31 18:27:26 tbmaindoma kernel: ? fat__get_entry+0x71/0x207

    Jan 31 18:27:26 tbmaindoma kernel: fat_add_entries+0x31f/0x474

    Jan 31 18:27:26 tbmaindoma kernel: ? fat_time_unix2fat+0x4b/0x123

    Jan 31 18:27:26 tbmaindoma kernel: vfat_add_entry+0x262/0xb64

    Jan 31 18:27:26 tbmaindoma kernel: vfat_create+0x65/0x162

    Jan 31 18:27:26 tbmaindoma kernel: ? __dentry_kill+0x127/0x130

    Jan 31 18:27:26 tbmaindoma kernel: path_openat+0x6bd/0xc16

    Jan 31 18:27:26 tbmaindoma kernel: do_filp_open+0x4c/0xa9

    Jan 31 18:27:26 tbmaindoma kernel: ? _copy_to_user+0x22/0x28

    Jan 31 18:27:26 tbmaindoma kernel: do_sys_open+0x132/0x1ce

    Jan 31 18:27:26 tbmaindoma kernel: do_syscall_64+0x57/0xe6

    Jan 31 18:27:26 tbmaindoma kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9

    Jan 31 18:27:26 tbmaindoma kernel: RIP: 0033:0x14bd201f3380

    Jan 31 18:27:26 tbmaindoma kernel: Code: 25 00 00 41 00 3d 00 00 41 00 74 36 48 8d 05 87 c3 0d 00 8b 00 85 c0 75 5a 89 f2 b8 01 01 00 00 48 89 fe bf 9c ff ff ff 0f 05 <48> 3d 00 f0 ff ff 0f 87 84 00 00 00 48 83 c4 68 5b 5d c3 0f 1f 44

    Jan 31 18:27:26 tbmaindoma kernel: RSP: 002b:00007ffc1e8473e0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101

    Jan 31 18:27:26 tbmaindoma kernel: RAX: ffffffffffffffda RBX: 00007ffc1e8479c0 RCX: 000014bd201f3380

    Jan 31 18:27:26 tbmaindoma kernel: RDX: 00000000000000c1 RSI: 00007ffc1e847f16 RDI: 00000000ffffff9c

    Jan 31 18:27:26 tbmaindoma kernel: RBP: 00007ffc1e847830 R08: 00007ffc1e8479c0 R09: 0000000000000000

    Jan 31 18:27:26 tbmaindoma kernel: R10: 00000000000001ff R11: 0000000000000246 R12: 00000000000001ff

    Jan 31 18:27:26 tbmaindoma kernel: R13: 0000000000000001 R14: 0000000000008000 R15: 0000000000000004

    Jan 31 18:27:26 tbmaindoma kernel: ---[ end trace c2c780389234cbc7 ]---

    Jan 31 18:27:26 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    Jan 31 18:27:26 tbmaindoma kernel: usb 4-2: device not accepting address 4, error -71

    Jan 31 18:27:26 tbmaindoma sSMTP[1845]: SSL connection using ECDHE-RSA-AES256-GCM-SHA384

    Jan 31 18:27:26 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    ### [PREVIOUS LINE REPEATED 1 TIMES] ###

    Jan 31 18:27:27 tbmaindoma kernel: FAT-fs (sdb1): FAT read failed (blocknr 3273)

    Jan 31 18:27:27 tbmaindoma kernel: usb 4-2: device not accepting address 5, error -71

    Jan 31 18:27:27 tbmaindoma kernel: usb usb4-port2: attempt power cycle

    Jan 31 18:27:28 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    Jan 31 18:27:28 tbmaindoma root: Starting Samba:  /usr/sbin/nmbd -D

    Jan 31 18:27:28 tbmaindoma root:                  /usr/sbin/smbd -D

    Jan 31 18:27:28 tbmaindoma root:                  /usr/sbin/winbindd -D

    Jan 31 18:27:28 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    Jan 31 18:27:28 tbmaindoma kernel: usb 4-2: device not accepting address 6, error -71

    Jan 31 18:27:28 tbmaindoma kernel: usb 4-2: Device not responding to setup address.

    ### [PREVIOUS LINE REPEATED 1 TIMES] ###

    Jan 31 18:27:29 tbmaindoma sSMTP[1845]: Sent mail for [email protected] (221 perfora.net Service closing transmission channel) uid=0 username=xxx outbytes=594

    Jan 31 18:27:29 tbmaindoma kernel: usb 4-2: device not accepting address 7, error -71

    Jan 31 18:27:29 tbmaindoma kernel: usb usb4-port2: unable to enumerate USB device

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/admin.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownc.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownl.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownt.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/chrisw.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/downloads.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/media.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/misc.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/photos.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/shared.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/temp.cfg

    Jan 31 18:27:29 tbmaindoma emhttpd: Starting services...

    Jan 31 18:27:29 tbmaindoma emhttpd: shcmd (2511): /etc/rc.d/rc.samba restart

    Jan 31 18:27:29 tbmaindoma root: cp: cannot create regular file '/boot/config': Input/output error

    Jan 31 18:27:29 tbmaindoma kernel: FAT-fs (sdb1): FAT read failed (blocknr 3273)

    Jan 31 18:27:31 tbmaindoma root: Starting Samba:  /usr/sbin/nmbd -D

    Jan 31 18:27:31 tbmaindoma root:                  /usr/sbin/smbd -D

    Jan 31 18:27:31 tbmaindoma root:                  /usr/sbin/winbindd -D

    Jan 31 18:27:31 tbmaindoma kernel: fat__get_entry: 428 callbacks suppressed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32768) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32769) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32770) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32771) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32772) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32773) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32774) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32775) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32776) failed

    Jan 31 18:27:31 tbmaindoma kernel: FAT-fs (sdb1): Directory bread(block 32777) failed

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/admin.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownc.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownl.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/brownt.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/chrisw.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/downloads.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/media.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/misc.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/photos.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/shared.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/temp.cfg

    Jan 31 18:27:32 tbmaindoma emhttpd: Starting services...

    Jan 31 18:27:32 tbmaindoma emhttpd: shcmd (2521): /etc/rc.d/rc.samba restart

    Jan 31 18:27:32 tbmaindoma root: cp: cannot create regular file '/boot/config': Input/output error

    Jan 31 18:27:32 tbmaindoma kernel: FAT-fs (sdb1): FAT read failed (blocknr 3273)"

     

     

    Unraid OS version 6.7.0-rc2 available

    in Prereleases

    Posted

    Hi. I ended up moving to the RC because as a new user there was not much to loose.

     

    How ever I have found my usb boot drive dropping after a day or so where as under 6.6.6 it was fine for the few weeks I ran it.

     

    My question before I shell out in a new key is could this be a bug or is it my key is not compatible in some way given that I assume there are new drivers in this release ?

     

    Thanks

     

    Terran

     

    Ps I'm really liking the new gui