Frank1940 Posted July 16, 2016 Share Posted July 16, 2016 Anybody else seeing loads of XFS errors since this update? My log is filled with constant errors shown below. I/O errors on Windows based machines trying to write to the array aswell "Jul 16 12:00:58 AVALON kernel: XFS (md3): xfs_log_force: error -5 returned." I would suggest that you follow the request (see first post in this thread) to attach your Diagnostics file to your post if you want a definite diagnoses. Your description is most likely the result of the problem and not the cause of the actual problem. Link to comment
Kuroyukihimeeee Posted July 16, 2016 Share Posted July 16, 2016 Anybody else seeing loads of XFS errors since this update? My log is filled with constant errors shown below. I/O errors on Windows based machines trying to write to the array aswell "Jul 16 12:00:58 AVALON kernel: XFS (md3): xfs_log_force: error -5 returned." I would suggest that you follow the request (see first post in this thread) to attach your Diagnostics file to your post if you want a definite diagnoses. Your description is most likely the result of the problem and not the cause of the actual problem. Diag attached. Was more posting to see if this was just a know issue others are experiencing avalon-diagnostics-20160716-1447.zip Link to comment
nexusmaniac Posted July 16, 2016 Share Posted July 16, 2016 Strange... Jul 16 18:35:27 Raptor root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Jul 16 18:35:29 Raptor root: Jul 16 18:35:29 Raptor root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Jul 16 18:35:29 Raptor root: Jul 16 18:35:29 Raptor root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Jul 16 18:35:32 Raptor kernel: fat__get_entry: 102 callbacks suppressed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:37 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:39 Raptor emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sda Jul 16 18:35:43 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:48 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:53 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:58 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:36:01 Raptor root: Jul 16 18:36:01 Raptor root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Jul 16 18:36:01 Raptor root: Jul 16 18:36:01 Raptor root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Jul 16 18:36:03 Raptor kernel: fat__get_entry: 102 callbacks suppressed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:36:08 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:36:10 Raptor kernel: usb 4-1: USB disconnect, device number 3 Jul 16 18:36:14 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed System's been up for about 30 mins now, my webUI went white instead of black and that's filling the boot USB logs Got some general errors floating around the web pages: Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 38 Fatal error: Uncaught exception 'UnexpectedValueException' with message 'RecursiveDirectoryIterator::__construct(/boot/config/plugins/dockerMan/templates-user): failed to open dir: No such file or directory' in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:62 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(62): RecursiveDirectoryIterator->__construct('/boot/config/pl...', 4096) #1 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(91): DockerTemplates->listDir('/boot/config/pl...', 'xml') #2 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(220): DockerTemplates->getTemplates('all') #3 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(329): DockerTemplates->getTemplateValue('linuxserver/ope...', 'Registry') #4 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(300) : eval()'d code(70): DockerTemplates->getAllInfo() #5 /usr/local/emhttp/plugins/dynamix/include/DefaultPage in Everything seems a bit off Diagnostics attached USB is decent, 16GB Sandisk Ultra Fit --- Rebooted and everything went back to normal. But it can't be good --- raptor-diagnostics-20160716-1837.zip Link to comment
Kuroyukihimeeee Posted July 16, 2016 Share Posted July 16, 2016 Anybody else seeing loads of XFS errors since this update? My log is filled with constant errors shown below. I/O errors on Windows based machines trying to write to the array aswell "Jul 16 12:00:58 AVALON kernel: XFS (md3): xfs_log_force: error -5 returned." my experience is that this normally means the disk has dropped offline. You were right All disks were showing as active but an entire disk worth of files was just missing. Rebooted array and it came back, but im going to keep a close eye on it now All SMART tests come back clear, drives are 3-4 months old yet an entire drive dropped without unraid even noticing... I kept logs open and watch Plex as normal, about 10 mins after booting array this kicks in with red. Jul 16 19:46:44 AVALON kernel: XFS (md3): Internal error XFS_WANT_CORRUPTED_GOTO at line 1635 of file fs/xfs/libxfs/xfs_alloc.c. Caller xfs_alloc_fix_freelist+0x155/0x2de Jul 16 19:46:44 AVALON kernel: CPU: 7 PID: 22360 Comm: kworker/u34:7 Tainted: G IO 4.4.15-unRAID #1 Jul 16 19:46:44 AVALON kernel: Hardware name: FUJITSU CELSIUS R570-2 /D2628-C1, BIOS 6.00 R1.22.2628.C1 12/19/2011 Jul 16 19:46:44 AVALON kernel: Workqueue: writeback wb_workfn (flush-9:3) Jul 16 19:46:44 AVALON kernel: 0000000000000000 ffff88050f8cb480 ffffffff81369dfe ffff8804ea7f8000 Jul 16 19:46:44 AVALON kernel: 0000000000000001 ffff88050f8cb498 ffffffff81274baa ffffffff812457e0 Jul 16 19:46:44 AVALON kernel: ffff88050f8cb510 ffffffff81244eb1 0000000300000001 ffff8801ad7ec780 Jul 16 19:46:44 AVALON kernel: Call Trace: Jul 16 19:46:44 AVALON kernel: [<ffffffff81369dfe>] dump_stack+0x61/0x7e Jul 16 19:46:44 AVALON kernel: [<ffffffff81274baa>] xfs_error_report+0x32/0x35 Jul 16 19:46:44 AVALON kernel: [<ffffffff812457e0>] ? xfs_alloc_fix_freelist+0x155/0x2de Jul 16 19:46:44 AVALON kernel: [<ffffffff81244eb1>] xfs_free_ag_extent+0x13d/0x558 Jul 16 19:46:44 AVALON kernel: [<ffffffff81243ee2>] ? xfs_alloc_get_freelist+0x135/0x14d Jul 16 19:46:44 AVALON kernel: [<ffffffff812457e0>] xfs_alloc_fix_freelist+0x155/0x2de Jul 16 19:46:44 AVALON kernel: [<ffffffff8126b1cd>] ? xfs_perag_get+0x3a/0x44 Jul 16 19:46:44 AVALON kernel: [<ffffffff81245bb2>] xfs_alloc_vextent+0x249/0x3a3 Jul 16 19:46:44 AVALON kernel: [<ffffffff81251251>] xfs_bmap_btalloc+0x3c8/0x598 Jul 16 19:46:44 AVALON kernel: [<ffffffff8125142a>] xfs_bmap_alloc+0x9/0xb Jul 16 19:46:44 AVALON kernel: [<ffffffff81251cbe>] xfs_bmapi_write+0x40e/0x80f Jul 16 19:46:44 AVALON kernel: [<ffffffff8127cd9d>] xfs_iomap_write_allocate+0x1c1/0x2bd Jul 16 19:46:44 AVALON kernel: [<ffffffff8126dc40>] xfs_map_blocks+0x134/0x143 Jul 16 19:46:44 AVALON kernel: [<ffffffff8126e8e7>] xfs_vm_writepage+0x287/0x483 Jul 16 19:46:44 AVALON kernel: [<ffffffff810c0eb2>] __writepage+0xe/0x26 Jul 16 19:46:44 AVALON kernel: [<ffffffff810c1372>] write_cache_pages+0x249/0x351 Jul 16 19:46:44 AVALON kernel: [<ffffffff810c0ea4>] ? mapping_tagged+0xf/0xf Jul 16 19:46:44 AVALON kernel: [<ffffffff810c14c2>] generic_writepages+0x48/0x67 Jul 16 19:46:44 AVALON kernel: [<ffffffff8137a240>] ? find_next_bit+0x15/0x1b Jul 16 19:46:44 AVALON kernel: [<ffffffff8136a14d>] ? fprop_fraction_percpu+0x32/0x72 Jul 16 19:46:44 AVALON kernel: [<ffffffff8126daef>] xfs_vm_writepages+0x3f/0x47 Jul 16 19:46:44 AVALON kernel: [<ffffffff8126daef>] ? xfs_vm_writepages+0x3f/0x47 Jul 16 19:46:44 AVALON kernel: [<ffffffff810c2e31>] do_writepages+0x1b/0x24 Jul 16 19:46:44 AVALON kernel: [<ffffffff81129a8f>] __writeback_single_inode+0x3d/0x151 Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a044>] writeback_sb_inodes+0x20d/0x3ad Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a255>] __writeback_inodes_wb+0x71/0xa9 Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a43b>] wb_writeback+0x10b/0x195 Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a984>] wb_workfn+0x18e/0x22b Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a984>] ? wb_workfn+0x18e/0x22b Jul 16 19:46:44 AVALON kernel: [<ffffffff8105acd4>] process_one_work+0x194/0x2a0 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105b68a>] worker_thread+0x26b/0x353 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105b41f>] ? rescuer_thread+0x285/0x285 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105f910>] kthread+0xcd/0xd5 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105f843>] ? kthread_worker_fn+0x137/0x137 Jul 16 19:46:44 AVALON kernel: [<ffffffff816232bf>] ret_from_fork+0x3f/0x70 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105f843>] ? kthread_worker_fn+0x137/0x137 Jul 16 19:46:44 AVALON kernel: XFS (md3): Internal error xfs_trans_cancel at line 990 of file fs/xfs/xfs_trans.c. Caller xfs_iomap_write_allocate+0x298/0x2bd Jul 16 19:46:44 AVALON kernel: CPU: 7 PID: 22360 Comm: kworker/u34:7 Tainted: G IO 4.4.15-unRAID #1 Jul 16 19:46:44 AVALON kernel: Hardware name: FUJITSU CELSIUS R570-2 /D2628-C1, BIOS 6.00 R1.22.2628.C1 12/19/2011 Jul 16 19:46:44 AVALON kernel: Workqueue: writeback wb_workfn (flush-9:3) Jul 16 19:46:44 AVALON kernel: 0000000000000000 ffff88050f8cb820 ffffffff81369dfe ffff8804ba061790 Jul 16 19:46:44 AVALON kernel: 0000000000000101 ffff88050f8cb838 ffffffff81274baa ffffffff8127ce74 Jul 16 19:46:44 AVALON kernel: ffff88050f8cb860 ffffffff81288dc0 ffff8800cc6ef800 0000000000053e82 Jul 16 19:46:44 AVALON kernel: Call Trace: Jul 16 19:46:44 AVALON kernel: [<ffffffff81369dfe>] dump_stack+0x61/0x7e Jul 16 19:46:44 AVALON kernel: [<ffffffff81274baa>] xfs_error_report+0x32/0x35 Jul 16 19:46:44 AVALON kernel: [<ffffffff8127ce74>] ? xfs_iomap_write_allocate+0x298/0x2bd Jul 16 19:46:44 AVALON kernel: [<ffffffff81288dc0>] xfs_trans_cancel+0x49/0xbf Jul 16 19:46:44 AVALON kernel: [<ffffffff8127ce74>] xfs_iomap_write_allocate+0x298/0x2bd Jul 16 19:46:44 AVALON kernel: [<ffffffff8126dc40>] xfs_map_blocks+0x134/0x143 Jul 16 19:46:44 AVALON kernel: [<ffffffff8126e8e7>] xfs_vm_writepage+0x287/0x483 Jul 16 19:46:44 AVALON kernel: [<ffffffff810c0eb2>] __writepage+0xe/0x26 Jul 16 19:46:44 AVALON kernel: [<ffffffff810c1372>] write_cache_pages+0x249/0x351 Jul 16 19:46:44 AVALON kernel: [<ffffffff810c0ea4>] ? mapping_tagged+0xf/0xf Jul 16 19:46:44 AVALON kernel: [<ffffffff810c14c2>] generic_writepages+0x48/0x67 Jul 16 19:46:44 AVALON kernel: [<ffffffff8137a240>] ? find_next_bit+0x15/0x1b Jul 16 19:46:44 AVALON kernel: [<ffffffff8136a14d>] ? fprop_fraction_percpu+0x32/0x72 Jul 16 19:46:44 AVALON kernel: [<ffffffff8126daef>] xfs_vm_writepages+0x3f/0x47 Jul 16 19:46:44 AVALON kernel: [<ffffffff8126daef>] ? xfs_vm_writepages+0x3f/0x47 Jul 16 19:46:44 AVALON kernel: [<ffffffff810c2e31>] do_writepages+0x1b/0x24 Jul 16 19:46:44 AVALON kernel: [<ffffffff81129a8f>] __writeback_single_inode+0x3d/0x151 Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a044>] writeback_sb_inodes+0x20d/0x3ad Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a255>] __writeback_inodes_wb+0x71/0xa9 Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a43b>] wb_writeback+0x10b/0x195 Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a984>] wb_workfn+0x18e/0x22b Jul 16 19:46:44 AVALON kernel: [<ffffffff8112a984>] ? wb_workfn+0x18e/0x22b Jul 16 19:46:44 AVALON kernel: [<ffffffff8105acd4>] process_one_work+0x194/0x2a0 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105b68a>] worker_thread+0x26b/0x353 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105b41f>] ? rescuer_thread+0x285/0x285 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105f910>] kthread+0xcd/0xd5 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105f843>] ? kthread_worker_fn+0x137/0x137 Jul 16 19:46:44 AVALON kernel: [<ffffffff816232bf>] ret_from_fork+0x3f/0x70 Jul 16 19:46:44 AVALON kernel: [<ffffffff8105f843>] ? kthread_worker_fn+0x137/0x137 Jul 16 19:46:44 AVALON kernel: XFS (md3): xfs_do_force_shutdown(0x8) called from line 991 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff81288dd9 Jul 16 19:46:44 AVALON kernel: XFS (md3): Corruption of in-memory data detected. Shutting down filesystem Jul 16 19:46:44 AVALON kernel: XFS (md3): Please umount the filesystem and rectify the problem(s) Jul 16 19:46:44 AVALON shfs/user0: shfs_read: read: (5) Input/output error Jul 16 19:46:44 AVALON shfs/user0: shfs_read: read: (5) Input/output error Jul 16 19:46:44 AVALON shfs/user0: shfs_read: read: (5) Input/output error Jul 16 19:46:44 AVALON shfs/user0: shfs_read: read: (5) Input/output error Jul 16 19:46:44 AVALON shfs/user0: shfs_read: read: (5) Input/output error Jul 16 19:46:44 AVALON shfs/user0: shfs_read: read: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Jul 16 19:46:45 AVALON shfs/user0: shfs_write: write: (5) Input/output error Going to run memtest now. Seems to be RAM related Link to comment
Squid Posted July 16, 2016 Share Posted July 16, 2016 Strange... Jul 16 18:35:27 Raptor root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Jul 16 18:35:29 Raptor root: Jul 16 18:35:29 Raptor root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Jul 16 18:35:29 Raptor root: Jul 16 18:35:29 Raptor root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Jul 16 18:35:32 Raptor kernel: fat__get_entry: 102 callbacks suppressed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:32 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:37 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:37 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:39 Raptor emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sda Jul 16 18:35:43 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:43 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:48 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:48 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:53 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:53 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:35:58 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:35:58 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:36:01 Raptor root: Jul 16 18:36:01 Raptor root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Jul 16 18:36:01 Raptor root: Jul 16 18:36:01 Raptor root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Jul 16 18:36:03 Raptor kernel: fat__get_entry: 102 callbacks suppressed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:36:03 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:36:08 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed Jul 16 18:36:08 Raptor kernel: FAT-fs (sda1): Directory bread(block 32777) failed Jul 16 18:36:10 Raptor kernel: usb 4-1: USB disconnect, device number 3 Jul 16 18:36:14 Raptor kernel: fat__get_entry: 70 callbacks suppressed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32768) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32769) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32770) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32771) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32772) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32773) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32774) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32775) failed Jul 16 18:36:14 Raptor kernel: FAT-fs (sda1): Directory bread(block 32776) failed System's been up for about 30 mins now, my webUI went white instead of black and that's filling the boot USB logs Got some general errors floating around the web pages: Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 38 Fatal error: Uncaught exception 'UnexpectedValueException' with message 'RecursiveDirectoryIterator::__construct(/boot/config/plugins/dockerMan/templates-user): failed to open dir: No such file or directory' in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:62 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(62): RecursiveDirectoryIterator->__construct('/boot/config/pl...', 4096) #1 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(91): DockerTemplates->listDir('/boot/config/pl...', 'xml') #2 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(220): DockerTemplates->getTemplates('all') #3 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(329): DockerTemplates->getTemplateValue('linuxserver/ope...', 'Registry') #4 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(300) : eval()'d code(70): DockerTemplates->getAllInfo() #5 /usr/local/emhttp/plugins/dynamix/include/DefaultPage in Everything seems a bit off Diagnostics attached USB is decent, 16GB Sandisk Ultra Fit --- Rebooted and everything went back to normal. But it can't be good --- Try a different USB port (ideally on a different controller -> ie: if the flash is in a USB 3, try it in a USB2 etc) The system lost track of the flash drive. Quite often port related (and not flash related) Link to comment
JayTreDoe Posted July 16, 2016 Share Posted July 16, 2016 Has anyone else's VM's performance tanked since rc1 and rc2? Link to comment
rick.p Posted July 16, 2016 Share Posted July 16, 2016 anyone else having problems with the plugin's tab? Just sits there and hangs on 'Please wait, retrieving plugin information ...' and "Check for Updates" just give a blank box Link to comment
ljm42 Posted July 17, 2016 Share Posted July 17, 2016 - docker: fix populate variable descriptions for v1 templates I just upgraded from 6.2rc1 to rc2 and I see no evidence of this fix, everything looks the same as it did in rc1: https://lime-technology.com/forum/index.php?topic=50240.msg482644#msg482644 Is that because my templates have already been upgraded from v1 to v2? If so, what do I need to do manually to bring them in sync? I ended up hitting EDIT, then SAVE for each variable on each docker. This set a usable description for each one. I still don't understand why we have a "name" of "Key 1" instead of just calling it "PUID" though. Link to comment
Squid Posted July 17, 2016 Share Posted July 17, 2016 I still don't understand why we have a "name" of "Key 1" instead of just calling it "PUID" though. Yeah probably would make sense when dockerMan converts a v1 template to have the Name match the description. Link to comment
dikkiedirk Posted July 17, 2016 Share Posted July 17, 2016 Is preclear no longer working? I just upgraded a 6.1.9 machine to 6.2.0 RC2 and found that I get get a disk is busy error. All disks are attached to LSI SAS 2008 controllers. After downgrading to 6.1.9 preclear works again. Link to comment
Helmonder Posted July 17, 2016 Share Posted July 17, 2016 there is a new preclear script that should be used with 6.2 http://lime-technology.com/forum/index.php?topic=39985.510 Link to comment
hawihoney Posted July 17, 2016 Share Posted July 17, 2016 there is a new preclear script that should be used with 6.2 The original thread does not mention a new script. Where did you find it, where did you read about it. TIA Link to comment
Helmonder Posted July 17, 2016 Share Posted July 17, 2016 http://lime-technology.com/forum/index.php?topic=39985.510 Link to comment
NAS Posted July 17, 2016 Share Posted July 17, 2016 there is a new preclear script that should be used with 6.2 http://lime-technology.com/forum/index.php?topic=39985.510 This needs added to the changelog. Most users dont read the forum and certainly not page 35 of a 50 page thread Link to comment
Helmonder Posted July 17, 2016 Share Posted July 17, 2016 Not really.. Preclear is at best a plugin and no part of unraid itself. The changelog focusses in unraid, not on plugins.. Verzonden vanaf mijn iPhone met Tapatalk Link to comment
NAS Posted July 17, 2016 Share Posted July 17, 2016 Normally I would agree however not this time. Preclear has been a cornerstone of unRAID community for years now. If an unRAID release breaks something used by so many users should be informed. Its just the right thing to do for the community. Link to comment
Squid Posted July 17, 2016 Share Posted July 17, 2016 Normally I would agree however not this time. Preclear has been a cornerstone of unRAID community for years now. If an unRAID release breaks something used by so many users should be informed. Its just the right thing to do for the community. Compatibility issues are not the problem of LT. Rather gfjardim should include in the template for Preclear the minimum version and maximum version tags (to prevent new users from installing the incorrect version) and additionally have a version test at installation to prevent installation on incompatibile systems (so that upgrading users would not have any issues as they would then be forced to reinstall the correct version through CA) Link to comment
garycase Posted July 17, 2016 Share Posted July 17, 2016 The need for a newer version of the pre-clear script is NOT a change to UnRAID ... I agree it doesn't belong in the changelog. However, burying it 35-pages into the discussion thread on the preclear plugin is also not a good idea. I'd think the best approach is for gfjardim to edit the first post in his thread to note that a newer version of the script is required for v6.2 and should provide a link to that version in that initial post. Link to comment
bonienl Posted July 17, 2016 Share Posted July 17, 2016 As mentioned by squid, unRAID 6.2 supports version tagging in the PLG file. It is recommended for plugin developers to use these in order to do proper plugin installation depending on the unRAID version in use. Link to comment
Frank1940 Posted July 17, 2016 Share Posted July 17, 2016 Is preclear no longer working? I just upgraded a 6.1.9 machine to 6.2.0 RC2 and found that I get get a disk is busy error. All disks are attached to LSI SAS 2008 controllers. After downgrading to 6.1.9 preclear works again. Joe L. has provided instructions on how to modify the original preclear script to make it work with version 6.2. You can find it here: http://lime-technology.com/forum/index.php?topic=13054.msg464653#msg464653 After I did that, I precleared a 3TB WD Red without an issue using the original preclear plugin (Not the preclear.beta plugin). IF you are confused about the various scripts and preclear plugins, you can see this post: http://lime-technology.com/forum/index.php?topic=39985.msg477858#msg477858 And the next few pages of that thread. I know that many people are confused by the whole issue as there are TWO preclear scripts (Joe L.'s script and the 'faster' one) and TWO Preclear Plugins (The Original Preclear Plugin and the Preclear.beta Plugin) . The PreClear Plugins are actually contained and discussed in the same thread. It takes some reading and study to get everything straight in one's head! Link to comment
Squid Posted July 17, 2016 Share Posted July 17, 2016 Is preclear no longer working? I just upgraded a 6.1.9 machine to 6.2.0 RC2 and found that I get get a disk is busy error. All disks are attached to LSI SAS 2008 controllers. After downgrading to 6.1.9 preclear works again. Joe L. has provided instructions on how to modify the original preclear script to make it work with version 6.2. You can find it here: http://lime-technology.com/forum/index.php?topic=13054.msg464653#msg464653 After I did that, I precleared a 3TB WD Red without an issue using the original preclear plugin (Not the preclear.beta plugin). IF you are confused about the various scripts and preclear plugins, you can see this post: http://lime-technology.com/forum/index.php?topic=39985.msg477858#msg477858 And the next few pages of that thread. I know that many people are confused by the whole issue as there are TWO preclear scripts (Joe L.'s script and the 'faster' one) and TWO Preclear Plugins (The Original Preclear Plugin and the Preclear.beta Plugin) . The PreClear Plugins are actually contained and discussed in the same thread. It takes some reading and study to get everything straight in one's head! But the point remains the same. Preclear should not install under 6.2 (nor should it appear within CA). Preclear Beta should install (and be the only version to appear in CA) when running 6.2. And if the plg's and the xml's were set up correctly this would indeed happen (and additionally FCP would also notify users about attempts to have incompatible Preclears plugins attempting to install) A user shouldn't have to jump through the hoops to get Preclear to work (or wonder why it doesn't). The problem is only going to get worse as 6.2 gets even closer (and hits) final stage and more people upgrade. Link to comment
garycase Posted July 17, 2016 Share Posted July 17, 2016 A few thoughts relevant to the pre-clear discussion ... (a) Historically, the reason JoeL developed the script was to eliminate the hours of downtime in an array when a new disk was added; as it would be off-line for the entire time it was zeroing a new disk. (b) Rather than simply zero the disk and add a pre-clear signature (which Tom was kind enough to share with JoeL to enable the script in the first place); Joe did a few additional tests to provide a bit of an initial "burn in" on the disk ... i.e. the pre-read and post-read phases. © Clearly the pre-clear script became the "standard" way of both testing and clearing new disks ... and many folks used it to test new disks that didn't require clearing [i.e. disks that were going to be replacements or new parity disks ... not new additions to the array]. Now, with v6.2, there is NO need to pre-clear a disk to do what point (a) noted, as there is no downtime when you add a new disk ... UnRAID handles the clearing and subsequent adding to the array without the previous off-line requirement. So the only real function pre-clear now provides is a bit of an initial test of the disk. Still a valuable feature; and certainly many prefer to have this one on their UnRAID server; BUT without the pre-clear requirement, this function can easily be done on any other PC you may have BEFORE you even bother to add the drive to your server. e.g. I've long done all my actual testing on a PC by simply connecting a new drive to an eSATA port and then running WD's Data Lifeguard to several rounds of tests. There are other equally good testing utilities -- Seagate's SeaTools; Crystal Disk; HDTune; etc. and a few others. If you have a dedicated PC you can use for testing and want to do a REALLY thorough test you can use SpinRite or HDD Regenerator ... but this level of testing really isn't needed and will take a VERY long time to do with modern drive sizes. [i used to do that as well, but don't anymore] Bottom line: The primary "clearing" function of the pre-clear script is simply not needed with v6.2 => so the pre-clear script is far less important than it used to be. Link to comment
Frank1940 Posted July 17, 2016 Share Posted July 17, 2016 Is preclear no longer working? I just upgraded a 6.1.9 machine to 6.2.0 RC2 and found that I get get a disk is busy error. All disks are attached to LSI SAS 2008 controllers. After downgrading to 6.1.9 preclear works again. Joe L. has provided instructions on how to modify the original preclear script to make it work with version 6.2. You can find it here: http://lime-technology.com/forum/index.php?topic=13054.msg464653#msg464653 After I did that, I precleared a 3TB WD Red without an issue using the original preclear plugin (Not the preclear.beta plugin). IF you are confused about the various scripts and preclear plugins, you can see this post: http://lime-technology.com/forum/index.php?topic=39985.msg477858#msg477858 And the next few pages of that thread. I know that many people are confused by the whole issue as there are TWO preclear scripts (Joe L.'s script and the 'faster' one) and TWO Preclear Plugins (The Original Preclear Plugin and the Preclear.beta Plugin) . The PreClear Plugins are actually contained and discussed in the same thread. It takes some reading and study to get everything straight in one's head! But the point remains the same. Preclear should not install under 6.2 (nor should it appear within CA). Preclear Beta should install (and be the only version to appear in CA) when running 6.2. And if the plg's and the xml's were set up correctly this would indeed happen (and additionally FCP would also notify users about attempts to have incompatible Preclears plugins attempting to install) A user shouldn't have to jump through the hoops to get Preclear to work (or wonder why it doesn't). The problem is only going to get worse as 6.2 gets even closer (and hits) final stage and more people upgrade. I concur with your conclusions and agree that you have a valid point as I have been involved in assisting folks in doing the upgrades from one version to the newer ones. (as have you!) I tried the Preclear.beta plugin when I was preclearing that 3TB WD Red. It was VERY SLOW in doing the preread (it seems to me it was approaching 24 hours and it still was not finished!) and I decided to terminate it. (I suspect that my slow CPU was the cause but I admit I did not investigate enough to reach any conclusion so I didn't post about it. For what it's worth, folks, a 3TB is not the ideal choice of a drive to be used in evaluating a preclear scripts and plugins. ) I searched and found a 'fix' for which Joe L. wrote the short 'sed' script to modify his preclear script for ver 6.2. (BTW, folks, The reason Joe L. has not reissued the script with this mod is that he is not sure it will work with all of the earlier versions of unRAID!!!) I think you have to be a little bit careful in what CA and FCP do when they are doing their checking. In my opinion, while CA should not offer a out-of-version plugin for a new install, either CA or FCP should modify an existing install to remove a suspect one. Give a strong warning--- ABSOLUTELY--- but don't 'fix' what could be a non-issue with that setup. Link to comment
Squid Posted July 17, 2016 Share Posted July 17, 2016 I think you have to be a little bit careful in what CA and FCP do when they are doing their checking. In my opinion, while CA should not offer a out-of-version plugin for a new install, either CA or FCP should modify an existing install to remove a suspect one. Give a strong warning--- ABSOLUTELY--- but don't 'fix' what could be a non-issue with that setup. Which is why I have not as of yet moderated the Preclear plugin to prevent installation under 6.2 (and FCP only goes by what the author dictates as compatible or not) Link to comment
Frank1940 Posted July 17, 2016 Share Posted July 17, 2016 A few thoughts relevant to the pre-clear discussion ... (a) Historically, the reason JoeL developed the script was to eliminate the hours of downtime in an array when a new disk was added; as it would be off-line for the entire time it was zeroing a new disk. (b) Rather than simply zero the disk and add a pre-clear signature (which Tom was kind enough to share with JoeL to enable the script in the first place); Joe did a few additional tests to provide a bit of an initial "burn in" on the disk ... i.e. the pre-read and post-read phases. © Clearly the pre-clear script became the "standard" way of both testing and clearing new disks ... and many folks used it to test new disks that didn't require clearing [i.e. disks that were going to be replacements or new parity disks ... not new additions to the array]. Now, with v6.2, there is NO need to pre-clear a disk to do what point (a) noted, as there is no downtime when you add a new disk ... UnRAID handles the clearing and subsequent adding to the array without the previous off-line requirement. So the only real function pre-clear now provides is a bit of an initial test of the disk. Still a valuable feature; and certainly many prefer to have this one on their UnRAID server; BUT without the pre-clear requirement, this function can easily be done on any other PC you may have BEFORE you even bother to add the drive to your server. e.g. I've long done all my actual testing on a PC by simply connecting a new drive to an eSATA port and then running WD's Data Lifeguard to several rounds of tests. There are other equally good testing utilities -- Seagate's SeaTools; Crystal Disk; HDTune; etc. and a few others. If you have a dedicated PC you can use for testing and want to do a REALLY thorough test you can use SpinRite or HDD Regenerator ... but this level of testing really isn't needed and will take a VERY long time to do with modern drive sizes. [i used to do that as well, but don't anymore] Bottom line: The primary "clearing" function of the pre-clear script is simply not needed with v6.2 => so the pre-clear script is far less important than it used to be. I personally feel (and reinforced by years of experience in my working career) that infant mortality is still an issue with all things electrical and mechanical so some type of preburn is desirable. The main reason that many folks use their server to do this preburn is that it is 'on' anyway. (My other PC's are always shutdown at night and at other times during the day.) And there are a lot of CPU cycles available that would be unused other wise. And there is no worry that I might 'accidentally' terminate the process as once I start the preclear on the server, I can close the window and reopen it when I feel it is necessary to check process. Link to comment
Recommended Posts