chuck23322

You probably want the "preclear.sh results" thread. https://forums.lime-technology.com/topic/3930-preclearsh-results-questions-about-your-results-post-them-here/

Looks good. In the past, the errors immediately began (whether or not I actually used the plugin). I'm assuming it was something related to my old motherboard having a floppy-chip and returning a null serial (at least that''s what I gathered from the above) I checked my NewEgg order history -- that MoBo dates back to a 2010 order when I first built a WHS server -- but quickly converted it to an Unraid server with 250 & 500mb drives -- back then, on 4.x unraid Highly doubt any MoBo of recent still has a floppy controller. Anyway, huge thanks. Sincerely appreciate having a GUI front-end to preclear...

No, I don't. But was looking at syslog, and apparently Unraid thinks I do root@unraid:~# cat /var/log/syslog | grep fd0 Sep 24 09:11:03 unraid kernel: pci 0000:00:11.0: reg 0x18: [io 0xfd00-0xfd07] Sep 24 09:11:03 unraid kernel: Floppy drive(s): fd0 is 1.44M Sep 24 09:11:29 unraid kernel: blk_update_request: I/O error, dev fd0, sector 0 Sep 24 09:13:41 unraid kernel: blk_update_request: I/O error, dev fd0, sector 0 Sep 24 09:15:02 unraid kernel: blk_update_request: I/O error, dev fd0, sector 0 root@unraid:~# Digging further -- checking my motherboard specs - https://www.gigabyte.com/Motherboard/GA-MA770T-UD3-rev-14#sp South Bridge: 1 x IDE connector supporting ATA-133/100/66/33 and up to 2 IDE devices 6 x SATA 3Gb/s connectors supporting up to 6 SATA 3Gb/s devices Support for SATA RAID 0, RAID 1 and RAID 0+1 iTE IT8720 chip: 1 x floppy disk drive connector supporting up to 1 floppy disk drive

Hi, I'm at Unraid 6.3.5 root@unraid:~# lsblk --version && lsblk -nbP -o name,type,serial lsblk from util-linux 2.28.2 NAME="md11" TYPE="md" SERIAL="" NAME="sdf" TYPE="disk" SERIAL="K4K7UXVB" NAME="sdf1" TYPE="part" SERIAL="" NAME="md8" TYPE="md" SERIAL="" NAME="sdo" TYPE="disk" SERIAL="5XW1BMCH" NAME="sdo1" TYPE="part" SERIAL="" NAME="sdd" TYPE="disk" SERIAL="WD-WMAZA5166243" NAME="sdd1" TYPE="part" SERIAL="" NAME="md6" TYPE="md" SERIAL="" NAME="sdm" TYPE="disk" SERIAL="K4KA796B" NAME="sdm1" TYPE="part" SERIAL="" NAME="sdb" TYPE="disk" SERIAL="5YD3YW18" NAME="sdb1" TYPE="part" SERIAL="" NAME="md4" TYPE="md" SERIAL="" NAME="sdk" TYPE="disk" SERIAL="Z1F0MZ6Y" NAME="sdk1" TYPE="part" SERIAL="" NAME="md2" TYPE="md" SERIAL="" NAME="sdi" TYPE="disk" SERIAL="Z1F1ZZRJ" NAME="sdi1" TYPE="part" SERIAL="" NAME="sdg" TYPE="disk" SERIAL="5YD5RWGW" NAME="sdg1" TYPE="part" SERIAL="" NAME="md9" TYPE="md" SERIAL="" NAME="fd0" TYPE="disk" SERIAL="" NAME="md10" TYPE="md" SERIAL="" NAME="sde" TYPE="disk" SERIAL="WD-WMAWZ0247359" NAME="sde1" TYPE="part" SERIAL="" NAME="md7" TYPE="md" SERIAL="" NAME="loop0" TYPE="loop" SERIAL="" NAME="sdn" TYPE="disk" SERIAL="S1F0KCZF" NAME="sdn1" TYPE="part" SERIAL="" NAME="sdc" TYPE="disk" SERIAL="4C531001540804103384" NAME="sdc1" TYPE="part" SERIAL="" NAME="md5" TYPE="md" SERIAL="" NAME="sdl" TYPE="disk" SERIAL="Z1W1AGJX" NAME="sdl1" TYPE="part" SERIAL="" NAME="sda" TYPE="disk" SERIAL="ML0221F30431JD" NAME="sda1" TYPE="part" SERIAL="" NAME="md3" TYPE="md" SERIAL="" NAME="sdj" TYPE="disk" SERIAL="S1F01NX2" NAME="sdj1" TYPE="part" SERIAL="" NAME="md1" TYPE="md" SERIAL="" NAME="sdh" TYPE="disk" SERIAL="Z1F0L360" NAME="sdh1" TYPE="part" SERIAL=""

I've installed the update -- and the errors persist -- goes away when I uninstall the Preclear plugin.

Am I the only one getting: Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339 Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339 Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339 Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339 Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339 If I install the Preclear plugin -- this happens and fills up my logs. When I remove it, it goes away. If it matters, I've included that "rc.diskinfo" file. (I have no clue what I am looking at) I am running: preclear plugin - 2017.09.22a (just re-installed it) rc.diskinfo.txt

Been awhile since I've added a new disk. Putting in a new 3TB drive -- running 4 passes of PreClear -- have downloaded and running the latest version of it. Noticed something that looked weird to me. In my "settings" for RC4 -- I have "Default partition format:" = MBR: 4k aligned And I'm running Pre_Clear with: ./preclear_disk.sh -M 4 -c 4 /dev/sde I would expect it to run as 4k aligned, starting on sector 64... Says "will start on sector 64" -- what I would expect... Then the pre-clear starts... That says starts on sector 1 Huh?

Each drive "stands alone". While if you have some drives formatted poorly, you may have lower performance on those drives. "Back in the day" you could set a jumper on AF drives and format them "without alignment", or remove (or not install) the jumper and format them with the "alignment". Where you got into trouble is if you did it backwards -- 'aligned' with a jumper, or didn't align without the jumper. {And note: Removing/Adding a jumper AFTER the drive is active in your array is bad juju. You need to effectively remove the drive, safely from the array, and decide whether to jumper and format without alignment {the jumper "fakes out" the drive to effectively do the alignment internally} -- or, as many are now doing, not jumpering and formatting with alignment} Since most modern AF drives are shipped without the jumper now, the proper behavior (of 4.7 +) is to format ALL drives as aligned. This works fine on old and new drives now. So yes, you can mix/match. Just if you get it wrong, you'll get worse performance. There are long threads here on the whole subject.

Perhaps another tweak? SATA I, II, or III ports? As I understand it, today's HDDs don't even saturate SATA I, so SATA II or III is basically just marketing hype. For an SSD application it certainly matters, but it shouldn't matter for a HDD application like unRAID. So far, I can see a difference between SATA I and II in performance... I'm not quite OCD to graph it out though. Especially if I'm doing port multiplying.... {of course}. And my ancient SSD (ancient by modern standards) is an OCZ Agility which doesn't benefit from SATA III, but certainly does for SATA II vs. SATA I. But even internally, one-to-one, I've learned to move my "smaller" drives to the SATA I connections so that parity checks get done with the SATA I connections as soon as they can.

Perhaps another tweak? SATA I, II, or III ports?

For PCI it's hard to get much cheaper than monoprice. I know that 4 port card works. yea, that monoprice card works great for me, but a small FYI to those considering it -- it's SATA 1.0 -- a little slow. I've got to jiggle around my drives so my smaller ones are on that card, so that a pairity check, etc gets done faster once it's past the 4 SATA 1.0 connections and moves over to just my SATA II's on the MoBo (six) -- the recommendation received was move my small drives to the SATA 1 connections, and the big drives to SATA II. And it may be the case that being an old-fashioned PCI card that SATA 1.0 is just fine... but if anyone has a lead on a similar, cheap 4-port PCI card that is SATA II ... drop a line here

http://tinyurl.com/6gsm5ch

Hello. First time post here. Just getting started with unRAID. Ultimately this new system will replace my WHS. While awaiting the flash memory I ordered (waiting to register those for the PRO version), I couldn't wait to build the server and get three of my "laying around" hard drives online... to play with. I downloaded/installed 4.7-beta1 (because I want to avoid the jumper issues when formatting, etc), and installed unMenu, mail, etc. Ran pre_clear on all three of the drives. One of them reports as a "known" issue -- a Seagate 7200.11 (SDA) Model Family: Seagate Barracuda 7200.11 family Device Model: ST3750330AS Serial Number: 5QK0169W Firmware Version: SD04 But when I check Seagate's website, there is nothing for my serial number, nor my firmware. Googling, I've read stories of those who have bricked this drive upgrading the firmware when it was not advised/listed on the Seagate website. Attached is the pre-clear results from Seagate SDA (ST3750330AS), and the Western Digital SDB and SDC (B = WD5000AAKS, C = WD5000AAJS ) I'm not sure how to read these results. I know these were removed from 'active' service awhile back... (being 700, 500 and 500 gb respectively -- they had been upgraded in the WHS server to larger drives. I now have the ability with my new build to use them again...) Some of the results come back as "Pre-fail" or "Old_age", and again, not sure how to interpret this data -- informational? Of concern? Example: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 191 167 021 Pre-fail Always - 5433 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 38 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 So I guess I have three basic questions: 1) If Seagate's website for that drive comes back, by serial number, and doesn't have anything listed for my current firmwared of SD04 -- should I just leave it be? 2) The SMARTS info about "Pre-fail" or "Old_age" -- how should I interpret it? 3) And if anyone sees anything else 'weird' in the pre_clear report, I would be grateful for the education. (Pre_clear results attached) PreClear-SDA.txt PreClear-SDB.txt PreClear-SDC.txt