unRAID Server Release 6.2.0-beta21 Available

Lebowski · May 27, 2016

Reporting back,

Dual Parity working just fine,

VM's working fine

Dockers all ok

NVME cache pool all ok

No crashes, system seems very stable (Im not doing anything fancy with my VM's, it's just for RDP)

dalben · May 27, 2016

Nope, screw the bus, dust off the pitchforks lol

what about torches ?

spylex · May 27, 2016

I guess 'agile' is not part of limetechs mantra

bonienl · May 27, 2016

agile™ - now it is

Adam64 · May 27, 2016

New issue here: Last night I noticed that videos wouldn't play on any of my devices from my plex server docker. This morning checking the unRAID box showed me all the drives powered down and Plex still wouldn't play. Thinking I needed to reboot the box I tried to shut the dockers down -- all shut down except for the Crashplan docker. I tried to take the array offline through the gui and it accepted the command, but then became unresponsive. Got the diagnostics via the command line and attempted to restart it using the shutdown -r command, but nothing happened. Had to power off and power back on. Diags attached.

Edit: to clarify, shutdown -r said something like "RESTARTING NOW!", but then nothing happened.

unraid-diagnostics-20160527-0855.zip

methanoid · May 27, 2016

Think I had the same issue... but didnt log it... but Plex unresponsive and unRAID generally mega sluggish

Adam64 · May 28, 2016

New issue here: Last night I noticed that videos wouldn't play on any of my devices from my plex server docker. This morning checking the unRAID box showed me all the drives powered down and Plex still wouldn't play. Thinking I needed to reboot the box I tried to shut the dockers down -- all shut down except for the Crashplan docker. I tried to take the array offline through the gui and it accepted the command, but then became unresponsive. Got the diagnostics via the command line and attempted to restart it using the shutdown -r command, but nothing happened. Had to power off and power back on. Diags attached.

Edit: to clarify, shutdown -r said something like "RESTARTING NOW!", but then nothing happened.

It happened again not 24 hours later -- after it's been working for weeks. I guess the next thing I'll try is to reinstall the Plex docker as no one is reporting issues in the docker thread.

Bugman1400 · May 28, 2016

Instructions to roll back to 6.1.9?

I confirmed VMware passthrough doesn't work on 6.2 so need to revert back.

If you upgraded from 6.1.9 directly to 6.2beta21, then copy the files within the previous folder on the flash drive to the root of the flash and then reboot.

If you've gone through more than 1 version of the betas, then download 6.1.9 from LT's website, extract bzimage and bzroot from them and overwrite those two files on the flash drive and then reboot.

All this works if you've only got a single parity drive set up. Not sure what happens if you have 2 set up.

Is there a clever way of copying the files from the "previous" folder to the "root" folder? I am having no luck using Dolphin or Krusader.

Squid · May 28, 2016

Instructions to roll back to 6.1.9?

I confirmed VMware passthrough doesn't work on 6.2 so need to revert back.

If you upgraded from 6.1.9 directly to 6.2beta21, then copy the files within the previous folder on the flash drive to the root of the flash and then reboot.

If you've gone through more than 1 version of the betas, then download 6.1.9 from LT's website, extract bzimage and bzroot from them and overwrite those two files on the flash drive and then reboot.

All this works if you've only got a single parity drive set up. Not sure what happens if you have 2 set up.

Is there a clever way of copying the files from the "previous" folder to the "root" folder? I am having no luck using Dolphin or Krusader.

Did you try over the network? IE: through windows Works perfectly and takes 1 sec

Lebowski · May 28, 2016

This might be unrelated to beta, I just logged into unraid and all of a sudden most of my dockers had an update notification. I just went to the dockers tab and did another manual update check, they all went back to no updates (Green - Normal)

I did hard power my router just before all of this as I had to move it. I figure its related to that?

ryoko227 · May 28, 2016

Hey bigjme, I was wondering since I hadn't seen any update about this if downgrading the drivers had fixed your issues? I'm having literally the same error myself. I only just now found it though as I hadn't ever really stress tested my system till just the other day. I tried running 2 VMs (both in OVMF) with my 960s passthroughed to them. I wanted to see what she could do, so I opened up multiple games, movies and web videos, but instead found that I can reliably recreate the error you described in a similar manner. VM locks up but shows paused in unraid and cant be resumed just as you described. I'll check out using the 362 drivers, but thought I would ask you first since you initiated it.

Also, similar to your other post (and a few others here), I also have the "samba lockup issue" when I transfer a larger amount of files between the shares. Not knowing much of anything about how Samba works (only vaguely that it has to do with file sharing) I'll note that this only seems to happen with transfers from inside the windows VMs to the unraid shares (which I think is the function of samba if I'm not mistaken). However, if I SSH in and move stuff around the shares via mc, I've not had any issues.

EDIT-- I found your post on the nvidia forum, and the issue that they are having is being reported as still causing problems with the newest driver set 365.19. Installing 362 now and see how she fares after that.

The downgrade did indeed resolve my issue, I haven't shut down my system in a while to test the samba lockup issue but I can safely say my vms haven't had any lockups in rather a while

I haven't updated to anything newer since - I must say that I haven't really stressed the system since other then 1 of the vms playing minecraft

I am due to start playing the new doom game which should give it a decent test soon

Awesome, thank you for the update bigjme. I'd like to tack on that using the 362 drivers seems to have resolved the issue for me as well. I did my version of a "practical" stress test early today and ran up both VMs, running 3 games each (mixtures of -War Thunder, Black Desert, Heroes and Generals, Lords of Vermilion, Wizardry Online, etc.), while playing 3 random movies in 3 separate players, along with 1/2 a dozen or so Youtube videos running at the same time on both. No crash, no pause, just worked. Thank you for finding that fix and sharing it here bigjme!

ryoko227 · May 28, 2016

Also, similar to your other post (and a few others here), I also have the "samba lockup issue" when I transfer a larger amount of files between the shares. Not knowing much of anything about how Samba works (only vaguely that it has to do with file sharing) I'll note that this only seems to happen with transfers from inside the windows VMs to the unraid shares (which I think is the function of samba if I'm not mistaken). However, if I SSH in and move stuff around the shares via mc, I've not had any issues.

Have you tried the num_stripes fix (setting num_stripes to 8192)?

Took a little searching, but I found some of your posts that lead me to the http://lime-technology.com/wiki/index.php/Tips_and_Tweaks page. I changed the settings as directed. I'm kind of in the process of a game library migration, so I should have some juicy large files to test this out with over the next few days. I'll toss up an update if I encounter the issue again. Thanks RobJ!

luca · May 29, 2016

On beta 21, I'm also experiencing problem with copying large files to the server. I do have a VM running, but the file transfers are usually from a secondary unraid server to my main unraid server, so nothing is copied to/from the VM.

The copies start fine (70-80 Mbps), but within a few seconds they slow down to a crawl, and eventually stop altogether. At the same time unraid web gui becomes unresponsive. In the last few times this happened, I was able to stop the array, but not to restart the server (had to manually hit the reset button).

Changing the num_stripes setting didn't seem to make any difference, the first large file copy hung the server again, however I was able to stop the array and restart the server as well from the gui, so maybe an improvement? I've never been able to see anything in the log suggesting a problem. After restarting, the server seems fine for a few days.

fs1-syslog-20160529-1047.zip

bigjme · May 29, 2016

On beta 21, I'm also experiencing problem with copying large files to the server. I do have a VM running, but the file transfers are usually from a secondary unraid server to my main unraid server, so nothing is copied to/from the VM.

The copies start fine (70-80 Mbps), but within a few seconds they slow down to a crawl, and eventually stop altogether. At the same time unraid web gui becomes unresponsive. In the last few times this happened, I was able to stop the array, but not to restart the server (had to manually hit the reset button).

Changing the num_stripes setting didn't seem to make any difference, the first large file copy hung the server again, however I was able to stop the array and restart the server as well from the gui, so maybe an improvement? I've never been able to see anything in the log suggesting a problem. After restarting, the server seems fine for a few days.

Can you install the stats plugin and run it on another screen to check how much memory is being used? Keep it on real time

I have had this issue on my system where my VMs are by the looks of it leaking memory and using a lot more than they should - when i then do a transfer the remaining memory is used up to increase transfer times and doing anything with the array on my VMs during this time will crash samba and can often cause the GUI to lockup

I have mentioned it a few times but for now to get round this i had to decrease my vm memory but the issue is coming back as the longer i leave the system on the more memory my vms use

luca · May 30, 2016

On beta 21, I'm also experiencing problem with copying large files to the server. I do have a VM running, but the file transfers are usually from a secondary unraid server to my main unraid server, so nothing is copied to/from the VM.

The copies start fine (70-80 Mbps), but within a few seconds they slow down to a crawl, and eventually stop altogether. At the same time unraid web gui becomes unresponsive. In the last few times this happened, I was able to stop the array, but not to restart the server (had to manually hit the reset button).

Changing the num_stripes setting didn't seem to make any difference, the first large file copy hung the server again, however I was able to stop the array and restart the server as well from the gui, so maybe an improvement? I've never been able to see anything in the log suggesting a problem. After restarting, the server seems fine for a few days.

Can you install the stats plugin and run it on another screen to check how much memory is being used? Keep it on real time

I have had this issue on my system where my VMs are by the looks of it leaking memory and using a lot more than they should - when i then do a transfer the remaining memory is used up to increase transfer times and doing anything with the array on my VMs during this time will crash samba and can often cause the GUI to lockup

I have mentioned it a few times but for now to get round this i had to decrease my vm memory but the issue is coming back as the longer i leave the system on the more memory my vms use

I've installed stats plugin and run a test copy: ~16GB file from my windows 10 PC to the main unraid server. The copy starts fast as usual, and I can see almost all RAM getting used up as "cache" (see pic), BTW, is that normal? When the ram is used up, speed slows down gradually.

At around 17:22 I turn off the one VM I have running (it's now set to only use 2GB of ram), and I can see the copy speed up again (bump at 17:23), until the cache is full again. After 17:36 speed recovers around 20 MBps, and is stable until the end of the copy.

http://i.imgur.com/5m66g5K.png

Lebowski · May 30, 2016

Im doing a data re-build on 2 disks. I upgraded 2 of my 2TB disks to 4TB disks. So far so good doing a dual re-build. (I have back ups and the original drives still so I figured to give it a go)

Looking in the shares folder, I have some inconsistency on whats protected (Green Triangle). The share comment where it's cache only is just that cache only.

Appdata and Downloads (Cache only) are correct. But Upload, domains and system show the orange triangle. I dont think that's correct, no data / files / folders are on the array for those shares. They should be Green protect by cache pool?

unless this has something to do with the Enable copy on write setting? (Mine are all Auto) or another setting? but I cant seem to find it when I compare settings of Downloads to Upload.

Or is the cache drives part of the rebuild, not sure if what I see is correct or a bug.

nexusmaniac · May 30, 2016

Not sure what's going on - the web ui seems quite wonky

Normally set to the black theme - but now it's white, the dashboard is blank, the Docker tab is broken and everything else seems off

Syslog is filled up with /dev/sda errors

May 30 13:47:11 Raptor kernel: usb 4-1: USB disconnect, device number 2
May 30 13:47:11 Raptor kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
May 30 13:47:11 Raptor kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
May 30 13:47:11 Raptor kernel: scsi host7: usb-storage 4-1:1.0
May 30 13:47:12 Raptor kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: Attached scsi generic sg0 type 0
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] 30031250 512-byte logical blocks: (15.4 GB/14.3 GiB)
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write Protect is off
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Mode Sense: 43 00 00 00
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 30 13:47:12 Raptor kernel: sdh: sdh1
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Attached SCSI removable disk
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: fat__get_entry: 6 callbacks suppressed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): FAT read failed (blocknr 3480)
May 30 14:21:01 Raptor kernel: ------------[ cut here ]------------
May 30 14:21:01 Raptor kernel: WARNING: CPU: 0 PID: 28498 at fs/fs-writeback.c:2100 __mark_inode_dirty+0x1d2/0x1e3()
May 30 14:21:01 Raptor kernel: bdi-block not registered
May 30 14:21:01 Raptor kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb ahci i2c_i801 libahci fbdev x86_pkg_temp_thermal coretemp kvm_intel igb kvm ptp pps_core i2c_algo_bit ipmi_si acpi_cpufreq
May 30 14:21:01 Raptor kernel: CPU: 0 PID: 28498 Comm: php Not tainted 4.4.6-unRAID #1
May 30 14:21:01 Raptor kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./E3C226D2I, BIOS P3.30 06/04/2015
May 30 14:21:01 Raptor kernel: 0000000000000000 ffff8801024f7ba0 ffffffff813688da ffff8801024f7be8
May 30 14:21:01 Raptor kernel: 0000000000000834 ffff8801024f7bd8 ffffffff8104a28a ffffffff8112940d
May 30 14:21:01 Raptor kernel: ffff88040a190340 ffff88040997bb80 0000000000000000 ffff88040a1903c0
May 30 14:21:01 Raptor kernel: Call Trace:
May 30 14:21:01 Raptor kernel: [<ffffffff813688da>] dump_stack+0x61/0x7e
May 30 14:21:01 Raptor kernel: [<ffffffff8104a28a>] warn_slowpath_common+0x8f/0xa8
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] ? __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff8104a2e6>] warn_slowpath_fmt+0x43/0x4b
May 30 14:21:01 Raptor kernel: [<ffffffff81127cc2>] ? locked_inode_to_wb_and_lock_list+0x64/0xf7
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff811c36de>] mark_fsinfo_dirty+0x28/0x2a
May 30 14:21:01 Raptor kernel: [<ffffffff811c4212>] fat_alloc_clusters+0x327/0x40e
May 30 14:21:01 Raptor kernel: [<ffffffff81110e7f>] ? terminate_walk+0x21/0x82
May 30 14:21:01 Raptor kernel: [<ffffffff81086f16>] ? rcu_is_watching+0x10/0x22
May 30 14:21:01 Raptor kernel: [<ffffffff81119798>] ? __d_instantiate+0x84/0xda
May 30 14:21:01 Raptor kernel: [<ffffffff811c2d6c>] fat_alloc_new_dir+0x30/0x1ca
May 30 14:21:01 Raptor kernel: [<ffffffff811c83ca>] ? vfat_lookup+0xdb/0x145
May 30 14:21:01 Raptor kernel: [<ffffffff811c946b>] vfat_mkdir+0x4d/0x140
May 30 14:21:01 Raptor kernel: [<ffffffff81111690>] vfs_mkdir+0x7e/0xae
May 30 14:21:01 Raptor kernel: [<ffffffff81115a6f>] SyS_mkdirat+0x75/0xac
May 30 14:21:01 Raptor kernel: [<ffffffff81115aba>] SyS_mkdir+0x14/0x16
May 30 14:21:01 Raptor kernel: [<ffffffff8161a0ae>] entry_SYSCALL_64_fastpath+0x12/0x6d
May 30 14:21:01 Raptor kernel: ---[ end trace fd44b47a9ddf242e ]---

edit: going to \\Raptor\flash results in a blank directory

Frank1940 · May 30, 2016

Not sure what's going on - the web ui seems quite wonky

Normally set to the black theme - but now it's white, the dashboard is blank, the Docker tab is broken and everything else seems off

Syslog is filled up with /dev/sda errors

May 30 13:47:11 Raptor kernel: usb 4-1: USB disconnect, device number 2
May 30 13:47:11 Raptor kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
May 30 13:47:11 Raptor kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
May 30 13:47:11 Raptor kernel: scsi host7: usb-storage 4-1:1.0
May 30 13:47:12 Raptor kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: Attached scsi generic sg0 type 0
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] 30031250 512-byte logical blocks: (15.4 GB/14.3 GiB)
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write Protect is off
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Mode Sense: 43 00 00 00
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 30 13:47:12 Raptor kernel: sdh: sdh1
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Attached SCSI removable disk
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: fat__get_entry: 6 callbacks suppressed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): FAT read failed (blocknr 3480)
May 30 14:21:01 Raptor kernel: ------------[ cut here ]------------
May 30 14:21:01 Raptor kernel: WARNING: CPU: 0 PID: 28498 at fs/fs-writeback.c:2100 __mark_inode_dirty+0x1d2/0x1e3()
May 30 14:21:01 Raptor kernel: bdi-block not registered
May 30 14:21:01 Raptor kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb ahci i2c_i801 libahci fbdev x86_pkg_temp_thermal coretemp kvm_intel igb kvm ptp pps_core i2c_algo_bit ipmi_si acpi_cpufreq
May 30 14:21:01 Raptor kernel: CPU: 0 PID: 28498 Comm: php Not tainted 4.4.6-unRAID #1
May 30 14:21:01 Raptor kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./E3C226D2I, BIOS P3.30 06/04/2015
May 30 14:21:01 Raptor kernel: 0000000000000000 ffff8801024f7ba0 ffffffff813688da ffff8801024f7be8
May 30 14:21:01 Raptor kernel: 0000000000000834 ffff8801024f7bd8 ffffffff8104a28a ffffffff8112940d
May 30 14:21:01 Raptor kernel: ffff88040a190340 ffff88040997bb80 0000000000000000 ffff88040a1903c0
May 30 14:21:01 Raptor kernel: Call Trace:
May 30 14:21:01 Raptor kernel: [<ffffffff813688da>] dump_stack+0x61/0x7e
May 30 14:21:01 Raptor kernel: [<ffffffff8104a28a>] warn_slowpath_common+0x8f/0xa8
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] ? __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff8104a2e6>] warn_slowpath_fmt+0x43/0x4b
May 30 14:21:01 Raptor kernel: [<ffffffff81127cc2>] ? locked_inode_to_wb_and_lock_list+0x64/0xf7
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff811c36de>] mark_fsinfo_dirty+0x28/0x2a
May 30 14:21:01 Raptor kernel: [<ffffffff811c4212>] fat_alloc_clusters+0x327/0x40e
May 30 14:21:01 Raptor kernel: [<ffffffff81110e7f>] ? terminate_walk+0x21/0x82
May 30 14:21:01 Raptor kernel: [<ffffffff81086f16>] ? rcu_is_watching+0x10/0x22
May 30 14:21:01 Raptor kernel: [<ffffffff81119798>] ? __d_instantiate+0x84/0xda
May 30 14:21:01 Raptor kernel: [<ffffffff811c2d6c>] fat_alloc_new_dir+0x30/0x1ca
May 30 14:21:01 Raptor kernel: [<ffffffff811c83ca>] ? vfat_lookup+0xdb/0x145
May 30 14:21:01 Raptor kernel: [<ffffffff811c946b>] vfat_mkdir+0x4d/0x140
May 30 14:21:01 Raptor kernel: [<ffffffff81111690>] vfs_mkdir+0x7e/0xae
May 30 14:21:01 Raptor kernel: [<ffffffff81115a6f>] SyS_mkdirat+0x75/0xac
May 30 14:21:01 Raptor kernel: [<ffffffff81115aba>] SyS_mkdir+0x14/0x16
May 30 14:21:01 Raptor kernel: [<ffffffff8161a0ae>] entry_SYSCALL_64_fastpath+0x12/0x6d
May 30 14:21:01 Raptor kernel: ---[ end trace fd44b47a9ddf242e ]---

sda is generally your Flash Drive. I would suspect some sort of corruption on that device. Suggest you run chkdsk (or the Apple equivalent) on it.

nexusmaniac · May 30, 2016

Not sure what's going on - the web ui seems quite wonky

Normally set to the black theme - but now it's white, the dashboard is blank, the Docker tab is broken and everything else seems off

Syslog is filled up with /dev/sda errors

May 30 13:47:11 Raptor kernel: usb 4-1: USB disconnect, device number 2
May 30 13:47:11 Raptor kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
May 30 13:47:11 Raptor kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
May 30 13:47:11 Raptor kernel: scsi host7: usb-storage 4-1:1.0
May 30 13:47:12 Raptor kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: Attached scsi generic sg0 type 0
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] 30031250 512-byte logical blocks: (15.4 GB/14.3 GiB)
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write Protect is off
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Mode Sense: 43 00 00 00
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 30 13:47:12 Raptor kernel: sdh: sdh1
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Attached SCSI removable disk
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: fat__get_entry: 6 callbacks suppressed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): FAT read failed (blocknr 3480)
May 30 14:21:01 Raptor kernel: ------------[ cut here ]------------
May 30 14:21:01 Raptor kernel: WARNING: CPU: 0 PID: 28498 at fs/fs-writeback.c:2100 __mark_inode_dirty+0x1d2/0x1e3()
May 30 14:21:01 Raptor kernel: bdi-block not registered
May 30 14:21:01 Raptor kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb ahci i2c_i801 libahci fbdev x86_pkg_temp_thermal coretemp kvm_intel igb kvm ptp pps_core i2c_algo_bit ipmi_si acpi_cpufreq
May 30 14:21:01 Raptor kernel: CPU: 0 PID: 28498 Comm: php Not tainted 4.4.6-unRAID #1
May 30 14:21:01 Raptor kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./E3C226D2I, BIOS P3.30 06/04/2015
May 30 14:21:01 Raptor kernel: 0000000000000000 ffff8801024f7ba0 ffffffff813688da ffff8801024f7be8
May 30 14:21:01 Raptor kernel: 0000000000000834 ffff8801024f7bd8 ffffffff8104a28a ffffffff8112940d
May 30 14:21:01 Raptor kernel: ffff88040a190340 ffff88040997bb80 0000000000000000 ffff88040a1903c0
May 30 14:21:01 Raptor kernel: Call Trace:
May 30 14:21:01 Raptor kernel: [<ffffffff813688da>] dump_stack+0x61/0x7e
May 30 14:21:01 Raptor kernel: [<ffffffff8104a28a>] warn_slowpath_common+0x8f/0xa8
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] ? __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff8104a2e6>] warn_slowpath_fmt+0x43/0x4b
May 30 14:21:01 Raptor kernel: [<ffffffff81127cc2>] ? locked_inode_to_wb_and_lock_list+0x64/0xf7
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff811c36de>] mark_fsinfo_dirty+0x28/0x2a
May 30 14:21:01 Raptor kernel: [<ffffffff811c4212>] fat_alloc_clusters+0x327/0x40e
May 30 14:21:01 Raptor kernel: [<ffffffff81110e7f>] ? terminate_walk+0x21/0x82
May 30 14:21:01 Raptor kernel: [<ffffffff81086f16>] ? rcu_is_watching+0x10/0x22
May 30 14:21:01 Raptor kernel: [<ffffffff81119798>] ? __d_instantiate+0x84/0xda
May 30 14:21:01 Raptor kernel: [<ffffffff811c2d6c>] fat_alloc_new_dir+0x30/0x1ca
May 30 14:21:01 Raptor kernel: [<ffffffff811c83ca>] ? vfat_lookup+0xdb/0x145
May 30 14:21:01 Raptor kernel: [<ffffffff811c946b>] vfat_mkdir+0x4d/0x140
May 30 14:21:01 Raptor kernel: [<ffffffff81111690>] vfs_mkdir+0x7e/0xae
May 30 14:21:01 Raptor kernel: [<ffffffff81115a6f>] SyS_mkdirat+0x75/0xac
May 30 14:21:01 Raptor kernel: [<ffffffff81115aba>] SyS_mkdir+0x14/0x16
May 30 14:21:01 Raptor kernel: [<ffffffff8161a0ae>] entry_SYSCALL_64_fastpath+0x12/0x6d
May 30 14:21:01 Raptor kernel: ---[ end trace fd44b47a9ddf242e ]---

sda is generally your Flash Drive. I would suspect some sort of corruption on that device. Suggest you run chkdsk (or the Apple equivalent) on it.

It is.

I've just run chkdsk on my Windows PC - No errors / issues reported

Frank1940 · May 30, 2016

Not sure what's going on - the web ui seems quite wonky

Normally set to the black theme - but now it's white, the dashboard is blank, the Docker tab is broken and everything else seems off

Syslog is filled up with /dev/sda errors

May 30 13:47:11 Raptor kernel: usb 4-1: USB disconnect, device number 2
May 30 13:47:11 Raptor kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
May 30 13:47:11 Raptor kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
May 30 13:47:11 Raptor kernel: scsi host7: usb-storage 4-1:1.0
May 30 13:47:12 Raptor kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: Attached scsi generic sg0 type 0
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] 30031250 512-byte logical blocks: (15.4 GB/14.3 GiB)
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write Protect is off
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Mode Sense: 43 00 00 00
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 30 13:47:12 Raptor kernel: sdh: sdh1
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Attached SCSI removable disk
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: fat__get_entry: 6 callbacks suppressed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): FAT read failed (blocknr 3480)
May 30 14:21:01 Raptor kernel: ------------[ cut here ]------------
May 30 14:21:01 Raptor kernel: WARNING: CPU: 0 PID: 28498 at fs/fs-writeback.c:2100 __mark_inode_dirty+0x1d2/0x1e3()
May 30 14:21:01 Raptor kernel: bdi-block not registered
May 30 14:21:01 Raptor kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb ahci i2c_i801 libahci fbdev x86_pkg_temp_thermal coretemp kvm_intel igb kvm ptp pps_core i2c_algo_bit ipmi_si acpi_cpufreq
May 30 14:21:01 Raptor kernel: CPU: 0 PID: 28498 Comm: php Not tainted 4.4.6-unRAID #1
May 30 14:21:01 Raptor kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./E3C226D2I, BIOS P3.30 06/04/2015
May 30 14:21:01 Raptor kernel: 0000000000000000 ffff8801024f7ba0 ffffffff813688da ffff8801024f7be8
May 30 14:21:01 Raptor kernel: 0000000000000834 ffff8801024f7bd8 ffffffff8104a28a ffffffff8112940d
May 30 14:21:01 Raptor kernel: ffff88040a190340 ffff88040997bb80 0000000000000000 ffff88040a1903c0
May 30 14:21:01 Raptor kernel: Call Trace:
May 30 14:21:01 Raptor kernel: [<ffffffff813688da>] dump_stack+0x61/0x7e
May 30 14:21:01 Raptor kernel: [<ffffffff8104a28a>] warn_slowpath_common+0x8f/0xa8
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] ? __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff8104a2e6>] warn_slowpath_fmt+0x43/0x4b
May 30 14:21:01 Raptor kernel: [<ffffffff81127cc2>] ? locked_inode_to_wb_and_lock_list+0x64/0xf7
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff811c36de>] mark_fsinfo_dirty+0x28/0x2a
May 30 14:21:01 Raptor kernel: [<ffffffff811c4212>] fat_alloc_clusters+0x327/0x40e
May 30 14:21:01 Raptor kernel: [<ffffffff81110e7f>] ? terminate_walk+0x21/0x82
May 30 14:21:01 Raptor kernel: [<ffffffff81086f16>] ? rcu_is_watching+0x10/0x22
May 30 14:21:01 Raptor kernel: [<ffffffff81119798>] ? __d_instantiate+0x84/0xda
May 30 14:21:01 Raptor kernel: [<ffffffff811c2d6c>] fat_alloc_new_dir+0x30/0x1ca
May 30 14:21:01 Raptor kernel: [<ffffffff811c83ca>] ? vfat_lookup+0xdb/0x145
May 30 14:21:01 Raptor kernel: [<ffffffff811c946b>] vfat_mkdir+0x4d/0x140
May 30 14:21:01 Raptor kernel: [<ffffffff81111690>] vfs_mkdir+0x7e/0xae
May 30 14:21:01 Raptor kernel: [<ffffffff81115a6f>] SyS_mkdirat+0x75/0xac
May 30 14:21:01 Raptor kernel: [<ffffffff81115aba>] SyS_mkdir+0x14/0x16
May 30 14:21:01 Raptor kernel: [<ffffffff8161a0ae>] entry_SYSCALL_64_fastpath+0x12/0x6d
May 30 14:21:01 Raptor kernel: ---[ end trace fd44b47a9ddf242e ]---

sda is generally your Flash Drive. I would suspect some sort of corruption on that device. Suggest you run chkdsk (or the Apple equivalent) on it.

It is.

I've just run chkdsk on my Windows PC - No errors / issues reported

Post complete diagnostics file. ('Tools' >>>> 'Diagnostics')

Squid · May 30, 2016

Not sure what's going on - the web ui seems quite wonky

Normally set to the black theme - but now it's white, the dashboard is blank, the Docker tab is broken and everything else seems off

Syslog is filled up with /dev/sda errors

May 30 13:47:11 Raptor kernel: usb 4-1: USB disconnect, device number 2
May 30 13:47:11 Raptor kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
May 30 13:47:11 Raptor kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
May 30 13:47:11 Raptor kernel: scsi host7: usb-storage 4-1:1.0
May 30 13:47:12 Raptor kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: Attached scsi generic sg0 type 0
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] 30031250 512-byte logical blocks: (15.4 GB/14.3 GiB)
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write Protect is off
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Mode Sense: 43 00 00 00
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 30 13:47:12 Raptor kernel: sdh: sdh1
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Attached SCSI removable disk
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: fat__get_entry: 6 callbacks suppressed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): FAT read failed (blocknr 3480)
May 30 14:21:01 Raptor kernel: ------------[ cut here ]------------
May 30 14:21:01 Raptor kernel: WARNING: CPU: 0 PID: 28498 at fs/fs-writeback.c:2100 __mark_inode_dirty+0x1d2/0x1e3()
May 30 14:21:01 Raptor kernel: bdi-block not registered
May 30 14:21:01 Raptor kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb ahci i2c_i801 libahci fbdev x86_pkg_temp_thermal coretemp kvm_intel igb kvm ptp pps_core i2c_algo_bit ipmi_si acpi_cpufreq
May 30 14:21:01 Raptor kernel: CPU: 0 PID: 28498 Comm: php Not tainted 4.4.6-unRAID #1
May 30 14:21:01 Raptor kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./E3C226D2I, BIOS P3.30 06/04/2015
May 30 14:21:01 Raptor kernel: 0000000000000000 ffff8801024f7ba0 ffffffff813688da ffff8801024f7be8
May 30 14:21:01 Raptor kernel: 0000000000000834 ffff8801024f7bd8 ffffffff8104a28a ffffffff8112940d
May 30 14:21:01 Raptor kernel: ffff88040a190340 ffff88040997bb80 0000000000000000 ffff88040a1903c0
May 30 14:21:01 Raptor kernel: Call Trace:
May 30 14:21:01 Raptor kernel: [<ffffffff813688da>] dump_stack+0x61/0x7e
May 30 14:21:01 Raptor kernel: [<ffffffff8104a28a>] warn_slowpath_common+0x8f/0xa8
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] ? __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff8104a2e6>] warn_slowpath_fmt+0x43/0x4b
May 30 14:21:01 Raptor kernel: [<ffffffff81127cc2>] ? locked_inode_to_wb_and_lock_list+0x64/0xf7
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff811c36de>] mark_fsinfo_dirty+0x28/0x2a
May 30 14:21:01 Raptor kernel: [<ffffffff811c4212>] fat_alloc_clusters+0x327/0x40e
May 30 14:21:01 Raptor kernel: [<ffffffff81110e7f>] ? terminate_walk+0x21/0x82
May 30 14:21:01 Raptor kernel: [<ffffffff81086f16>] ? rcu_is_watching+0x10/0x22
May 30 14:21:01 Raptor kernel: [<ffffffff81119798>] ? __d_instantiate+0x84/0xda
May 30 14:21:01 Raptor kernel: [<ffffffff811c2d6c>] fat_alloc_new_dir+0x30/0x1ca
May 30 14:21:01 Raptor kernel: [<ffffffff811c83ca>] ? vfat_lookup+0xdb/0x145
May 30 14:21:01 Raptor kernel: [<ffffffff811c946b>] vfat_mkdir+0x4d/0x140
May 30 14:21:01 Raptor kernel: [<ffffffff81111690>] vfs_mkdir+0x7e/0xae
May 30 14:21:01 Raptor kernel: [<ffffffff81115a6f>] SyS_mkdirat+0x75/0xac
May 30 14:21:01 Raptor kernel: [<ffffffff81115aba>] SyS_mkdir+0x14/0x16
May 30 14:21:01 Raptor kernel: [<ffffffff8161a0ae>] entry_SYSCALL_64_fastpath+0x12/0x6d
May 30 14:21:01 Raptor kernel: ---[ end trace fd44b47a9ddf242e ]---

sda is generally your Flash Drive. I would suspect some sort of corruption on that device. Suggest you run chkdsk (or the Apple equivalent) on it.

It is.

I've just run chkdsk on my Windows PC - No errors / issues reported

Post complete diagnostics file. ('Tools' >>>> 'Diagnostics')

Ross it in a different port and speed (2.0 vs 3.0) if you can

Bread errors tend to happen when the port loses track of the stick and then remounts it

Sent from my LG-D852 using Tapatalk

bubbaQ · May 30, 2016

Had a nasty hang with 6.2B21.... I could not get a diagnostic dump, but I was able to pull off the log file (sdc is cache drive):

May 28 04:40:01 Tower9 root: Community Applications Auto Update Running
May 28 04:48:26 Tower9 kernel: sd 1:0:1:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

May 28 04:48:26 Tower9 kernel: sd 1:0:1:0: [sdc] tag#0 Sense Key : 0x4 [current]

May 28 04:48:26 Tower9 kernel: sd 1:0:1:0: [sdc] tag#0 ASC=0x44 ASCQ=0x0

May 28 04:48:26 Tower9 kernel: sd 1:0:1:0: [sdc] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 09 60 f1 f0 00 00 01 e8 00 00

May 28 04:48:26 Tower9 kernel: blk_update_request: critical target error, dev sdc, sector 157348336

May 28 04:48:26 Tower9 kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0

May 28 05:00:19 Tower9 kernel: sd 1:0:1:0: [sdc] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

May 28 05:00:19 Tower9 kernel: sd 1:0:1:0: [sdc] tag#1 Sense Key : 0x4 [current]

May 28 05:00:19 Tower9 kernel: sd 1:0:1:0: [sdc] tag#1 ASC=0x44 ASCQ=0x0

May 28 05:00:19 Tower9 kernel: sd 1:0:1:0: [sdc] tag#1 CDB: opcode=0x88 88 00 00 00 00 00 09 72 fc d0 00 00 00 08 00 00

May 28 05:00:19 Tower9 kernel: blk_update_request: critical target error, dev sdc, sector 158530768

May 28 05:00:19 Tower9 kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0

May 28 05:00:19 Tower9 kernel: sd 1:0:1:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

May 28 05:00:19 Tower9 kernel: sd 1:0:1:0: [sdc] tag#0 Sense Key : 0x4 [current]

May 28 05:00:19 Tower9 kernel: sd 1:0:1:0: [sdc] tag#0 ASC=0x44 ASCQ=0x0

May 28 05:00:19 Tower9 kernel: sd 1:0:1:0: [sdc] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 09 72 fc d8 00 00 00 80 00 00

May 28 05:00:19 Tower9 kernel: blk_update_request: critical target error, dev sdc, sector 158530776

May 28 05:00:19 Tower9 kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 3, flush 0, corrupt 0, gen 0

May 28 05:20:50 Tower9 kernel: aacraid: Host adapter abort request (1,0,2,0)

May 28 05:20:50 Tower9 kernel: aacraid: Host adapter abort request (1,0,0,0)

May 28 05:20:50 Tower9 kernel: aacraid: Host adapter abort request (1,0,4,0)

May 28 05:20:50 Tower9 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

May 28 05:20:50 Tower9 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

May 28 05:20:50 Tower9 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

May 28 05:20:50 Tower9 kernel: aacraid: Host adapter abort request (1,0,3,0)

May 28 05:20:50 Tower9 kernel: aacraid: Host adapter abort request (1,0,5,0)

May 28 05:20:50 Tower9 kernel: aacraid: Host adapter abort request (1,0,1,0)

May 28 05:20:50 Tower9 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

May 28 05:20:50 Tower9 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

May 28 05:20:50 Tower9 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

May 28 05:21:17 Tower9 kernel: aacraid: Host adapter abort request (1,0,5,0)

May 28 05:21:51 Tower9 kernel: aacraid: Host adapter abort request (1,0,1,0)

May 28 05:21:51 Tower9 kernel: aacraid: Host adapter reset request. SCSI hang ?

May 28 05:22:51 Tower9 kernel: aacraid: SCSI bus appears hung

May 28 05:23:59 Tower9 kernel: scsi_eh_1: page allocation failure: order:10, mode:0x2080020

May 28 05:23:59 Tower9 kernel: CPU: 0 PID: 1947 Comm: scsi_eh_1 Tainted: G O 4.4.6-unRAID #1

May 28 05:23:59 Tower9 kernel: Hardware name: Supermicro Super Server/X10SRi-F, BIOS 1.0c 09/09/2015

May 28 05:23:59 Tower9 kernel: 0000000000000000 ffff880857d53990 ffffffff813688da 0000000000000000

May 28 05:23:59 Tower9 kernel: 000000000000000a ffff880857d53a28 ffffffff810bc9b0 ffff88087fffdb50

May 28 05:23:59 Tower9 kernel: ffff88087fffbb00 fffffffffffffc00 000000000000000a 000000000000000a

May 28 05:23:59 Tower9 kernel: Call Trace:

May 28 05:23:59 Tower9 kernel: [<ffffffff813688da>] dump_stack+0x61/0x7e

May 28 05:23:59 Tower9 kernel: [<ffffffff810bc9b0>] warn_alloc_failed+0x10f/0x127

May 28 05:23:59 Tower9 kernel: [<ffffffff810bf9c7>] __alloc_pages_nodemask+0x870/0x8ca

May 28 05:23:59 Tower9 kernel: [<ffffffff810f7aee>] ? kfree+0xd0/0xeb

May 28 05:23:59 Tower9 kernel: [<ffffffff810ee9b2>] alloc_pages_current+0xbe/0xe8

May 28 05:23:59 Tower9 kernel: [<ffffffff8143770a>] intel_alloc_coherent+0x8d/0xf9

May 28 05:23:59 Tower9 kernel: [<ffffffffa05c69f0>] aac_fib_setup+0xaf/0x1ff [aacraid]

May 28 05:23:59 Tower9 kernel: [<ffffffffa05c5ff7>] aac_init_adapter+0x855/0x899 [aacraid]

May 28 05:23:59 Tower9 kernel: [<ffffffffa05cb626>] aac_srcv_init+0x2dd/0x378 [aacraid]

May 28 05:23:59 Tower9 kernel: [<ffffffffa05c795a>] _aac_reset_adapter+0x359/0x59d [aacraid]

May 28 05:23:59 Tower9 kernel: [<ffffffffa05c7cf1>] aac_reset_adapter+0x153/0x21a [aacraid]

May 28 05:23:59 Tower9 kernel: [<ffffffffa05c004f>] aac_eh_reset+0x181/0x18f [aacraid]

May 28 05:23:59 Tower9 kernel: [<ffffffff814653a0>] scsi_try_host_reset+0x2a/0x7c

May 28 05:23:59 Tower9 kernel: [<ffffffff814664a4>] scsi_eh_ready_devs+0x4ba/0x59f

May 28 05:23:59 Tower9 kernel: [<ffffffff81466ec3>] scsi_error_handler+0x240/0x49a

May 28 05:23:59 Tower9 kernel: [<ffffffff81466c83>] ? scsi_eh_get_sense+0xd5/0xd5

May 28 05:23:59 Tower9 kernel: [<ffffffff8105f870>] kthread+0xcd/0xd5

May 28 05:23:59 Tower9 kernel: [<ffffffff8105f7a3>] ? kthread_worker_fn+0x137/0x137

May 28 05:23:59 Tower9 kernel: [<ffffffff8161a3ff>] ret_from_fork+0x3f/0x70

May 28 05:23:59 Tower9 kernel: [<ffffffff8105f7a3>] ? kthread_worker_fn+0x137/0x137

May 28 05:23:59 Tower9 kernel: Mem-Info:

May 28 05:23:59 Tower9 kernel: active_anon:329602 inactive_anon:113161 isolated_anon:0

May 28 05:23:59 Tower9 kernel: active_file:481924 inactive_file:6868994 isolated_file:0

May 28 05:23:59 Tower9 kernel: unevictable:0 dirty:1675 writeback:6820 unstable:0

May 28 05:23:59 Tower9 kernel: slab_reclaimable:271591 slab_unreclaimable:17517

May 28 05:23:59 Tower9 kernel: mapped:22317 shmem:128685 pagetables:3104 bounce:0

May 28 05:23:59 Tower9 kernel: free:44604 free_pcp:1855 free_cma:0

May 28 05:23:59 Tower9 kernel: Node 0 DMA free:15716kB min:8kB low:8kB high:12kB active_anon:16kB inactive_anon:144kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15960kB managed:15876kB mlocked:0kB dirty:0kB writeback:0kB mapped:16kB shmem:160kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes

May 28 05:23:59 Tower9 kernel: lowmem_reserve[]: 0 1914 32121 32121

May 28 05:23:59 Tower9 kernel: Node 0 DMA32 free:128872kB min:1360kB low:1700kB high:2040kB active_anon:292288kB inactive_anon:31728kB active_file:125252kB inactive_file:1263300kB unevictable:0kB isolated(anon):0kB isolated(file):128kB present:1971440kB managed:1961772kB mlocked:0kB dirty:0kB writeback:764kB mapped:6428kB shmem:34368kB slab_reclaimable:83352kB slab_unreclaimable:4484kB kernel_stack:832kB pagetables:1248kB unstable:0kB bounce:0kB free_pcp:3668kB local_pcp:416kB free_cma:0kB writeback_tmp:0kB pages_scanned:172 all_unreclaimable? no

May 28 05:23:59 Tower9 kernel: lowmem_reserve[]: 0 0 30206 30206

May 28 05:23:59 Tower9 kernel: Node 0 Normal free:33828kB min:21496kB low:26868kB high:32244kB active_anon:1026104kB inactive_anon:420772kB active_file:1802444kB inactive_file:26212504kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:31457280kB managed:30931588kB mlocked:0kB dirty:6700kB writeback:26516kB mapped:82824kB shmem:480212kB slab_reclaimable:1003012kB slab_unreclaimable:65584kB kernel_stack:8864kB pagetables:11168kB unstable:0kB bounce:0kB free_pcp:3796kB local_pcp:164kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no

May 28 05:23:59 Tower9 kernel: lowmem_reserve[]: 0 0 0 0

May 28 05:23:59 Tower9 kernel: Node 0 DMA: 1*4kB (U) 0*8kB 0*16kB 1*32kB (M) 3*64kB (UM) 1*128kB (U) 2*256kB (UM) 1*512kB (M) 2*1024kB (UM) 2*2048kB (UM) 2*4096kB (M) = 15716kB

May 28 05:23:59 Tower9 kernel: Node 0 DMA32: 96*4kB (UMEH) 57*8kB (UMEH) 47*16kB (UMEH) 126*32kB (UMEH) 476*64kB (UMH) 80*128kB (UMH) 123*256kB (UMH) 42*512kB (UME) 27*1024kB (UME) 1*2048kB (U) 0*4096kB = 129016kB

May 28 05:23:59 Tower9 kernel: Node 0 Normal: 57*4kB (ME) 84*8kB (UME) 177*16kB (UME) 86*32kB (UME) 11*64kB (UM) 12*128kB (M) 66*256kB (UM) 12*512kB (ME) 2*1024kB (M) 0*2048kB 0*4096kB = 33812kB

May 28 05:23:59 Tower9 kernel: 7477409 total pagecache pages

May 28 05:23:59 Tower9 kernel: 0 pages in swap cache

May 28 05:23:59 Tower9 kernel: Swap cache stats: add 0, delete 0, find 0/0

May 28 05:23:59 Tower9 kernel: Free swap = 0kB

May 28 05:23:59 Tower9 kernel: Total swap = 0kB

May 28 05:23:59 Tower9 kernel: 8361170 pages RAM

May 28 05:23:59 Tower9 kernel: 0 pages HighMem/MovableOnly

May 28 05:23:59 Tower9 kernel: 133861 pages reserved

May 28 07:33:54 Tower9 in.telnetd[316]: connect from 192.168.0.46 (192.168.0.46)

May 28 07:33:56 Tower9 login[317]: ROOT LOGIN on '/dev/pts/0' from 'super9-WS'

May 28 07:34:41 Tower9 in.telnetd[423]: connect from 192.168.0.46 (192.168.0.46)

May 28 07:34:43 Tower9 login[424]: ROOT LOGIN on '/dev/pts/1' from 'super9-WS'

nexusmaniac · May 30, 2016

Not sure what's going on - the web ui seems quite wonky

Normally set to the black theme - but now it's white, the dashboard is blank, the Docker tab is broken and everything else seems off

Syslog is filled up with /dev/sda errors

May 30 13:47:11 Raptor kernel: usb 4-1: USB disconnect, device number 2
May 30 13:47:11 Raptor kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
May 30 13:47:11 Raptor kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
May 30 13:47:11 Raptor kernel: scsi host7: usb-storage 4-1:1.0
May 30 13:47:12 Raptor kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: Attached scsi generic sg0 type 0
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] 30031250 512-byte logical blocks: (15.4 GB/14.3 GiB)
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write Protect is off
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Mode Sense: 43 00 00 00
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 30 13:47:12 Raptor kernel: sdh: sdh1
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Attached SCSI removable disk
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: fat__get_entry: 6 callbacks suppressed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): FAT read failed (blocknr 3480)
May 30 14:21:01 Raptor kernel: ------------[ cut here ]------------
May 30 14:21:01 Raptor kernel: WARNING: CPU: 0 PID: 28498 at fs/fs-writeback.c:2100 __mark_inode_dirty+0x1d2/0x1e3()
May 30 14:21:01 Raptor kernel: bdi-block not registered
May 30 14:21:01 Raptor kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb ahci i2c_i801 libahci fbdev x86_pkg_temp_thermal coretemp kvm_intel igb kvm ptp pps_core i2c_algo_bit ipmi_si acpi_cpufreq
May 30 14:21:01 Raptor kernel: CPU: 0 PID: 28498 Comm: php Not tainted 4.4.6-unRAID #1
May 30 14:21:01 Raptor kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./E3C226D2I, BIOS P3.30 06/04/2015
May 30 14:21:01 Raptor kernel: 0000000000000000 ffff8801024f7ba0 ffffffff813688da ffff8801024f7be8
May 30 14:21:01 Raptor kernel: 0000000000000834 ffff8801024f7bd8 ffffffff8104a28a ffffffff8112940d
May 30 14:21:01 Raptor kernel: ffff88040a190340 ffff88040997bb80 0000000000000000 ffff88040a1903c0
May 30 14:21:01 Raptor kernel: Call Trace:
May 30 14:21:01 Raptor kernel: [<ffffffff813688da>] dump_stack+0x61/0x7e
May 30 14:21:01 Raptor kernel: [<ffffffff8104a28a>] warn_slowpath_common+0x8f/0xa8
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] ? __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff8104a2e6>] warn_slowpath_fmt+0x43/0x4b
May 30 14:21:01 Raptor kernel: [<ffffffff81127cc2>] ? locked_inode_to_wb_and_lock_list+0x64/0xf7
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff811c36de>] mark_fsinfo_dirty+0x28/0x2a
May 30 14:21:01 Raptor kernel: [<ffffffff811c4212>] fat_alloc_clusters+0x327/0x40e
May 30 14:21:01 Raptor kernel: [<ffffffff81110e7f>] ? terminate_walk+0x21/0x82
May 30 14:21:01 Raptor kernel: [<ffffffff81086f16>] ? rcu_is_watching+0x10/0x22
May 30 14:21:01 Raptor kernel: [<ffffffff81119798>] ? __d_instantiate+0x84/0xda
May 30 14:21:01 Raptor kernel: [<ffffffff811c2d6c>] fat_alloc_new_dir+0x30/0x1ca
May 30 14:21:01 Raptor kernel: [<ffffffff811c83ca>] ? vfat_lookup+0xdb/0x145
May 30 14:21:01 Raptor kernel: [<ffffffff811c946b>] vfat_mkdir+0x4d/0x140
May 30 14:21:01 Raptor kernel: [<ffffffff81111690>] vfs_mkdir+0x7e/0xae
May 30 14:21:01 Raptor kernel: [<ffffffff81115a6f>] SyS_mkdirat+0x75/0xac
May 30 14:21:01 Raptor kernel: [<ffffffff81115aba>] SyS_mkdir+0x14/0x16
May 30 14:21:01 Raptor kernel: [<ffffffff8161a0ae>] entry_SYSCALL_64_fastpath+0x12/0x6d
May 30 14:21:01 Raptor kernel: ---[ end trace fd44b47a9ddf242e ]---

sda is generally your Flash Drive. I would suspect some sort of corruption on that device. Suggest you run chkdsk (or the Apple equivalent) on it.

It is.

I've just run chkdsk on my Windows PC - No errors / issues reported

Post complete diagnostics file. ('Tools' >>>> 'Diagnostics')

Had already rebooted before you posted this - Sorry

nexusmaniac · May 30, 2016

Not sure what's going on - the web ui seems quite wonky

Normally set to the black theme - but now it's white, the dashboard is blank, the Docker tab is broken and everything else seems off

Syslog is filled up with /dev/sda errors

May 30 13:47:11 Raptor kernel: usb 4-1: USB disconnect, device number 2
May 30 13:47:11 Raptor kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
May 30 13:47:11 Raptor kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
May 30 13:47:11 Raptor kernel: scsi host7: usb-storage 4-1:1.0
May 30 13:47:12 Raptor kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: Attached scsi generic sg0 type 0
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] 30031250 512-byte logical blocks: (15.4 GB/14.3 GiB)
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write Protect is off
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Mode Sense: 43 00 00 00
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 30 13:47:12 Raptor kernel: sdh: sdh1
May 30 13:47:12 Raptor kernel: sd 7:0:0:0: [sdh] Attached SCSI removable disk
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 13:47:15 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: fat__get_entry: 6 callbacks suppressed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed
May 30 14:21:01 Raptor kernel: FAT-fs (sda1): FAT read failed (blocknr 3480)
May 30 14:21:01 Raptor kernel: ------------[ cut here ]------------
May 30 14:21:01 Raptor kernel: WARNING: CPU: 0 PID: 28498 at fs/fs-writeback.c:2100 __mark_inode_dirty+0x1d2/0x1e3()
May 30 14:21:01 Raptor kernel: bdi-block not registered
May 30 14:21:01 Raptor kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ast drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb ahci i2c_i801 libahci fbdev x86_pkg_temp_thermal coretemp kvm_intel igb kvm ptp pps_core i2c_algo_bit ipmi_si acpi_cpufreq
May 30 14:21:01 Raptor kernel: CPU: 0 PID: 28498 Comm: php Not tainted 4.4.6-unRAID #1
May 30 14:21:01 Raptor kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./E3C226D2I, BIOS P3.30 06/04/2015
May 30 14:21:01 Raptor kernel: 0000000000000000 ffff8801024f7ba0 ffffffff813688da ffff8801024f7be8
May 30 14:21:01 Raptor kernel: 0000000000000834 ffff8801024f7bd8 ffffffff8104a28a ffffffff8112940d
May 30 14:21:01 Raptor kernel: ffff88040a190340 ffff88040997bb80 0000000000000000 ffff88040a1903c0
May 30 14:21:01 Raptor kernel: Call Trace:
May 30 14:21:01 Raptor kernel: [<ffffffff813688da>] dump_stack+0x61/0x7e
May 30 14:21:01 Raptor kernel: [<ffffffff8104a28a>] warn_slowpath_common+0x8f/0xa8
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] ? __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff8104a2e6>] warn_slowpath_fmt+0x43/0x4b
May 30 14:21:01 Raptor kernel: [<ffffffff81127cc2>] ? locked_inode_to_wb_and_lock_list+0x64/0xf7
May 30 14:21:01 Raptor kernel: [<ffffffff8112940d>] __mark_inode_dirty+0x1d2/0x1e3
May 30 14:21:01 Raptor kernel: [<ffffffff811c36de>] mark_fsinfo_dirty+0x28/0x2a
May 30 14:21:01 Raptor kernel: [<ffffffff811c4212>] fat_alloc_clusters+0x327/0x40e
May 30 14:21:01 Raptor kernel: [<ffffffff81110e7f>] ? terminate_walk+0x21/0x82
May 30 14:21:01 Raptor kernel: [<ffffffff81086f16>] ? rcu_is_watching+0x10/0x22
May 30 14:21:01 Raptor kernel: [<ffffffff81119798>] ? __d_instantiate+0x84/0xda
May 30 14:21:01 Raptor kernel: [<ffffffff811c2d6c>] fat_alloc_new_dir+0x30/0x1ca
May 30 14:21:01 Raptor kernel: [<ffffffff811c83ca>] ? vfat_lookup+0xdb/0x145
May 30 14:21:01 Raptor kernel: [<ffffffff811c946b>] vfat_mkdir+0x4d/0x140
May 30 14:21:01 Raptor kernel: [<ffffffff81111690>] vfs_mkdir+0x7e/0xae
May 30 14:21:01 Raptor kernel: [<ffffffff81115a6f>] SyS_mkdirat+0x75/0xac
May 30 14:21:01 Raptor kernel: [<ffffffff81115aba>] SyS_mkdir+0x14/0x16
May 30 14:21:01 Raptor kernel: [<ffffffff8161a0ae>] entry_SYSCALL_64_fastpath+0x12/0x6d
May 30 14:21:01 Raptor kernel: ---[ end trace fd44b47a9ddf242e ]---

sda is generally your Flash Drive. I would suspect some sort of corruption on that device. Suggest you run chkdsk (or the Apple equivalent) on it.

It is.

I've just run chkdsk on my Windows PC - No errors / issues reported

Post complete diagnostics file. ('Tools' >>>> 'Diagnostics')

Ross it in a different port and speed (2.0 vs 3.0) if you can

Bread errors tend to happen when the port loses track of the stick and then remounts it

Sent from my LG-D852 using Tapatalk

It's happened twice in the month of May... I'm using a Sandisk Ultra Fit - Which is a pretty decent USB drive And a server grade Asrock - I can try a USB 2 port, but I wish I didn't need to haha

No other cause you can think of? There's not a 'chkdsk' tool included with unRAID by any chance?

Frank1940 · May 30, 2016

No other cause you can think of? There's not a 'chkdsk' tool included with unRAID by any chance?

I googled and found this:

http://www.thegeekstuff.com/2012/08/fsck-command-examples/

I am not sure how many of these are a part of the unRAID distribution but a quick check show that fsck was. Someone else will have to walk you through its usage or you will have to find the man(ual) pages to be able to really use it.

unRAID Server Release 6.2.0-beta21 Available

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment