Mizz141 Posted December 26, 2019 Share Posted December 26, 2019 Ok, So Ive got unraid setup (again) with a new motherboard because the previous one died unexpected after a few days of use, I also switched from unraid V6.8 to 6.7 because I thought it was a compatibility issue or sth. I thought I wouldnt get these problems again but they suddenly reappeared out of basically nowhere... I have copied all the errors onto one TXT file, because I thought it would be the fastet way. Errors.txt Quote Link to comment
Mizz141 Posted December 26, 2019 Author Share Posted December 26, 2019 From what I can tell, it has to do something with the Community plugins plugin, I have installed "Fix Common Problems" but I dont seem to have access to it anymore, since my Apps tab gives out the errors I have attached... Quote Link to comment
Mizz141 Posted December 26, 2019 Author Share Posted December 26, 2019 Ok, Its probably not the Community plugins, its probably Docker Itself, I dont seem to start it up again, yet I still have access to Sonarr, Plex and qBittorrent Quote Link to comment
Mizz141 Posted December 26, 2019 Author Share Posted December 26, 2019 Ok, Im just looking at the Boot Device tab now and the Flashdrive suddenly has 18,446,744,073,709,551,616 Writes?!?! Quote Link to comment
Mizz141 Posted December 26, 2019 Author Share Posted December 26, 2019 Ok, I now have the Entire System log Downloaded here... tower-syslog-20191226-1823.zip Quote Link to comment
Mizz141 Posted December 26, 2019 Author Share Posted December 26, 2019 I think somehow my USB got F'd up, I dont want to cause more damage so I wont unplug or do anything more... Also this is the part of the Log where everything goes horribly wrong Dec 26 09:53:24 Tower kernel: xhci_hcd 0000:01:00.0: Abort failed to stop command ring: -110 Dec 26 09:53:24 Tower kernel: xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead Dec 26 09:53:24 Tower kernel: xhci_hcd 0000:01:00.0: HC died; cleaning up Dec 26 09:53:24 Tower kernel: xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command Dec 26 09:53:24 Tower kernel: usb 2-3: USB disconnect, device number 0 Dec 26 09:53:24 Tower kernel: usb 2-3: device not accepting address 2, error -22 Dec 26 09:53:24 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Dec 26 09:53:24 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 06 4d 2a 00 00 01 00 Dec 26 09:53:24 Tower kernel: print_req_error: I/O error, dev sda, sector 412970 Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410922) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410923) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410922) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410923) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410796) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410797) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410798) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410799) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410800) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Directory bread(block 410801) failed Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): error, corrupted directory (invalid entries) Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): Filesystem has been set read-only Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): FAT read failed (blocknr 110) Dec 26 09:53:24 Tower kernel: FAT-fs (sda1): FAT read failed (blocknr 110) Dec 26 09:53:25 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Plex Server.cfg Dec 26 09:53:25 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Torrent Server.cfg Dec 26 09:53:25 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Dec 26 09:53:25 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Dec 26 09:53:25 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Dec 26 09:53:25 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Dec 26 09:53:25 Tower emhttpd: Starting services... and then this gets repeated over and over Dec 26 09:53:25 Tower emhttpd: shcmd (8930): /etc/rc.d/rc.samba restart Dec 26 09:53:25 Tower root: cp: cannot create regular file '/boot/config/secrets.tdb': Read-only file system Dec 26 09:53:27 Tower root: Starting Samba: /usr/sbin/nmbd -D Dec 26 09:53:27 Tower root: /usr/sbin/smbd -D Dec 26 09:53:27 Tower root: /usr/sbin/winbindd -D Dec 26 09:53:28 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Plex Server.cfg Dec 26 09:53:28 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Torrent Server.cfg Dec 26 09:53:28 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Dec 26 09:53:28 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Dec 26 09:53:28 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Dec 26 09:53:28 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Dec 26 09:53:28 Tower emhttpd: Starting services... Quote Link to comment
Mizz141 Posted December 26, 2019 Author Share Posted December 26, 2019 Here is the full diagnostic tower-diagnostics-20191226-1909.zip Quote Link to comment
BRiT Posted December 26, 2019 Share Posted December 26, 2019 Your USB Flash drive is "bugging out". You need to fix that. Quote Link to comment
je82 Posted December 26, 2019 Share Posted December 26, 2019 Recommend trying usb2.0 if possible, usb suddenly going read only is usb 3.0 bug? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.