April 25, 201511 yr 1st of all I'm a total newbie with unRaid but I have this issue where my usb key is disconnecting after a while. I have a lexar usb3.0 key that I bought to install unraid on it. but after around 15 to 20 minutes the flash stops to be connected to the main board. When this happens in the flash setting I see the following error: Warning: file_get_contents(/boot/syslinux/syslinux.cfg) And the docker tab is not populated with the templates list. Is anybody have the same issues, is there a setting I can change to keep my usbkey connected ? I tried connecting the usb3.0 key on a usb2 port to see if it would resolve the issue but no luck so far. Thanks for your help
April 25, 201511 yr Not sure what the problem is, whether it is with the flash drive or the port, but what is really really odd is, why is anything trying to read syslinux.cfg well after the boot? It's only needed right at boot time, unless you manually view or edit it on the flash drive menu. Are you perhaps clicking on the flash drive on the Main screen, in order to test whether it is still connected? If so, then that specific warning is a red herring., when the flash drive has been dropped. BUT... I'm referring to the Main screen of v6, and this is the v5 support area. Can you confirm what version of unRAID you are using? Please provide a syslog - v5 - Capturing your syslog v6 - Need help? Read me first!
April 25, 201511 yr Author I'm using latest beta: 6.0-beta15. Yes i'm clicking un the flash drive from the Main screen, and this is the error I get. But what is the most weird part is the the docker menu is almost empty when this is happening, all my template list are gone. If I remove the key and plug-in back then run "mount -a" in the terminal everything is back to normal.
April 25, 201511 yr Author Here is the syslog from the las time it happenet Apr 24 23:57:50 Tower avahi-daemon[7826]: Withdrawing workstation service for vethef5eb36. Apr 24 23:57:50 Tower kernel: docker0: port 1(vethef5eb36) entered disabled state Apr 24 23:57:50 Tower kernel: device vethef5eb36 left promiscuous mode Apr 24 23:57:50 Tower kernel: docker0: port 1(vethef5eb36) entered disabled state Apr 25 00:01:13 Tower kernel: device veth38013a5 entered promiscuous mode Apr 25 00:01:13 Tower avahi-daemon[7826]: Withdrawing workstation service for veth8c65f3f. Apr 25 00:01:14 Tower kernel: eth0: renamed from veth8c65f3f Apr 25 00:01:14 Tower kernel: docker0: port 1(veth38013a5) entered forwarding state Apr 25 00:01:14 Tower kernel: docker0: port 1(veth38013a5) entered forwarding state Apr 25 00:01:29 Tower kernel: docker0: port 1(veth38013a5) entered forwarding state Apr 25 06:48:48 Tower kernel: usb 1-3: USB disconnect, device number 9 Apr 25 06:48:48 Tower kernel: sd 10:0:0:0: [sde] Synchronizing SCSI cache Apr 25 06:48:48 Tower kernel: sd 10:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30556) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30557) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30558) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30559) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30560) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30561) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30562) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30563) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30564) failed Apr 25 06:48:49 Tower kernel: FAT-fs (sde1): Directory bread(block 30565) failed Apr 25 06:48:49 Tower kernel: usb 1-3: new high-speed USB device number 10 using xhci_hcd Apr 25 06:48:50 Tower kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Apr 25 06:48:50 Tower kernel: scsi host11: usb-storage 1-3:1.0 Apr 25 06:48:51 Tower kernel: scsi 11:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 6 Apr 25 06:48:51 Tower kernel: sd 11:0:0:0: Attached scsi generic sg3 type 0 Apr 25 06:48:51 Tower kernel: sd 11:0:0:0: [sdc] 31285248 512-byte logical blocks: (16.0 GB/14.9 GiB) Apr 25 06:48:51 Tower kernel: sd 11:0:0:0: [sdc] Write Protect is off Apr 25 06:48:51 Tower kernel: sd 11:0:0:0: [sdc] Mode Sense: 43 00 00 00 Apr 25 06:48:51 Tower kernel: sd 11:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 25 06:48:51 Tower kernel: sdc: sdc1 Apr 25 06:48:51 Tower kernel: sd 11:0:0:0: [sdc] Attached SCSI removable disk Apr 25 06:48:51 Tower kernel: usb 2-1.3: USB disconnect, device number 4 Apr 25 06:49:03 Tower kernel: usb 1-3: USB disconnect, device number 10 Apr 25 06:49:03 Tower kernel: sd 11:0:0:0: [sdc] Synchronizing SCSI cache Apr 25 06:49:03 Tower kernel: sd 11:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Apr 25 06:51:44 Tower kernel: fat__get_entry: 6 callbacks suppressed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30556) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30557) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30558) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30559) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30560) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30561) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30562) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30563) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30564) failed Apr 25 06:51:44 Tower kernel: FAT-fs (sde1): Directory bread(block 30565) failed
April 25, 201511 yr Author Finally it was a faulty usb stick. I used another one and it's ok. By chance I did not registered it yet.
December 11, 201510 yr Sometimes my USB Flash drive also disconnects suddenly after a few months - the first sign is, that unMENU is somehow broken. I was able to mount the Flash drive again, without rebooting: sudo mount -t vfat /dev/sdf1 /boot sdf1 was in my case the flash drive, check it out first with "fdisk -l" !!!
Archived
This topic is now archived and is closed to further replies.