Edgeman56

I have mine downloading and unpacking to cache, my problem was that the unpacker was hung up in that background and used all cpu until the server crashed, and then when it started up it would start all over again. Thanks to the help on here I have the problem resolved. And it is great to have a community that is so knowledgeable and willing to help.

Thank you for all the help, sabnzb is causing the server to lockup. I can now focus on what is wrong. Thanks for you help and time it is much appreciated.

Here is the diagnostic file, the server has been up and running for 30mins or so and is pegged at 100%. So it shouldn't be startup programs. Thanks for the help. server-diagnostics-20220804-1240.zip

I just put the server online so I will let it run for a bit and repost, it has just been pegging the cpu at 100 percent to the point the server shuts down. I will repost the diagnostics after 30 mins or so. Thank you for your input, and your time

Sorry about that here it is. server-diagnostics-20220804-1150.zip

For that past 2 days or so my server is running at 100 percent cpu usage. I updated to the newest version today and I am still having the same problem. I attached the server log and the processes log also. I have tried stopping all apps and it seems to have very little effect. Not sure what the next step should be. Thanks for any help you can provide. server-syslog-20220804-1507.zip processes.txt

I have the fix common problems app running on my Unraid server, and it has warned me that I have call traces? Not sure what that means, but it suggest that I post my diagnostic here and ask for help, so that is what I am doing. So any help or guidance would be greatly appreciated. Thanks. server-diagnostics-20170527-1148.zip

Rebuilt the drive and everything is working, I have it running a parity check. Thanks for the help.

I have it chugging away hopefully in 12 hours or so all will be right again. On the dashboard screen under the parity status in red letters it reads Data is invalid, I guess that must be for the bad drive. Thanks for all the help, hopefully one day I will have a clue and be able to do this on my own. Thanks again. I will report back on the drive rebuild.

Here is another snap of the config that I missed in the first pic.

Here is the the main page shot and the dashboard.

Well that is not good. In that main page it says configuration valid, and on the dashboard under parity status it has data is invalid. So is it worth trying to rebuild or is it just not going to work. And if it is not going to work i just need to uninstall the bad drive and install a new one and do a parity sync to get back to working, then transfer off the old drive from the windows computer. And what caused this big of a failure with just one drive having problems??? Thanks.

The drive finished the extended smart check and found no errors. I have another drive that will be here tomorrow. My parity shows invalid I am assuming that is because the drive error happened during a parity check. So with it showing invalid will I have problems with the rebuild? And is there any way to find out what the cause of the problem was. And is there anything more I need to know to get this rebuilt. Thanks for all the help.

Is there a way to just bring that drive online without a rebuild?? Assuming the extended test comes back fine is there a way to bring the drive back into the drive pool without any risk of data loss?? This is my first drive error so I am worried that I will do somthing stupid and lose data. Thanks.

Ran a parity check and a drive is showing a red x and says device is disabled and being emulated. I grabbed the diagnostic file then shut down the server to make sure all the cables where seated correctly. This is the smart data form the diagnostic file. === START OF INFORMATION SECTION === Vendor: /2:0:1:0 Product: User Capacity: 600,332,565,813,390,450 bytes [600 PB] Logical block size: 774843950 bytes Physical block size: 1549687900 bytes Lowest aligned LBA: 14896 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 >> Terminate command early due to bad response to IEC mode page A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. I shut down the system and rechecked all the cables connections restarted and the smart data from that disc passed, zip attached. I am now running the extended self test. So my question is what should I do? I have read previous post and I believe I should. Stop the array Unassign the disk Start the array. Stop the array Assign the disk Start the array and parity build should start Please let me know if this is what I should do assuming it passes the long test. If this is all wrong please let me know what I should do. Thank you. server-smart-20151015-1220.zip

Thank you again for your help, I rebooted again and the file was able to be created, and I also disabled unmenu in the go file. I will eventually get these problems worked out with the flash drive, the problem is that is can take upwards of a 2 weeks for it to reappear. I have switched flash drives switched USB ports, next is to disable usb3 in the bios and see if that helps. If you know of anything else I should try or watch for I am all ears. And thanks again form taking the time and helping me out.

Ran chkdsk on windows machine and rebooted and have the same error. I attached the diagnostics file. Thanks for the help at some point I will have all the bugs worked out and have a clue as to what I am doing. server-diagnostics-20150917-1241.zip

Trying to install this plugin(my first) and I get this error. Is there somthing this I am missing? I am also running version 6.1.2. Thanks for any help. Sep 16 21:45:01 server emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install error: unable to create parent directory for /boot/config/plugins/community.applications/community.applications-2015.09.15.txz Sep 16 21:45:25 server emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

Interesting I though it was a software problem, I'll change ports and dig around in the bios and give it a go. Thanks for the idea.

Sorry here are the attachments. server-diagnostics-20150913-1436.zip

System running version 6.1.2 Supermicro - X10SL7-F Intel® Xeon®CPU E3-1271 v3 @ 3.60GHz-F I have had continuing issues with my flash drive becoming corrupted and have no idea what is causing it. Before the upgrade to 6.1.2 the flash drive would show an error and the mover would move the appdate fold to the array, and if I rebooted the server it would show and invalid parity, and I would have to run check disk on a windows computer. Now that I am on 6.1.2 it did not move the appdata folder but on the dashboard it doesn't show the dockers I am using(Sickbeard and Sabnzb) and in the docker tab I get error messages, I have attached a screen shot of that. Also a week ago I replaced the flash dive thinking that was the issue, and that has had no effect. I am not very experienced in this so any help would be greatly appreciated. I am also attaching a section of the syslog that look like the problem. Again thank you for any help. Sep 13 09:08:18 server kernel: fat__get_entry: 182 callbacks suppressed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 09:08:18 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 09:08:18 server kernel: ------------[ cut here ]------------ Sep 13 09:08:18 server kernel: WARNING: CPU: 6 PID: 15795 at fs/fs-writeback.c:1327 __mark_inode_dirty+0x162/0x265() Sep 13 09:08:18 server kernel: bdi-block not registered Sep 13 09:08:18 server kernel: Modules linked in: kvm_intel kvm 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 mvsas libahci igb libsas i2c_algo_bit ptp pps_core mpt2sas raid_class scsi_transport_sas ipmi_si [last unloaded: md_mod] Sep 13 09:08:18 server kernel: CPU: 6 PID: 15795 Comm: php Not tainted 4.1.5-unRAID #5 Sep 13 09:08:18 server kernel: Hardware name: Supermicro X10SL7-F/X10SL7-F, BIOS 2.00 04/24/2014 Sep 13 09:08:18 server kernel: 0000000000000009 ffff880100dd3b78 ffffffff816105e3 0000000000000000 Sep 13 09:08:18 server kernel: ffff880100dd3bc8 ffff880100dd3bb8 ffffffff8104774b ffff88041ffb3cd8 Sep 13 09:08:18 server kernel: ffffffff8111cae4 ffff88040a230330 ffff880400bd8180 ffff880400bd8390 Sep 13 09:08:18 server kernel: Call Trace: Sep 13 09:08:18 server kernel: [] dump_stack+0x4c/0x6e Sep 13 09:08:18 server kernel: [] warn_slowpath_common+0x97/0xb1 Sep 13 09:08:18 server kernel: [] ? __mark_inode_dirty+0x162/0x265 Sep 13 09:08:18 server kernel: [] warn_slowpath_fmt+0x41/0x43 Sep 13 09:08:18 server kernel: [] __mark_inode_dirty+0x162/0x265 Sep 13 09:08:18 server kernel: [] mark_fsinfo_dirty+0x28/0x2a Sep 13 09:08:18 server kernel: [] fat_alloc_clusters+0x326/0x411 Sep 13 09:08:18 server kernel: [] ? d_rehash+0x4f/0x54 Sep 13 09:08:18 server kernel: [] ? d_alloc+0x6c/0x78 Sep 13 09:08:18 server kernel: [] fat_alloc_new_dir+0x30/0x1c8 Sep 13 09:08:18 server kernel: [] ? lookup_hash+0x14/0x16 Sep 13 09:08:18 server kernel: [] ? filename_create+0x85/0x13e Sep 13 09:08:18 server kernel: [] vfat_mkdir+0x4c/0x13e Sep 13 09:08:18 server kernel: [] ? __inode_permission+0x61/0x9f Sep 13 09:08:18 server kernel: [] vfs_mkdir+0x6e/0xa8 Sep 13 09:08:18 server kernel: [] SyS_mkdirat+0x6d/0xab Sep 13 09:08:18 server kernel: [] SyS_mkdir+0x14/0x16 Sep 13 09:08:18 server kernel: [] system_call_fastpath+0x12/0x71 Sep 13 09:08:18 server kernel: ---[ end trace ba9000e340e31633 ]--- Sep 13 09:08:23 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 09:08:27 server kernel: fat__get_entry: 182 callbacks suppressed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 09:08:27 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 09:08:32 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 09:08:32 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 09:09:32 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 09:09:32 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 09:10:02 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 09:10:02 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 10:09:51 server kernel: mdcmd (209): spindown 12 Sep 13 14:24:55 server kernel: kvm: already loaded the other module Sep 13 14:27:21 server kernel: fat__get_entry: 118 callbacks suppressed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 14:27:21 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 14:28:54 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 14:28:54 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 14:29:09 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 14:29:09 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 14:31:48 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 14:31:48 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 14:31:54 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 14:31:54 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 14:32:34 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 14:32:34 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) Sep 13 14:42:23 server kernel: fat__get_entry: 54 callbacks suppressed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Sep 13 14:42:23 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed Sep 13 14:42:24 server kernel: FAT-fs (sda1): FAT read failed (blocknr 799) server-diagnostics-20150913-1436.zip

System running version 6.1.2 Supermicro - X10SL7-F Intel® Xeon®CPU E3-1271 v3 @ 3.60GHz-F

I have had a reoccurring issue where my flash drive will get corrupted and the the mover will move the the docker files in my appdata. I believe this is being causes by the UPS program. I have tried to set it up but it never actually shuts down the computer just flashes warnings that there is no power and that the system is going into shutdown and never does. I just the other day replaced my flash drive thinking it was the problem but that does not seem to be the case. I have attached the diagnostic files in hope someone can help. Thanks for any light you can shed on this problem. server-diagnostics-20150901-1341.zip

Thanks for the help I am going to replace the usb drive and see if this solves the problem. Thanks for taking the time to help me out again.

Also I rebooted the server and when it started up it had detected and unclean shutdown, so i am attaching the diagnostics file from that, just trying to give you guys as much information to help me I can. Thank you. server-diagnostics-20150828-1413.zip