archedraft Posted February 5, 2016 Share Posted February 5, 2016 Just checked my log this morning and noticed this: Feb 5 08:28:44 unRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) I thought this was indicating my flash drive needed to be corrected but my flash drive is on sdc. I in fact do not have a sdb disk on unRAID at all. The error message keeps on coming up. Any ideas? Parity: sdf disk1: sdd disk2: sdk disk3: sdh cache: sdg flash: sdc UD1: sde -- UD = Unassigned Device UD2: sdi UD3: sdj Feb 5 01:43:21 UnRAID kernel: ------------[ cut here ]------------ Feb 5 01:43:21 UnRAID kernel: WARNING: CPU: 7 PID: 23434 at arch/x86/kernel/cpu/perf_event_intel_ds.c:315 reserve_ds_buffers+0x10e/0x347() Feb 5 01:43:21 UnRAID kernel: alloc_bts_buffer: BTS buffer allocation failure Feb 5 01:43:21 UnRAID kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_intel kvm vhost_net vhost macvtap macvlan tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod i2c_i801 ahci r8169 mii libahci acpi_cpufreq Feb 5 01:43:21 UnRAID kernel: CPU: 7 PID: 23434 Comm: qemu-system-x86 Not tainted 4.1.15-unRAID #1 Feb 5 01:43:21 UnRAID kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H77 Pro4-M, BIOS P2.00 08/06/2013 Feb 5 01:43:21 UnRAID kernel: 0000000000000009 ffff88028c1879a8 ffffffff815f1ad0 0000000000000000 Feb 5 01:43:21 UnRAID kernel: ffff88028c1879f8 ffff88028c1879e8 ffffffff8104775b ffff88044f315ec0 Feb 5 01:43:21 UnRAID kernel: ffffffff8101fd97 0000000000000000 0000000000000000 0000000000010e10 Feb 5 01:43:21 UnRAID kernel: Call Trace: Feb 5 01:43:21 UnRAID kernel: [<ffffffff815f1ad0>] dump_stack+0x4c/0x6e Feb 5 01:43:21 UnRAID kernel: [<ffffffff8104775b>] warn_slowpath_common+0x97/0xb1 Feb 5 01:43:21 UnRAID kernel: [<ffffffff8101fd97>] ? reserve_ds_buffers+0x10e/0x347 Feb 5 01:43:21 UnRAID kernel: [<ffffffff810477b6>] warn_slowpath_fmt+0x41/0x43 Feb 5 01:43:21 UnRAID kernel: [<ffffffff8101fd97>] reserve_ds_buffers+0x10e/0x347 Feb 5 01:43:21 UnRAID kernel: [<ffffffff8101ab58>] x86_reserve_hardware+0x141/0x153 Feb 5 01:43:21 UnRAID kernel: [<ffffffff8101abae>] x86_pmu_event_init+0x44/0x240 Feb 5 01:43:21 UnRAID kernel: [<ffffffff810a7b77>] perf_try_init_event+0x42/0x74 Feb 5 01:43:21 UnRAID kernel: [<ffffffff810ad260>] perf_init_event+0x9d/0xd4 Feb 5 01:43:21 UnRAID kernel: [<ffffffff810ad61c>] perf_event_alloc+0x385/0x4f7 Feb 5 01:43:21 UnRAID kernel: [<ffffffffa014555b>] ? stop_counter+0x2f/0x2f [kvm] Feb 5 01:43:21 UnRAID kernel: [<ffffffff810ad7bc>] perf_event_create_kernel_counter+0x2e/0x12c Feb 5 01:43:21 UnRAID kernel: [<ffffffffa0145676>] reprogram_counter+0xc0/0x109 [kvm] Feb 5 01:43:21 UnRAID kernel: [<ffffffffa0145741>] reprogram_fixed_counter+0x82/0x8d [kvm] Feb 5 01:43:21 UnRAID kernel: [<ffffffffa0145929>] reprogram_idx+0x4a/0x4f [kvm] Feb 5 01:43:21 UnRAID kernel: [<ffffffffa014618b>] kvm_handle_pmu_event+0x66/0x87 [kvm] Feb 5 01:43:21 UnRAID kernel: [<ffffffffa01722dc>] ? vmx_invpcid_supported+0x1b/0x1b [kvm_intel] Feb 5 01:43:21 UnRAID kernel: [<ffffffffa012f2dc>] kvm_arch_vcpu_ioctl_run+0x4f9/0xeb0 [kvm] Feb 5 01:43:21 UnRAID kernel: [<ffffffff810a90d3>] ? perf_event_update_userpage+0x109/0x11f Feb 5 01:43:21 UnRAID kernel: [<ffffffff810a90d3>] ? perf_event_update_userpage+0x109/0x11f Feb 5 01:43:21 UnRAID kernel: [<ffffffffa0174773>] ? __vmx_load_host_state.part.53+0x125/0x12c [kvm_intel] Feb 5 01:43:21 UnRAID kernel: [<ffffffffa012a65b>] ? kvm_arch_vcpu_load+0x139/0x143 [kvm] Feb 5 01:43:21 UnRAID kernel: [<ffffffffa0121ff1>] kvm_vcpu_ioctl+0x169/0x48f [kvm] Feb 5 01:43:21 UnRAID kernel: [<ffffffff810a5b3e>] ? perf_ctx_unlock+0x20/0x24 Feb 5 01:43:21 UnRAID kernel: [<ffffffff810ab462>] ? perf_event_context_sched_in+0x82/0x8b Feb 5 01:43:21 UnRAID kernel: [<ffffffff8110c316>] do_vfs_ioctl+0x367/0x421 Feb 5 01:43:21 UnRAID kernel: [<ffffffff81114033>] ? __fget+0x6c/0x78 Feb 5 01:43:21 UnRAID kernel: [<ffffffff8110c409>] SyS_ioctl+0x39/0x64 Feb 5 01:43:21 UnRAID kernel: [<ffffffff815f71ee>] system_call_fastpath+0x12/0x71 Feb 5 01:43:21 UnRAID kernel: ---[ end trace 47a538f245ba28f3 ]--- Feb 5 02:42:44 UnRAID kernel: mdcmd (21): spindown 0 Feb 5 03:02:35 UnRAID kernel: mdcmd (22): spindown 3 Feb 5 03:27:35 UnRAID kernel: mdcmd (23): spindown 2 Feb 5 04:08:38 UnRAID kernel: mdcmd (24): spindown 1 Feb 5 08:20:02 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:20:02 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:20:02 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:20:03 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:20:03 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:20:03 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:27:39 UnRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 5 08:28:05 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:28:05 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:28:05 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:28:44 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:28:44 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:28:44 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:29:04 UnRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 5 08:30:11 UnRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 5 08:32:50 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:32:50 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:32:50 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:33:02 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:33:02 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:33:02 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:33:12 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:33:12 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Feb 5 08:33:12 UnRAID kernel: FAT-fs (sdb1): FAT read failed (blocknr 598) Link to comment
trurl Posted February 5, 2016 Share Posted February 5, 2016 Post the results from lsblk Link to comment
itimpi Posted February 5, 2016 Share Posted February 5, 2016 Something must be taking up the sda and sdb device identification. Perhaps a built-in card reader? Link to comment
archedraft Posted February 5, 2016 Author Share Posted February 5, 2016 Post the results from lsblk md1 9:1 0 3.7T 0 md /mnt/disk1 md2 9:2 0 2.7T 0 md /mnt/disk2 md3 9:3 0 3.7T 0 md /mnt/disk3 sdc 8:32 1 7.5G 0 disk ??sdc1 8:33 1 7.5G 0 part /boot ??sdc2 8:34 1 31.5K 0 part sdd 8:48 0 3.7T 0 disk ??sdd1 8:49 0 3.7T 0 part sde 8:64 0 1.8T 0 disk ??sde1 8:65 0 1.8T 0 part /mnt/vmdisk-2 sdf 8:80 0 4.6T 0 disk ??sdf1 8:81 0 4.6T 0 part sdg 8:96 0 698.7G 0 disk ??sdg1 8:97 0 698.7G 0 part /mnt/cache sdh 8:112 0 3.7T 0 disk ??sdh1 8:113 0 3.7T 0 part sdi 8:128 0 232.9G 0 disk ??sdi1 8:129 0 232.9G 0 part /mnt/vmdisk sdj 8:144 0 931.5G 0 disk ??sdj1 8:145 0 931.5G 0 part /mnt/z_backup sdk 8:160 0 2.7T 0 disk ??sdk1 8:161 0 2.7T 0 part loop0 7:0 0 10G 0 loop loop1 7:1 0 3M 0 loop /etc/libvirt Link to comment
archedraft Posted February 5, 2016 Author Share Posted February 5, 2016 Something must be taking up the sda and sdb device identification. Perhaps a built-in card reader? Possibly, I passthrough a USB card reader to one of my VM's. Before it gets passed through "Unassigned Devices" shows it in its list but once my USB controller gets passed through, the card reader disappears. If it is the case, unRAID shouldn't be able to even that device anymore? Also I did restart my server but upon reboot the FAT read failed messages are still present at the end of the syslog. Link to comment
dlandon Posted February 5, 2016 Share Posted February 5, 2016 Do you have the unassigned devices plugin installed? Link to comment
archedraft Posted February 5, 2016 Author Share Posted February 5, 2016 Do you have the unassigned devices plugin installed? Yes, your version and the most upto date one as well. Link to comment
trurl Posted February 5, 2016 Share Posted February 5, 2016 Do you have the unassigned devices plugin installed? Yes, your version and the most upto date one as well. What does that mean? There should only be one installed. Link to comment
archedraft Posted February 5, 2016 Author Share Posted February 5, 2016 Do you have the unassigned devices plugin installed? Yes, your version and the most upto date one as well. What does that mean? There should only be one installed. Dlandon took over the development of the unassigned device plugin. What I was trying to say, I am using dlandon's unassigned devices plugin and I have made sure that it is up to date (version 2016.02.03). Link to comment
dlandon Posted February 5, 2016 Share Posted February 5, 2016 Do you have the unassigned devices plugin installed? Yes, your version and the most upto date one as well. Does this device show in unassigned devices? Does it show as mounted? I think it might be auto mounting in UD. If it does show there, set auto mount off. Link to comment
archedraft Posted February 5, 2016 Author Share Posted February 5, 2016 Something must be taking up the sda and sdb device identification. Perhaps a built-in card reader? Does this device show in unassigned devices? Does it show as mounted? I think it might be auto mounting in UD. If it does show there, set auto mount off. So I set my VM to not auto start and rebooted unRAID. The SD card reader does take up slots sda and sdb. The SD cards sdb was set to automount. I used UD to fix the bad bit and then turned auto mount off and rebooted. It didn't auto mount on startup and error message is gone. Good catch. Link to comment
dlandon Posted February 5, 2016 Share Posted February 5, 2016 Just a heads up about how UD handles devices. Any device that unraid is not using as the boot flash, parity, array disks, or cache is grabbed by UD when udev sees it and auto mounted. UD does not have any knowledge of devices passed to VMs. You solved it correctly. Don't let UD mount it and it will be available for VMs. UD will ignore it when auto mount is off and it will show as unassigned and not mounted. Link to comment
dlandon Posted February 6, 2016 Share Posted February 6, 2016 I've changed UD so a new device does not default to auto mounted and shared. I think this is how your issue got started. Now when a new device is installed, you have to manually set it to auto mount and share. Link to comment
archedraft Posted February 7, 2016 Author Share Posted February 7, 2016 I've changed UD so a new device does not default to auto mounted and shared. I think this is how your issue got started. Now when a new device is installed, you have to manually set it to auto mount and share. That makes sense. That way the user has a chance to set the mount point and various other things before it get auto mounted. Thanks for the update. Link to comment
dlandon Posted February 7, 2016 Share Posted February 7, 2016 I've changed UD so a new device does not default to auto mounted and shared. I think this is how your issue got started. Now when a new device is installed, you have to manually set it to auto mount and share. That makes sense. That way the user has a chance to set the mount point and various other things before it get auto mounted. Thanks for the update. UD started out life as "Auto Mount USB" and the idea was to insert a USB drive and it would mount and share without any user interaction. While it made sense then, the auto mount and share by default for a USB device appears to create more problems now than the feature is worth. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.