brownster Posted November 13, 2017 Share Posted November 13, 2017 Hello, Whilst copying some files over from a mounted unassigned drive to a share via command line cp command I started to get "unable to write disk" "disk full" messages. When checking the web interface all the shares i created have disappeared. Looking at the log it seems i have a hardware issue but cant tell if its a disk or a controller, could i possibly trouble someone with more knowledge than I to take a look at my log file? I suspect a reboot will bring the shares back but thought i would wait. Attached log and diagnostics file also a screen shot of the disks. Thanks Marc unraid log.txt tower-diagnostics-20171113-0527.zip Quote Link to comment
JorgeB Posted November 13, 2017 Share Posted November 13, 2017 Nov 13 05:06:22 Tower kernel: XFS (md1): Corruption of in-memory data detected. Shutting down filesystem Nov 13 05:06:22 Tower kernel: XFS (md1): Please umount the filesystem and rectify the problem(s) Not sure this can be caused just file the filesystem being full, you should at least run a few memtest passes. Quote Link to comment
brownster Posted November 13, 2017 Author Share Posted November 13, 2017 Ran memtest for three passes no errors The drives aren't full, i think that error was more down to access to the drives Quote Link to comment
brownster Posted November 13, 2017 Author Share Posted November 13, 2017 Booted back into Unraid and no shares in the web interface... how do i get the shares back with the data? Quote Link to comment
brownster Posted November 13, 2017 Author Share Posted November 13, 2017 (edited) rebooted again started array this time I can see the shares Would like to know what caused it. Edited November 13, 2017 by brownster Quote Link to comment
JorgeB Posted November 13, 2017 Share Posted November 13, 2017 23 minutes ago, brownster said: The drives aren't full, i think that error was more down to access to the drives Disk1 was completely full and giving out space errors before the filesystem shutdown. Quote Link to comment
JorgeB Posted November 13, 2017 Share Posted November 13, 2017 8 minutes ago, brownster said: Would like to know what caused it. 2 hours ago, johnnie.black said: Shutting down filesystem 1 Quote Link to comment
brownster Posted November 13, 2017 Author Share Posted November 13, 2017 Thanks Johnnie changed the share from high water to most free, see if that helps it was set to split on top level (which would be film title folder Quote Link to comment
JorgeB Posted November 13, 2017 Share Posted November 13, 2017 Attention that split level takes precedence over allocation mode. 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.