Jump to content
  • Unraid OS version 6.7.0-rc2 available


    limetech

    Mainly bug fixes, webGUI tweaks.

     

    Other highlights:

    • Added the '--allow-discards' option to LUKS open.  This should only have any effect when using encrypted Cache device/pool with SSD devices.  It allows a file system to notice if underlying device supports TRIM and if so, passes TRIM commands down.
    • Fixed issue where files created through OS X had improper permission set.

     

    Version 6.7.0-rc2 2019-01-24

    Linux kernel:

    • version: 4.19.17
    • patch: btrfs: prevent failed readahead from spamming syslog
    • patch: PCI: Quirk Silicon Motion SM2262/SM2263 NVMe controller reset

    Management:

    • emhttpd: Add --allow-discard luksOpen option
    • emhttpd: Increase number of queued inotify IN_MOVED_TO events from 16 to 1024 for /var/local/emhttp directory.
    • firmware:
      added BCM20702A0-0a5c-21e8.hcd
      added BCM20702A1-0a5c-21e8.hcd
    • smb: when Enhanced OS X interoperability set, include "fruit:nfs_aces = no" to be compatible with Unraid security model
    • webgui: Dashboard: fixed display of Wattage in UPS load
    • webgui: Fixed version display in system information
    • webgui: Dashboard: fixed wrapping of long lines
    • webgui: Docker: textual update
    • webgui: Switch button: use blue color in ON state
    • webgui: File browser: force download of files

     



    User Feedback

    Recommended Comments



    Not a bug report...

    On the docker page, 99% of it is using your mouse to move dockers up/down.

    It cancels out all other function, I can't copy/paste paths or addresses because it.

    I don't think many people are interested in adjusting their docker rows that often that all other functionality is removed. There could be a small row to the left which allows you to do the same function. 

    Share this comment


    Link to comment
    Share on other sites
    3 hours ago, marshy919 said:

    Not a bug report...

    On the docker page, 99% of it is using your mouse to move dockers up/down.

    It cancels out all other function, I can't copy/paste paths or addresses because it.

    I don't think many people are interested in adjusting their docker rows that often that all other functionality is removed. There could be a small row to the left which allows you to do the same function. 

    Sounds like a feature request. Add a column to the far left, Start Order, with numbers indicating such. That would allow sorting based on the other columns, as the number would stick with the docker, until such time as the user dragged around the Start Order number in that column. You would be dragging the number to match the docker order you wished, rather than the way it is now where you drag to docker to the slot you want.

    Share this comment


    Link to comment
    Share on other sites
    33 minutes ago, jonathanm said:

    Sounds like a feature request. Add a column to the far left, Start Order, with numbers indicating such. That would allow sorting based on the other columns, as the number would stick with the docker, until such time as the user dragged around the Start Order number in that column. You would be dragging the number to match the docker order you wished, rather than the way it is now where you drag to docker to the slot you want.

    Then something to "Apply" and the page would refresh with them sorted according to number.

    Share this comment


    Link to comment
    Share on other sites
    1 hour ago, trurl said:

    Then something to "Apply" and the page would refresh with them sorted according to number.

    Or, just click on the start order column header to sort by start order instead of sorting by some other column.

     

    Yeah, it's a pretty heavy feature request. I've already been slapped for suggesting feature creep, so I'll shut up now.

    Share this comment


    Link to comment
    Share on other sites

    Why? It's not like RC(s) here mean feature freeze that goes along with Release Candidate.

    Share this comment


    Link to comment
    Share on other sites

    Here we discuss bugs and issues.

    It is always possible to make a feature request in the designated section. This will ensure it stays "visible".

    Can't commit on when/if a feature request gets implemented.

    Share this comment


    Link to comment
    Share on other sites
    1 hour ago, BRiT said:

    Why? It's not like RC(s) here mean feature freeze that goes along with Release Candidate.

    You forget: RC doses not mean "Release Candidate", it means "Rickrolling Complainers" 😎

    • Like 4
    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites

    No. I did not forget that RC does not mean Release Candidate here. Other's have. That's why I asked why they don't ask for features.

    Share this comment


    Link to comment
    Share on other sites

    Guess Linus listened and made an even better setup to use Unraid on for your front page?

     

     

    on 6.6 or 6.7 RC ;)

     

     

    Share this comment


    Link to comment
    Share on other sites

    EDIT: After a hard reset I rolled back to 6.6.6 with no issue. Will report back on how stable the system runs for the next 6 hours while we catch a few movies. I'm guessing (unless there just happens to be a coincidental HW failure at the same time I upgraded) all will be fine as it has been.

     

    EDIT2: can a Mod please move this post to this thread. Read it start to finish and it seemed a very similar issue.

     

    EDIT3: its late so maybe I'm operating a bit slow, but reading the console output again could this be a cpu sleep state issue. Even with an e3-1241v3 cpu and never had an issue on any previous unraid version for the last couple of years?

     

    EDIT4: after successfull rollback, things are as stable as ever.

     

     

    Hi All.

     

    I've just upgraded to 6.7 RC2. I was in a trailblazing mood this afternoon.

     

    Unfortunately, after upgrading and everything seeming fine, the server locked up. In that I couldn't ping it, access GUI, telnet in (obviously given ping etc), Dockers all inaccessible OR unresponsive and VM's froze (while still outputting display BUT non responsive via any input device). I had to do a hard reset. Cancelled Parity Check. Started playing around and exploring. All was going well again. With everything.

     

    Then, an hour or so later, frozen. I tried to find some logs that would make an actual bug report worthwhile, but given I had to reset, nothing. Everything that was running on 6.6.6 should be fine on 6.7 RC2 as I didnt see anything in the release notes which required preparation so I did a straight switch to unstable and upgraded.

     

    As an aside, the server is rock solid and has been over the last 2 years, throughout all the upgrades. Monthly maintenance has shown nothing and just recently did a disk audit (1 week ago) and all was well. Upgraded from the latest stable version 6.6.6

     

    I did log into the IPMI console and that was unresponsive too. However, I did manage to capture the attached from the console output.

     

    My build is MainServer, documented here: https://forums.unraid.net/topic/35892-completed-daniels-home-setup-updated-14012016/

     

    Not sure what is going on but I am going to hard reset again and roll back.

     

    Ta

     

    D41275798_RCerror.PNG.9c2dbbece463170addaa025226d16cb7.PNG

    Edited by danioj

    Share this comment


    Link to comment
    Share on other sites

    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

     

    Share this comment


    Link to comment
    Share on other sites
    3 minutes ago, ccsnet said:

    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.

    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.) 

    Share this comment


    Link to comment
    Share on other sites

    Brill... I'll grab that next time it goes as I have rebooted it now. Thanks for the advice. 

     

    Terran

    Share this comment


    Link to comment
    Share on other sites
    On 1/30/2019 at 7:40 PM, danioj said:

    EDIT: After a hard reset I rolled back to 6.6.6 with no issue. Will report back on how stable the system runs for the next 6 hours while we catch a few movies. I'm guessing (unless there just happens to be a coincidental HW failure at the same time I upgraded) all will be fine as it has been.

     

    EDIT2: can a Mod please move this post to this thread. Read it start to finish and it seemed a very similar issue.

     

    EDIT3: its late so maybe I'm operating a bit slow, but reading the console output again could this be a cpu sleep state issue. Even with an e3-1241v3 cpu and never had an issue on any previous unraid version for the last couple of years?

     

    EDIT4: after successfull rollback, things are as stable as ever.

     

     

    Hi All.

     

    I've just upgraded to 6.7 RC2. I was in a trailblazing mood this afternoon.

     

    Unfortunately, after upgrading and everything seeming fine, the server locked up. In that I couldn't ping it, access GUI, telnet in (obviously given ping etc), Dockers all inaccessible OR unresponsive and VM's froze (while still outputting display BUT non responsive via any input device). I had to do a hard reset. Cancelled Parity Check. Started playing around and exploring. All was going well again. With everything.

     

    Then, an hour or so later, frozen. I tried to find some logs that would make an actual bug report worthwhile, but given I had to reset, nothing. Everything that was running on 6.6.6 should be fine on 6.7 RC2 as I didnt see anything in the release notes which required preparation so I did a straight switch to unstable and upgraded.

     

    As an aside, the server is rock solid and has been over the last 2 years, throughout all the upgrades. Monthly maintenance has shown nothing and just recently did a disk audit (1 week ago) and all was well. Upgraded from the latest stable version 6.6.6

     

    I did log into the IPMI console and that was unresponsive too. However, I did manage to capture the attached from the console output.

     

    My build is MainServer, documented here: https://forums.unraid.net/topic/35892-completed-daniels-home-setup-updated-14012016/

     

    Not sure what is going on but I am going to hard reset again and roll back.

     

    Ta

     

    D41275798_RCerror.PNG.9c2dbbece463170addaa025226d16cb7.PNG

    Server is still stable as all hell since rollback.

    Share this comment


    Link to comment
    Share on other sites

    Not directed at anyone in particular but make sure your BIOS is up-to-date.

    Share this comment


    Link to comment
    Share on other sites
    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@removed.com (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)"

     

     

    Share this comment


    Link to comment
    Share on other sites
    19 hours ago, Frank1940 said:

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

    19 hours ago, ccsnet said:

    Brill... I'll grab that next time it goes as I have rebooted it now. Thanks for the advice. 

     

    So why did you give us that wall of text instead?

    4 minutes ago, ccsnet said:

    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

    ...

    and on and on and on

     

    syslog snippets are seldom sufficient

    Share this comment


    Link to comment
    Share on other sites
    Squid

    Posted (edited)

    6 minutes ago, ccsnet said:

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

     

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

    6 minutes ago, ccsnet said:

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

     

    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.

    Edited by Squid
    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites
    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

    Share this comment


    Link to comment
    Share on other sites
    1 minute ago, ccsnet said:

    Do I upload the whole zip file that was generated to here

    yes

    Share this comment


    Link to comment
    Share on other sites

    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

    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites
    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

    Share this comment


    Link to comment
    Share on other sites

     

    On 1/26/2019 at 10:06 PM, Yak said:

    Loving the new look but not sure what is going on with the memory section on the dashboard. I have 24 of a possible 32 GiB of RAM installed but memory is reporting as 0 MiB with a usable size of 32.0 GiB and a maximum size of 16.0 ?

     

    Also a small issue with OpenVPN that was resolved on the relevant forum

     

    ram.jpg

    Can you post the output of

    dmidecode -qt17

    Share this comment


    Link to comment
    Share on other sites
    42 minutes ago, bonienl said:

     

    Can you post the output of

    
    dmidecode -qt17

    Memory Device
            Total Width: 64 bits
            Data Width: 64 bits
            Size: 4096 MB
            Form Factor: DIMM
            Set: None
            Locator: A0
            Bank Locator: Bank0/1
            Type: Unknown
            Type Detail: None
            Speed: 1333 MT/s
            Manufacturer: None
            Serial Number: None
            Asset Tag: None
            Part Number: None

    Memory Device
            Total Width: 64 bits
            Data Width: 64 bits
            Size: 4096 MB
            Form Factor: DIMM
            Set: None
            Locator: A1
            Bank Locator: Bank2/3
            Type: Unknown
            Type Detail: None
            Speed: 1333 MT/s
            Manufacturer: None
            Serial Number: None
            Asset Tag: None
            Part Number: None

    Memory Device
            Total Width: 64 bits
            Data Width: 64 bits
            Size: 8192 MB
            Form Factor: DIMM
            Set: None
            Locator: A2
            Bank Locator: Bank4/5
            Type: Unknown
            Type Detail: None
            Speed: 1333 MT/s
            Manufacturer: None
            Serial Number: None
            Asset Tag: None
            Part Number: None

    Memory Device
            Total Width: 64 bits
            Data Width: 64 bits
            Size: 8192 MB
            Form Factor: DIMM
            Set: None
            Locator: A3
            Bank Locator: Bank6/7
            Type: Unknown
            Type Detail: None
            Speed: 1333 MT/s
            Manufacturer: None
            Serial Number: None
            Asset Tag: None
            Part Number: None

    Share this comment


    Link to comment
    Share on other sites



    Guest
    This is now closed for further comments

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.