NAS Posted July 17, 2016 Share Posted July 17, 2016 Sometimes I despair over the internet. So much discussion over one line of change log just to help out users who dont read the forum (most). Who cares if its not the 100% right thing to do when 7 words can save bunch of users a headache. oh well, forget I asked Link to comment
BRiT Posted July 17, 2016 Share Posted July 17, 2016 Sometimes I despair over the internet. So much discussion over one line of change log just to help out users who dont read the forum (most). Who cares if its not the 100% right thing to do when 7 words can save bunch of users a headache. oh well, forget I asked That wouldn't even be needed if the preclear plugin author had properly setup their plugin xml files. Link to comment
mr-hexen Posted July 17, 2016 Share Posted July 17, 2016 Sometimes I despair over the internet. So much discussion over one line of change log just to help out users who dont read the forum (most). Who cares if its not the 100% right thing to do when 7 words can save bunch of users a headache. oh well, forget I asked I agree with you NAS. I wouldn't expect LT to check every plugin for compatibility (nor do I tihnk you do), but when a plugin of such wide use has a known issue it couldn't hurt to add it to the OP as a "known issue" when such issues are brought to the attention of LT. Certainly they've gone through more trouble adding drivers "per user request" or enabling hard links in shfs only to plan to remove it later. Link to comment
Squid Posted July 17, 2016 Share Posted July 17, 2016 Sometimes I despair over the internet. So much discussion over one line of change log just to help out users who dont read the forum (most). Who cares if its not the 100% right thing to do when 7 words can save bunch of users a headache. oh well, forget I asked I agree with you NAS. I wouldn't expect LT to check every plugin for compatibility (nor do I tihnk you do), but when a plugin of such wide use has a known issue it couldn't hurt to add it to the OP as a "known issue" when such issues are brought to the attention of LT. By doing that, the implication is that it is a fault of LT and/or they are responsible to fix it rather than the plugin authors. Link to comment
Frank1940 Posted July 17, 2016 Share Posted July 17, 2016 Sometimes I despair over the internet. So much discussion over one line of change log just to help out users who dont read the forum (most). Who cares if its not the 100% right thing to do when 7 words can save bunch of users a headache. oh well, forget I asked That wouldn't even be needed if the preclear plugin author had properly setup their plugin xml files. AND/OR, with the benefit of twenty-twenty hindsight (and some Monday morning quarterbacking), a second thread had been started when the preclear.beta plugin was released. The confusion factor would be one-tenth of what it is today... Link to comment
mr-hexen Posted July 17, 2016 Share Posted July 17, 2016 Sometimes I despair over the internet. So much discussion over one line of change log just to help out users who dont read the forum (most). Who cares if its not the 100% right thing to do when 7 words can save bunch of users a headache. oh well, forget I asked I agree with you NAS. I wouldn't expect LT to check every plugin for compatibility (nor do I tihnk you do), but when a plugin of such wide use has a known issue it couldn't hurt to add it to the OP as a "known issue" when such issues are brought to the attention of LT. By doing that, the implication is that it is a fault of LT and/or they are responsible to fix it rather than the plugin authors. KNOWN ISSUES: Preclear plugin v199.45 needed with this version of unRAID, prior versions fail. Hardly an implication that this is LT's fault. Link to comment
jumperalex Posted July 17, 2016 Share Posted July 17, 2016 Even more obvious, just to show how ridiculous it is to be arguing over this ... KNOWN ISSUES: Preclear plugin v199.45 needed with this version of unRAID, prior versions fail. !!! THIS IS NOT A LIMETECH ISSUE. THIS IS A COURTESY NOTIFICATION !!! Link to comment
Squid Posted July 17, 2016 Share Posted July 17, 2016 Even more obvious, just to show how ridiculous it is to be arguing over this ... KNOWN ISSUES: Preclear plugin v199.45 needed with this version of unRAID, prior versions fail. !!! THIS IS NOT A LIMETECH ISSUE. THIS IS A COURTESY NOTIFICATION !!! 100% right. It is ridiculous arguing over who's responsibility it is... Link to comment
TODDLT Posted July 17, 2016 Share Posted July 17, 2016 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. I agree, the real reason I've always used pre-clear ws to force a bad drive to fail before it's in use. I only run 2 or 3 passes, some do more. I would not get rid of preclear. Link to comment
BRiT Posted July 17, 2016 Share Posted July 17, 2016 Even more obvious, just to show how ridiculous it is to be arguing over this ... KNOWN ISSUES: Preclear plugin v199.45 needed with this version of unRAID, prior versions fail. !!! THIS IS NOT A LIMETECH ISSUE. THIS IS A COURTESY NOTIFICATION !!! 100% right. It is ridiculous arguing over who's responsibility it is... I agree because the party that is best in position to address the issue is the Plugin Author. All they need to do is update their plugin(s) to properly include min and max versions. Link to comment
archedraft Posted July 17, 2016 Share Posted July 17, 2016 Well I guess I must disagree about the above mentioned so that we can continue this very important discussion. Link to comment
bobbintb Posted July 17, 2016 Share Posted July 17, 2016 Well I guess I must disagree about the above mentioned so that we can continue this very important discussion. *in stuffy British accent* And I disagree with your disagreement, kind sir. Link to comment
Frank1940 Posted July 17, 2016 Share Posted July 17, 2016 Even more obvious, just to show how ridiculous it is to be arguing over this ... KNOWN ISSUES: Preclear plugin v199.45 needed with this version of unRAID, prior versions fail. !!! THIS IS NOT A LIMETECH ISSUE. THIS IS A COURTESY NOTIFICATION !!! 100% right. It is ridiculous arguing over who's responsibility it is... I agree because the party that is best in position to address the issue is the Plugin Author. All they need to do is update their plugin(s) to properly include min and max versions. I almost hate to bring this up BUT the original plugin works perfectly with 6.2!!!! It is the the shell script which the user has to download separately and place in the proper directory that has the issue. And that was caused when (as I remember it) a decision was made to drop a shell command from the latest version of the kernel. Link to comment
jbartlett Posted July 18, 2016 Share Posted July 18, 2016 What will likely happen is that people will upgrade to 6.2 and later try to preclear a disk using the incompatible script. It'll fail. They'll want to know why. They'll most likely visit the forum thread dedicated to the preclear script. As long as it's mentioned there on the first post what versions of UNRAID it's compatible with, people should find the clue they wish to purchase. Link to comment
HellDiverUK Posted July 18, 2016 Share Posted July 18, 2016 Wow, the signal to noise ratio is poor in this thread. Link to comment
unknown Posted July 18, 2016 Share Posted July 18, 2016 Your recommendation to me was do not upgrate to beta builds without any experience with Linux / unraid system. RC2 works stable now ? Can i upgrade without much experience...? Link to comment
garycase Posted July 18, 2016 Share Posted July 18, 2016 Your recommendation to me was do not upgrate to beta builds without any experience with Linux / unraid system. RC2 works stable now ? Can i upgrade without much experience...? A personal choice; but I've found that RC2 is very stable, so it shouldn't be an issue. However ... the only really compelling feature over the final 6.1 release is dual parity => if you're not planning to add a 2nd parity disk, you may indeed want to wait for the final release. Link to comment
HellDiverUK Posted July 18, 2016 Share Posted July 18, 2016 However ... the only really compelling feature over the final 6.1 release is dual parity => if you're not planning to add a 2nd parity disk, you may indeed want to wait for the final release. And NVMe cache support. Link to comment
NAS Posted July 18, 2016 Share Posted July 18, 2016 Your recommendation to me was do not upgrate to beta builds without any experience with Linux / unraid system. RC2 works stable now ? Can i upgrade without much experience...? If it is for a production but non critical system I would normally say an absolute YES to upgrading to an unRAID RC. However as I understand it the beta call home is still in place and as such should the internet "licensing" server go offline or be uncontactable your production server would fail to boot. Important: I am not 100% sure if this statement is true as I dont think anyone knows exactly what passes to between the systems but it seems to be the logical interpretation of "Your server must have access to the Internet to use the unRAID 6.2 rc." and if so that is a extra factor to take into account. The more RC testers the better but eyes should be open going in. Link to comment
unknown Posted July 18, 2016 Share Posted July 18, 2016 Are there any guildes for updating this ? Or i only have to put this in "https://raw.githubusercontent.com/limetech/unRAIDServer-6.2/master/unRAIDServer.plg" ?! The VMs and everything still exist after updating. or should i reinstall all ? Link to comment
John_M Posted July 18, 2016 Share Posted July 18, 2016 Are there any guildes for updating this ? Or i only have to put this in "https://raw.githubusercontent.com/limetech/unRAIDServer-6.2/master/unRAIDServer.plg" ?! The VMs and everything still exist after updating. or should i reinstall all ? Read the very first post of this thread. Link to comment
shawnee66226 Posted July 18, 2016 Share Posted July 18, 2016 "- added Adaptec HBA 1000-8i drivers per user request" Is the 1000-16i included in this driver? I assume the drivers could be similar or the same. Was possibly thinking about getting one for a future build. Link to comment
eschultz Posted July 18, 2016 Share Posted July 18, 2016 "- added Adaptec HBA 1000-8i drivers per user request" Is the 1000-16i included in this driver? I assume the drivers could be similar or the same. Was possibly thinking about getting one for a future build. Yes, the driver we added includes support for: Adaptec HBA 1000-8e Adaptec HBA 1000-8i Adaptec HBA 1000-8i8e Adaptec HBA 1000-16e Adaptec HBA 1000-16i Link to comment
peter_sm Posted July 18, 2016 Share Posted July 18, 2016 @LT, Can you take a look at my sysloig? it's part in there that I don't have seen before... one is Jul 18 08:30:39 Tower kernel: CPU: 3 PID: 15322 Comm: kworker/u32:0 Tainted: G W 4.4.15-unRAID #1 Jul 18 08:30:39 Tower kernel: Hardware name: Supermicro X9SRL-F/X9SRL-F, BIOS 3.2 01/16/2015 Jul 18 08:30:39 Tower kernel: Workqueue: scsi_wq_3 sas_destruct_devices [libsas] Jul 18 08:30:39 Tower kernel: 0000000000000000 ffff880d4b217ca0 ffffffff81369dfe ffff880d4b217ce8 Jul 18 08:30:39 Tower kernel: 00000000000000ed ffff880d4b217cd8 ffffffff8104a31d ffffffff8115ab8a Jul 18 08:30:39 Tower kernel: 0000000000000000 ffffffff818a8060 ffff881034e8d010 ffff881034e63350 Jul 18 08:30:39 Tower kernel: Call Trace: Jul 18 08:30:39 Tower kernel: [<ffffffff81369dfe>] dump_stack+0x61/0x7e Jul 18 08:30:39 Tower kernel: [<ffffffff8104a31d>] warn_slowpath_common+0x8f/0xa8 Jul 18 08:30:39 Tower kernel: [<ffffffff8115ab8a>] ? sysfs_remove_group+0x4c/0x7f Jul 18 08:30:39 Tower kernel: [<ffffffff8104a379>] warn_slowpath_fmt+0x43/0x4b Jul 18 08:30:39 Tower kernel: [<ffffffff810cdd00>] ? SyS_memfd_create+0xfe/0x122 Jul 18 08:30:39 Tower kernel: [<ffffffff8115ab8a>] sysfs_remove_group+0x4c/0x7f Jul 18 08:30:39 Tower kernel: [<ffffffff8144bad0>] dpm_sysfs_remove+0x4b/0x50 Jul 18 08:30:39 Tower kernel: [<ffffffff81442e6a>] device_del+0x42/0x1e1 Jul 18 08:30:39 Tower kernel: [<ffffffffa0487868>] sas_rphy_remove+0x68/0x6b [scsi_transport_sas] Jul 18 08:30:39 Tower kernel: [<ffffffffa0487878>] sas_rphy_delete+0xd/0x18 [scsi_transport_sas] Jul 18 08:30:39 Tower kernel: [<ffffffffa08e3190>] sas_destruct_devices+0x63/0x85 [libsas] Jul 18 08:30:39 Tower kernel: [<ffffffff8105acd4>] process_one_work+0x194/0x2a0 Jul 18 08:30:39 Tower kernel: [<ffffffff8105b68a>] worker_thread+0x26b/0x353 Jul 18 08:30:39 Tower kernel: [<ffffffff8105b41f>] ? rescuer_thread+0x285/0x285 Jul 18 08:30:39 Tower kernel: [<ffffffff8105f910>] kthread+0xcd/0xd5 Jul 18 08:30:39 Tower kernel: [<ffffffff8105f843>] ? kthread_worker_fn+0x137/0x137 Jul 18 08:30:39 Tower kernel: [<ffffffff816232bf>] ret_from_fork+0x3f/0x70 Jul 18 08:30:39 Tower kernel: [<ffffffff8105f843>] ? kthread_worker_fn+0x137/0x137 Jul 18 08:30:39 Tower kernel: ---[ end trace c3ff1be6012ee6df ]--- Jul 18 08:30:39 Tower kernel: sas: phy-3:3 added to port-3:2, phy_mask:0x8 ( 12345678c) and Jul 17 19:39:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Jul 17 19:39:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] Jul 17 19:39:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Jul 17 19:39:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Jul 17 19:39:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Jul 17 19:39:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] Jul 17 19:39:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Jul 17 19:39:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Jul 17 19:40:05 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Jul 17 19:40:05 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] Jul 17 19:40:05 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Jul 17 19:40:05 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Jul 17 19:40:05 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Jul 17 19:40:05 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] Jul 17 19:40:05 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Jul 17 19:40:05 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Jul 17 19:40:37 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Jul 17 19:40:37 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] Jul 17 19:40:37 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Jul 17 19:40:37 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Jul 17 19:40:37 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Jul 17 19:40:37 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] Jul 17 19:40:37 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Jul 18 08:30:39 Tower kernel: sas: phy-3:3 added to port-3:2, phy_mask:0x8 ( 12345678c) Jul 18 08:30:39 Tower kernel: sas: DOING DISCOVERY on port 2, pid:15322 Jul 18 08:30:39 Tower kernel: sas: DONE DISCOVERY on port 2, pid:15322, result:0 Jul 18 08:30:39 Tower kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Jul 18 08:30:39 Tower kernel: sas: ata7: end_device-3:0: dev error handler Jul 18 08:30:39 Tower kernel: sas: ata8: end_device-3:1: dev error handler Jul 18 08:30:39 Tower kernel: sas: ata10: end_device-3:2: dev error handler Jul 18 08:30:39 Tower kernel: XFS (sdn1): metadata I/O error: block 0x80 ("xfs_trans_read_buf_map") error 5 numblks 32 Jul 18 08:30:39 Tower kernel: XFS (sdn1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Jul 18 08:30:39 Tower kernel: XFS (sdn1): metadata I/O error: block 0x80 ("xfs_trans_read_buf_map") error 5 numblks 32 Jul 18 08:30:39 Tower kernel: XFS (sdn1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Jul 18 08:30:39 Tower kernel: XFS (sdn1): metadata I/O error: block 0x80 ("xfs_trans_read_buf_map") error 5 numblks 32 Jul 18 08:30:39 Tower kernel: XFS (sdn1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Jul 18 08:30:39 Tower kernel: XFS (sdn1): metadata I/O error: block 0x80 ("xfs_trans_read_buf_map") error 5 numblks 32 Jul 18 08:30:39 Tower kernel: XFS (sdn1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Jul 18 08:30:39 Tower kernel: XFS (sdn1): metadata I/O error: block 0x80 ("xfs_trans_read_buf_map") error 5 numblks 32 Jul 18 08:30:39 Tower kernel: XFS (sdn1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Jul 18 08:30:39 Tower kernel: XFS (sdn1): metadata I/O error: block 0x80 ("xfs_trans_read_buf_map") error 5 numblks 32 Jul 18 08:30:39 Tower kernel: XFS (sdn1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Jul 18 08:30:39 Tower kernel: ata10.00: ATA-9: Hitachi HTS541010A9E680, J8100019J1XWJA, JA0OA4D0, max UDMA/133 Jul 18 08:30:39 Tower kernel: ata10.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32) Jul 18 08:30:39 Tower kernel: ata10.00: configured for UDMA/133 Jul 18 08:30:39 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 tower-syslog-20160718-1803.zip Link to comment
chuga Posted July 19, 2016 Share Posted July 19, 2016 Hi, just checking to see if the recent betas and RC versions have 'fixed' the issue where unraid does not appear in windows 10 network? I hoped it would, with various samba updates, but on RC2 now and still no luck. Yes I can browse by pasting in IP address directly, have checked to make sure unraid the local master etc. will be interested to hear if anyone else still has this issue thanks, Link to comment
Recommended Posts