Swixxy

Members
  • Posts

    117
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Swixxy's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. Ah wicked thank you for the reply. So what do i do if the drive itself were to be dead? is there a way for me to force a repair on the parity disk emulated version, or will i have to reset all disks and rebuild parityfrom scratch
  2. Hey guys, so today my flash drive seems like it corrupted slightly. Server was running fine, however my flash drive became unresponsive, so i booted down, and ran chkdsk on the flash. Booted up successfully, however since then every time i try to start unraid it gives me this error in the syslog. It spins up the drives perfectly fine in maintenance mode, not sure what the error is. I've since updated to the latest version of unraid, just in case maybe an old file was corrupted however its still doing the same thing. Any advice? seems like there hasn't been this error posted on here before, im a bit stumped with how to proceed. I thought at first it might just be disk11, however i've since tried to remove it from my array and boot, but it seems to not be related to the last disk, but rather mounting the unraid filesystem itself? I'm going to go through and reseat each cable one by one, just incase its an odd little hardware bug, however if anybody could help out, id be most grateful. Jun 10 20:00:44 jbox emhttp: shcmd (109): mkdir -p /mnt/disk11 Jun 10 20:00:44 jbox emhttp: shcmd (110): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md11 /mnt/disk11 |& logger Jun 10 20:00:44 jbox kernel: XFS (md11): Mounting V5 Filesystem Jun 10 20:00:44 jbox kernel: XFS (md11): Starting recovery (logdev: internal) Jun 10 20:00:55 jbox kernel: XFS (md11): _xfs_buf_find: Block out of range: block 0x7fffffff8, EOFS 0x2baa0f448 Jun 10 20:00:55 jbox kernel: ------------[ cut here ]------------ Jun 10 20:00:55 jbox kernel: WARNING: CPU: 3 PID: 5792 at fs/xfs/xfs_buf.c:521 _xfs_buf_find+0x7f/0x28c Jun 10 20:00:55 jbox kernel: Modules linked in: md_mod e1000e ptp pps_core coretemp kvm_intel kvm i2c_i801 i2c_smbus i2c_core ahci libahci mvsas libsas scsi_transport_sas acpi_cpufreq [last unloaded: md_mod] Jun 10 20:00:55 jbox kernel: CPU: 3 PID: 5792 Comm: mount Not tainted 4.9.30-unRAID #1 Jun 10 20:00:55 jbox kernel: Hardware name: Supermicro X8SIL/X8SIL, BIOS 1.1 05/27/2010 Jun 10 20:00:55 jbox kernel: ffffc900089038a8 ffffffff813a4a1b 0000000000000000 ffffffff81965360 Jun 10 20:00:55 jbox kernel: ffffc900089038e8 ffffffff8104d0d9 0000020900000008 ffff88020634e000 Jun 10 20:00:55 jbox kernel: ffff880207b1d240 ffff880207b1d240 0000000000000000 0000000000000000 Jun 10 20:00:55 jbox kernel: Call Trace: Jun 10 20:00:55 jbox kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Jun 10 20:00:55 jbox kernel: [<ffffffff8104d0d9>] __warn+0xb8/0xd3 Jun 10 20:00:55 jbox kernel: [<ffffffff8104d1a1>] warn_slowpath_null+0x18/0x1a Jun 10 20:00:55 jbox kernel: [<ffffffff8129a9f3>] _xfs_buf_find+0x7f/0x28c Jun 10 20:00:55 jbox kernel: [<ffffffff8129ac24>] xfs_buf_get_map+0x24/0x12b Jun 10 20:00:55 jbox kernel: [<ffffffff812c0fb0>] xfs_trans_get_buf_map+0x83/0xaa Jun 10 20:00:55 jbox kernel: [<ffffffff81276512>] xfs_btree_get_bufs+0x4b/0x4d Jun 10 20:00:55 jbox kernel: [<ffffffff812656eb>] xfs_alloc_fix_freelist+0x197/0x317 Jun 10 20:00:55 jbox kernel: [<ffffffff8167c00e>] ? __schedule+0x2b1/0x46a Jun 10 20:00:55 jbox kernel: [<ffffffff81265c4b>] xfs_free_extent_fix_freelist+0x5f/0x8a Jun 10 20:00:55 jbox kernel: [<ffffffff81265cbd>] xfs_free_extent+0x47/0x115 Jun 10 20:00:55 jbox kernel: [<ffffffff812c1555>] xfs_trans_free_extent+0x28/0x65 Jun 10 20:00:55 jbox kernel: [<ffffffff812b932c>] xfs_efi_recover+0x129/0x161 Jun 10 20:00:55 jbox kernel: [<ffffffff812bbd51>] xlog_recover_process_efi+0x35/0x4d Jun 10 20:00:55 jbox kernel: [<ffffffff812bbee7>] xlog_recover_process_intents+0x97/0x100 Jun 10 20:00:55 jbox kernel: [<ffffffff811369ca>] ? unlock_new_inode+0x57/0x5c Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] xlog_recover_finish+0x18/0x8b Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] ? xlog_recover_finish+0x18/0x8b Jun 10 20:00:55 jbox kernel: [<ffffffff812b5091>] xfs_log_mount_finish+0x20/0x36 Jun 10 20:00:55 jbox kernel: [<ffffffff812ac969>] xfs_mountfs+0x63b/0x769 Jun 10 20:00:55 jbox kernel: [<ffffffff812b06a5>] xfs_fs_fill_super+0x485/0x536 Jun 10 20:00:55 jbox kernel: [<ffffffff81123ea9>] mount_bdev+0x139/0x18b Jun 10 20:00:55 jbox kernel: [<ffffffff812b0220>] ? xfs_test_remount_options.isra.1+0x56/0x56 Jun 10 20:00:55 jbox kernel: [<ffffffff812af0c9>] xfs_fs_mount+0x10/0x12 Jun 10 20:00:55 jbox kernel: [<ffffffff81124bc1>] mount_fs+0xf/0x84 Jun 10 20:00:55 jbox kernel: [<ffffffff8113abe3>] vfs_kern_mount+0x65/0xf7 Jun 10 20:00:55 jbox kernel: [<ffffffff8113d444>] do_mount+0x744/0xa23 Jun 10 20:00:55 jbox kernel: [<ffffffff810de06c>] ? strndup_user+0x3a/0x6f Jun 10 20:00:55 jbox kernel: [<ffffffff8113d919>] SyS_mount+0x72/0x9a Jun 10 20:00:55 jbox kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9 Jun 10 20:00:55 jbox kernel: ---[ end trace 3680fca2721e9ba7 ]--- Jun 10 20:00:55 jbox kernel: XFS (md11): _xfs_buf_find: Block out of range: block 0x7fffffff8, EOFS 0x2baa0f448 Jun 10 20:00:55 jbox kernel: ------------[ cut here ]------------ Jun 10 20:00:55 jbox kernel: WARNING: CPU: 3 PID: 5792 at fs/xfs/xfs_buf.c:521 _xfs_buf_find+0x7f/0x28c Jun 10 20:00:55 jbox kernel: Modules linked in: md_mod e1000e ptp pps_core coretemp kvm_intel kvm i2c_i801 i2c_smbus i2c_core ahci libahci mvsas libsas scsi_transport_sas acpi_cpufreq [last unloaded: md_mod] Jun 10 20:00:55 jbox kernel: CPU: 3 PID: 5792 Comm: mount Tainted: G W 4.9.30-unRAID #1 Jun 10 20:00:55 jbox kernel: Hardware name: Supermicro X8SIL/X8SIL, BIOS 1.1 05/27/2010 Jun 10 20:00:55 jbox kernel: ffffc900089038a8 ffffffff813a4a1b 0000000000000000 ffffffff81965360 Jun 10 20:00:55 jbox kernel: ffffc900089038e8 ffffffff8104d0d9 0000020900000008 0000000000000000 Jun 10 20:00:55 jbox kernel: ffff880207b1d240 ffff880207b1d240 ffff880205238900 ffff880205238900 Jun 10 20:00:55 jbox kernel: Call Trace: Jun 10 20:00:55 jbox kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Jun 10 20:00:55 jbox kernel: [<ffffffff8104d0d9>] __warn+0xb8/0xd3 Jun 10 20:00:55 jbox kernel: [<ffffffff8104d1a1>] warn_slowpath_null+0x18/0x1a Jun 10 20:00:55 jbox kernel: [<ffffffff8129a9f3>] _xfs_buf_find+0x7f/0x28c Jun 10 20:00:55 jbox kernel: [<ffffffff81299937>] ? xfs_buf_allocate_memory+0x161/0x2a1 Jun 10 20:00:55 jbox kernel: [<ffffffff8129ac70>] xfs_buf_get_map+0x70/0x12b Jun 10 20:00:55 jbox kernel: [<ffffffff812c0fb0>] xfs_trans_get_buf_map+0x83/0xaa Jun 10 20:00:55 jbox kernel: [<ffffffff81276512>] xfs_btree_get_bufs+0x4b/0x4d Jun 10 20:00:55 jbox kernel: [<ffffffff812656eb>] xfs_alloc_fix_freelist+0x197/0x317 Jun 10 20:00:55 jbox kernel: [<ffffffff8167c00e>] ? __schedule+0x2b1/0x46a Jun 10 20:00:55 jbox kernel: [<ffffffff81265c4b>] xfs_free_extent_fix_freelist+0x5f/0x8a Jun 10 20:00:55 jbox kernel: [<ffffffff81265cbd>] xfs_free_extent+0x47/0x115 Jun 10 20:00:55 jbox kernel: [<ffffffff812c1555>] xfs_trans_free_extent+0x28/0x65 Jun 10 20:00:55 jbox kernel: [<ffffffff812b932c>] xfs_efi_recover+0x129/0x161 Jun 10 20:00:55 jbox kernel: [<ffffffff812bbd51>] xlog_recover_process_efi+0x35/0x4d Jun 10 20:00:55 jbox kernel: [<ffffffff812bbee7>] xlog_recover_process_intents+0x97/0x100 Jun 10 20:00:55 jbox kernel: [<ffffffff811369ca>] ? unlock_new_inode+0x57/0x5c Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] xlog_recover_finish+0x18/0x8b Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] ? xlog_recover_finish+0x18/0x8b Jun 10 20:00:55 jbox kernel: [<ffffffff812b5091>] xfs_log_mount_finish+0x20/0x36 Jun 10 20:00:55 jbox kernel: [<ffffffff812ac969>] xfs_mountfs+0x63b/0x769 Jun 10 20:00:55 jbox kernel: [<ffffffff812b06a5>] xfs_fs_fill_super+0x485/0x536 Jun 10 20:00:55 jbox kernel: [<ffffffff81123ea9>] mount_bdev+0x139/0x18b Jun 10 20:00:55 jbox kernel: [<ffffffff812b0220>] ? xfs_test_remount_options.isra.1+0x56/0x56 Jun 10 20:00:55 jbox kernel: [<ffffffff812af0c9>] xfs_fs_mount+0x10/0x12 Jun 10 20:00:55 jbox kernel: [<ffffffff81124bc1>] mount_fs+0xf/0x84 Jun 10 20:00:55 jbox kernel: [<ffffffff8113abe3>] vfs_kern_mount+0x65/0xf7 Jun 10 20:00:55 jbox kernel: [<ffffffff8113d444>] do_mount+0x744/0xa23 Jun 10 20:00:55 jbox kernel: [<ffffffff810de06c>] ? strndup_user+0x3a/0x6f Jun 10 20:00:55 jbox kernel: [<ffffffff8113d919>] SyS_mount+0x72/0x9a Jun 10 20:00:55 jbox kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9 Jun 10 20:00:55 jbox kernel: ---[ end trace 3680fca2721e9ba8 ]--- Jun 10 20:00:55 jbox kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000000f8 Jun 10 20:00:55 jbox kernel: IP: [<ffffffff812c12e1>] xfs_trans_binval+0x7/0x89 Jun 10 20:00:55 jbox kernel: PGD 23363a067 Jun 10 20:00:55 jbox kernel: PUD 2058db067 Jun 10 20:00:55 jbox kernel: PMD 0 Jun 10 20:00:55 jbox kernel: Jun 10 20:00:55 jbox kernel: Oops: 0000 [#1] PREEMPT SMP Jun 10 20:00:55 jbox kernel: Modules linked in: md_mod e1000e ptp pps_core coretemp kvm_intel kvm i2c_i801 i2c_smbus i2c_core ahci libahci mvsas libsas scsi_transport_sas acpi_cpufreq [last unloaded: md_mod] Jun 10 20:00:55 jbox kernel: CPU: 3 PID: 5792 Comm: mount Tainted: G W 4.9.30-unRAID #1 Jun 10 20:00:55 jbox kernel: Hardware name: Supermicro X8SIL/X8SIL, BIOS 1.1 05/27/2010 Jun 10 20:00:55 jbox kernel: task: ffff8802341b9700 task.stack: ffffc90008900000 Jun 10 20:00:55 jbox kernel: RIP: 0010:[<ffffffff812c12e1>] [<ffffffff812c12e1>] xfs_trans_binval+0x7/0x89 Jun 10 20:00:55 jbox kernel: RSP: 0018:ffffc900089039c8 EFLAGS: 00010246 Jun 10 20:00:55 jbox kernel: RAX: 0000000000000000 RBX: ffffc90008903ae0 RCX: 0000000000176b03 Jun 10 20:00:55 jbox kernel: RDX: 0000000000000008 RSI: 0000000000000000 RDI: ffff88020634e000 Jun 10 20:00:55 jbox kernel: RBP: ffffc900089039d8 R08: 000000000001b750 R09: ffffffff8129a3e2 Jun 10 20:00:55 jbox kernel: R10: ffffea0008148e00 R11: ffffffff81de6f0c R12: ffff88020634e000 Jun 10 20:00:55 jbox kernel: R13: ffff8802337e1200 R14: 0000000000000002 R15: ffff880205ecc000 Jun 10 20:00:55 jbox kernel: FS: 00002ae949f9ce40(0000) GS:ffff88023fcc0000(0000) knlGS:0000000000000000 Jun 10 20:00:55 jbox kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 10 20:00:55 jbox kernel: CR2: 00000000000000f8 CR3: 0000000233643000 CR4: 00000000000006e0 Jun 10 20:00:55 jbox kernel: Stack: Jun 10 20:00:55 jbox kernel: ffffc90008903ae0 ffff88020634e000 ffffc90008903ad0 ffffffff812656f6 Jun 10 20:00:55 jbox kernel: 0000000608903a28 ffffffff8167c00e ffff88020509d680 0000000000000000 Jun 10 20:00:55 jbox kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Jun 10 20:00:55 jbox kernel: Call Trace: Jun 10 20:00:55 jbox kernel: [<ffffffff812656f6>] xfs_alloc_fix_freelist+0x1a2/0x317 Jun 10 20:00:55 jbox kernel: [<ffffffff8167c00e>] ? __schedule+0x2b1/0x46a Jun 10 20:00:55 jbox kernel: [<ffffffff81265c4b>] xfs_free_extent_fix_freelist+0x5f/0x8a Jun 10 20:00:55 jbox kernel: [<ffffffff81265cbd>] xfs_free_extent+0x47/0x115 Jun 10 20:00:55 jbox kernel: [<ffffffff812c1555>] xfs_trans_free_extent+0x28/0x65 Jun 10 20:00:55 jbox kernel: [<ffffffff812b932c>] xfs_efi_recover+0x129/0x161 Jun 10 20:00:55 jbox kernel: [<ffffffff812bbd51>] xlog_recover_process_efi+0x35/0x4d Jun 10 20:00:55 jbox kernel: [<ffffffff812bbee7>] xlog_recover_process_intents+0x97/0x100 Jun 10 20:00:55 jbox kernel: [<ffffffff811369ca>] ? unlock_new_inode+0x57/0x5c Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] xlog_recover_finish+0x18/0x8b Jun 10 20:00:55 jbox kernel: [<ffffffff812c008a>] ? xlog_recover_finish+0x18/0x8b Jun 10 20:00:55 jbox kernel: [<ffffffff812b5091>] xfs_log_mount_finish+0x20/0x36 Jun 10 20:00:55 jbox kernel: [<ffffffff812ac969>] xfs_mountfs+0x63b/0x769 Jun 10 20:00:55 jbox kernel: [<ffffffff812b06a5>] xfs_fs_fill_super+0x485/0x536 Jun 10 20:00:55 jbox kernel: [<ffffffff81123ea9>] mount_bdev+0x139/0x18b Jun 10 20:00:55 jbox kernel: [<ffffffff812b0220>] ? xfs_test_remount_options.isra.1+0x56/0x56 Jun 10 20:00:55 jbox kernel: [<ffffffff812af0c9>] xfs_fs_mount+0x10/0x12 Jun 10 20:00:55 jbox kernel: [<ffffffff81124bc1>] mount_fs+0xf/0x84 Jun 10 20:00:55 jbox kernel: [<ffffffff8113abe3>] vfs_kern_mount+0x65/0xf7 Jun 10 20:00:55 jbox kernel: [<ffffffff8113d444>] do_mount+0x744/0xa23 Jun 10 20:00:55 jbox kernel: [<ffffffff810de06c>] ? strndup_user+0x3a/0x6f Jun 10 20:00:55 jbox kernel: [<ffffffff8113d919>] SyS_mount+0x72/0x9a Jun 10 20:00:55 jbox kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9 Jun 10 20:00:55 jbox kernel: Code: 00 89 d6 83 ce 0a 80 e2 80 89 b0 80 00 00 00 75 12 55 89 ca 44 89 ce 48 89 c7 48 89 e5 e8 1f 77 ff ff 5d c3 55 48 89 e5 41 54 53 <48> 8b 9e f8 00 00 00 f6 83 80 00 00 00 04 75 6d 49 89 fc 48 89 Jun 10 20:00:55 jbox kernel: RIP [<ffffffff812c12e1>] xfs_trans_binval+0x7/0x89 Jun 10 20:00:55 jbox kernel: RSP <ffffc900089039c8> Jun 10 20:00:55 jbox kernel: CR2: 00000000000000f8 Jun 10 20:00:55 jbox kernel: ---[ end trace 3680fca2721e9ba9 ]--- Jun 10 20:00:55 jbox emhttp: err: shcmd: shcmd (110): exit status: -119 Jun 10 20:00:55 jbox emhttp: mount error: No file system (-119) Jun 10 20:00:55 jbox emhttp: shcmd (111): umount /mnt/disk11 |& logger Jun 10 20:00:55 jbox root: umount: /mnt/disk11: not mounted Jun 10 20:00:55 jbox emhttp: shcmd (112): rmdir /mnt/disk11 Jun 10 20:00:55 jbox emhttp: shcmd (113): mkdir -p /mnt/cache Jun 10 20:00:56 jbox emhttp: shcmd (114): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdb1 /mnt/cache |& logger Jun 10 20:00:56 jbox kernel: BTRFS info (device sdb1): disk space caching is enabled Jun 10 20:00:56 jbox kernel: BTRFS info (device sdb1): has skinny extents Jun 10 20:00:56 jbox kernel: BTRFS info (device sdb1): detected SSD devices, enabling SSD mode Jun 10 20:00:56 jbox emhttp: shcmd (115): sync
  3. I just did a fresh install with the dev branch and within a couple of minutes everything was installed and it was fired up. Here's what I see in my log: First install detected, cloning repository Using the dev branch Branch dev set up to track remote branch dev from origin. npm-container: updating npm dependencies -- git-rev-sync... Sep 23 14:09:46 cc54b1595e56 syslog-ng[123]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. => Meteor 1.2.0.1: React and Angular support, ECMAScript 2015, new faster build system, and improvements to the Cordova integration for mobile apps. This release is being downloaded in the background. Update your app to Meteor 1.2.0.1 by running 'meteor update'. => Started MongoDB. => Started your app. => App running at: http://localhost:3000/ [34mI20150923-14:10:02.876(-4) (percolate_synced-cron.js:85) [39mSyncedCron: Scheduled "Update CP download status" next run @Wed Sep 23 2015 18:00:00 GMT-0400 (EDT) See in the log where it says "Started your app" under "Started MongoDB". Do you not get that message? Could you perhaps be trying to use a port that is already being used by something else? Yeah i dont seem to get that message. Or the 'app running at'. However i do get the cronjobs all firing off successfully. I've tried reinstalling to a different location - And that works fine, so it seems that somethngs gone wrong with the DB thats stopping it from launching. Any ideas on what i can do? PITA having to set it all up again so trying to avoid that if possible
  4. I've tried all the different branches incase that was causing the issue - Is it the fact meteor seems to have an update? Not sure what to do at this point. The log seems fine. After starting the mongodb, it will take another 10-20 second to start the app (may be longer but that's how long it takes for me). Did you wait long enough? Does it give an error later? Meteor update should not have an effect. I tested it again and it will download the update in the background and then it will keep saying the update is ready to be applied. You can leave it as is and it is harmless. Unfortunately, the update is not compatible with plexrequests at the moment so just leave it as is. In my case (I tried the master branch) it works just fine once the app loads. I also installed from scratch and again it worked fine. I'll try other branches later to see if they cause any issues. Hmm.. I have left it running for days, and it still doesn't work. Afterwards it just says the cron.hourly logs so it all seems to 'think' its running fine. Is there a log file somewhere i could check besides the one found in the docker page of unraid? Looking through the apps files i don't see one
  5. Is there an issue with the plexRequests docker recently? Last few days it doesn't seem to work at all. Tried re-installing it several times. Log seems to do this I've tried all the different branches incase that was causing the issue - Is it the fact meteor seems to have an update? Not sure what to do at this point.
  6. I can't seem to get the files to get onto my cache drive. I've set the folder /MCMA2_Linux_x86_64 to my cache drive, but nothing goes inside it. What can i do to make these persist stopping and starting?
  7. I've had no luck with it and just had to give up using sensors on my motherboard
  8. Hi all, i've been having this problem for a while (Ever since moving cases and adding another controller card to my mobo) Every so often my parity disk will fail to write and get disabled by unraid. Sometimes when i boot up all the drives connected to a card will all error, sometimes it will last for an hour or so, then they slowly start to error. Now i've got it down to a few days, however eventually it seems a drive (Usually parity as obviously its most used) will error. I've attatched the bit of the syslog below. The drive when active has 0 health problems and runs fine. However i keep reseating the card into the port however im running out of ideas as to why the card seems to temporarily lose connection. The cards are an aoc-sas2lp-mv8 and aoc-saslp-mv8. I believe it is the newer sas2 card that keeps giving way, although i have had the other card do the same thing, but this is normally noticeable on bootup, so its apparent instantly when there is an issue. All the hard drives are in a backplane, ive tried moving the drives around and dont think the backplane has anything to do with it, am almost convinced its the card just temporarily 'losing connection' What type of things should i check for? Mar 24 10:21:31 jbox kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Mar 24 10:21:31 jbox kernel: sas: ata7: end_device-1:0: cmd error handler Mar 24 10:21:31 jbox kernel: sas: ata7: end_device-1:0: dev error handler Mar 24 10:21:31 jbox kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 24 10:21:31 jbox kernel: ata7.00: failed command: READ DMA EXT Mar 24 10:21:31 jbox kernel: ata7.00: cmd 25/00:00:b8:0a:d7/00:02:cc:01:00/e0 tag 19 dma 262144 in Mar 24 10:21:31 jbox kernel: res 51/40:00:c8:0a:d7/00:02:cc:01:00/e0 Emask 0x9 (media error) Mar 24 10:21:31 jbox kernel: ata7.00: status: { DRDY ERR } Mar 24 10:21:31 jbox kernel: ata7.00: error: { UNC } Mar 24 10:21:31 jbox kernel: sas: ata8: end_device-1:1: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata9: end_device-1:2: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata10: end_device-1:3: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata11: end_device-1:4: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata12: end_device-1:5: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata13: end_device-1:6: dev error handler Mar 24 10:21:31 jbox kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x1) Mar 24 10:21:31 jbox kernel: ata7.00: revalidation failed (errno=-5) Mar 24 10:21:31 jbox kernel: ata7: hard resetting link Mar 24 10:21:31 jbox kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x1) Mar 24 10:21:31 jbox kernel: ata7.00: revalidation failed (errno=-5) Mar 24 10:21:36 jbox kernel: ata7: hard resetting link Mar 24 10:21:37 jbox kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x1) Mar 24 10:21:37 jbox kernel: ata7.00: revalidation failed (errno=-5) Mar 24 10:21:37 jbox kernel: ata7.00: disabled Mar 24 10:21:37 jbox kernel: sd 1:0:0:0: [sdc] Mar 24 10:21:37 jbox kernel: Result: hostbyte=0x00 driverbyte=0x08 Mar 24 10:21:37 jbox kernel: sd 1:0:0:0: [sdc] Mar 24 10:21:37 jbox kernel: Sense Key : 0x3 [current] [descriptor] Mar 24 10:21:37 jbox kernel: Descriptor sense data with sense descriptors (in hex): Mar 24 10:21:37 jbox kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 01 Mar 24 10:21:37 jbox kernel: cc d7 0a c8 Mar 24 10:21:37 jbox kernel: sd 1:0:0:0: [sdc] Mar 24 10:21:37 jbox kernel: ASC=0x11 ASCQ=0x4 Mar 24 10:21:37 jbox kernel: sd 1:0:0:0: [sdc] CDB: Mar 24 10:21:37 jbox kernel: cdb[0]=0x88: 88 00 00 00 00 01 cc d7 0a b8 00 00 02 00 00 00 Mar 24 10:21:37 jbox kernel: blk_update_request: I/O error, dev sdc, sector 7731612360 Mar 24 10:21:37 jbox kernel: ata7: EH complete Mar 24 10:21:37 jbox kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Mar 24 10:21:37 jbox kernel: md: disk0 read error, sector=7731612296 Mar 24 10:21:37 jbox kernel: md: disk0 read error, sector=7731612304 Mar 24 10:21:37 jbox kernel: md: disk0 read error, sector=7731612312 Mar 24 10:21:37 jbox kernel: md: disk0 read error, sector=7731612320 log.zip
  9. So the fan script for me detects 4 PWM controllers, and i have 5 PWM fan ports. CPU Fan on Fan1, backplane on ports 2~4. However no matter what i do with the PWM controller, or with the PWM fan setting (No matter which pwm controller is selected ,it always detects /sys/devices/platform/w83627ehf.2576/fan1_input) it just sets all of the fans to slow down (Inluding my CPU fan!). What am i doing wrong?
  10. Working for me on v6b14, thank you very much.
  11. This link sadly goes to a 404 not found when you try to download the file. Can you throw it up on github if possible
  12. I also need this. Could someone perhaps host it on a google drive somewhere or any other free upload service.
  13. This is not a driver malfunction. When the Auto Fan tries to stop the fan, the IPMI interface will briefly sound an alarm, then will reset the PWM interface to met it's lower threshold. See were how to change the IPMI thresholds : https://forums.freenas.org/index.php?threads/how-to-change-sensor-thresholds-with-ipmi-using-ipmitool.23571/ To load the correct ipmi driver, use modprobe ipmi_devintf instead of "kldload ipmi.ko". I recommend you to use FANA to control the fans, since FAN1-4 are controlled in block using the CPU temperature as parameter. Hi thanks for the reply! Much appreciated. But the fans have been sounding the alarm from before i used the AutoFan script (Infact i only got the script to work today, as i saw bergware had made an update which let it recognize the fans, as before it would just show 'None' in the PWM controller) Also how do i stop unraid from using "kldload ipmi.ko" (I'm in way over my head when it comes to hardware stuff ), or do you mean when following the link to use ipmitool, in which case i understand, but how do i stop the IPMI web interface from seeing the wrong RPMs? And finally, what do you mean by 'use FANA to control the fans' As far as im aware there is just ports 1-5 on the board? (or is FanA Fan5? Connected directly to PSU?) Sorry! Gets confusing 1) If you follow the tutorial from the link, you have to change "kldload ipmi.ko" to "modprobe ipmi_devintf". 2) I think it's marked FAN_A in the motherboard, and, in my case (X9SCM-F), it's fan1 in "sensors". The Auto Fan should auto detect it for you. I can't seem to find any reference in the manual to a FAN_A (or on the motherboard itself) just Fan1 ~ Fan5. Also no reference to Fan1~4 being controlled in block with the CPU - although maybe that's just not in the manual i don't know. Also i feel i should mention, incase it sheds some light on things the 'auto fan script' as-is doesn't currently detect anything for me. I had to manually edit it to bergwares github version updated 12 days ago. Still just a bit confused as to why when the driver is loaded into unraid the IPMI device sees crazy RPM values (Even without the auto fan script installed it was doing this) Sorry for the constant questions! Just happy to have somebody that knows what they're talking about answering!
  14. This is not a driver malfunction. When the Auto Fan tries to stop the fan, the IPMI interface will briefly sound an alarm, then will reset the PWM interface to met it's lower threshold. See were how to change the IPMI thresholds : https://forums.freenas.org/index.php?threads/how-to-change-sensor-thresholds-with-ipmi-using-ipmitool.23571/ To load the correct ipmi driver, use modprobe ipmi_devintf instead of "kldload ipmi.ko". I recommend you to use FANA to control the fans, since FAN1-4 are controlled in block using the CPU temperature as parameter. Hi thanks for the reply! Much appreciated. But the fans have been sounding the alarm from before i used the AutoFan script (Infact i only got the script to work today, as i saw bergware had made an update which let it recognize the fans, as before it would just show 'None' in the PWM controller) Also how do i stop unraid from using "kldload ipmi.ko" (I'm in way over my head when it comes to hardware stuff ), or do you mean when following the link to use ipmitool, in which case i understand, but how do i stop the IPMI web interface from seeing the wrong RPMs? And finally, what do you mean by 'use FANA to control the fans' As far as im aware there is just ports 1-5 on the board? (or is FanA Fan5? Connected directly to PSU?) Sorry! Gets confusing
  15. Unraid OS: 6.0.14b using X8SIL-F supermicro mobo Problem My case has been having intermittent alarms for a while now, and the IPMI interface shows the fans RPMs as absurdly wrong after a few minutes of the server being on (saw 560000RPM at one point, and it flickers to 0 for a second or two Causing the alarm) i finally noticed it is due to the dynamix plugins loading the w83627ehf sensor using modprobe. Once i removed this plugin i started the server off and left it for 8 hours, IPMI sensors still showing correctly, no alarms or errors. Then i used modprobe w83627ehf in console, and within 2 minutes the fans RPMs were displaying wrong, and a port that isn't even plugged in, had been detected briefly as 0 RPMs and alarmed. I'm not sure if this is something that can be fixed by you, or perhaps its something wrong on my end, but it all seems to point to the driver to me, i can of course do without it, but controlling my fans speed would be nice! (3000RPM fans at full speed makes the SO quite mad whenever she enters the room with my servers in ) How to reproduce: modprobe w83627ehf on X8SIL-F board Expected results: fans continue working normally - able to set RPM correctly Actual results: fans IPMI RPMs fail, fans slightly unresponsive Other information: Mar 20 14:29:56 jbox autofan: Highest disk temp is 32°C, adjusting fan speed from: FULL (100% @ 2812rpm) to: OFF (0% @ 2766rpm) Mar 20 14:30:23 jbox autofan: killing autofan process 15348 Mar 20 14:30:23 jbox php: /etc/rc.d/rc.autofan start >/dev/null Mar 20 14:30:23 jbox autofan: autofan process ID 16851 started, To terminate it, type: autofan -q Mar 20 14:30:32 jbox autofan: Highest disk temp is 32°C, adjusting fan speed from: FULL (100% @ 2812rpm) to: OFF (0% @ 0rpm) Mar 20 14:30:51 jbox autofan: killing autofan process 16851 Mar 20 14:30:51 jbox php: /etc/rc.d/rc.autofan start >/dev/null Mar 20 14:30:51 jbox autofan: autofan process ID 18058 started, To terminate it, type: autofan -q Mar 20 14:30:51 jbox kernel: w83627ehf w83627ehf.2576: fan2 low limit and alarm disabled Mar 20 14:30:58 jbox autofan: Highest disk temp is 32°C, adjusting fan speed from: FULL (100% @ 2083rpm) to: OFF (0% @ 2008rpm) Whilst the autofan script was running this is the type of thing that would happen every time it was applied. (see 100% RPMs change and 0% rpms change within the same minute) NB: The alarms were happening before the autofan script was installed, i believe it was since the dynamix system temp plugin was installed, which to my knowledge only loads the drivers and doesnt try to 'write' any information to the hw so i dont believe this is the autofan script causing the error (Although i've been wrong plenty of times! ) However i never had a case of this happening prior to V6 of unraid (The alarms) - But i suspect this is due to the fact i never had any sensor detection happening prior to V6