My pre-clear completed successfully, but today when I added it to the array I saw this, is it anything to worry about?

 

The drive is a Hitachi 2TB, no AF I believe.  My server is set to 4k aligned and I ran the standard preclear, no -A.  I assume that is accurate right?

 

May 10 22:14:59 Tower kernel: scsi5 : ahci (Drive related)
May 10 22:14:59 Tower kernel: ata5: SATA max UDMA/133 irq_stat 0x00400000, PHY RDY changed irq 22 (Drive related)
May 10 22:14:59 Tower kernel: ata5: softreset failed (device not ready) (Minor Issues)
May 10 22:14:59 Tower kernel: ata5: applying SB600 PMP SRST workaround and retrying (Drive related)
May 10 22:14:59 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
May 10 22:14:59 Tower kernel: ata5.00: ATA-8: Hitachi HDS723020BLA642, MN6OA800, max UDMA/133 (Drive related)
May 10 22:14:59 Tower kernel: ata5.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA (Drive related)
May 10 22:14:59 Tower kernel: ata5.00: configured for UDMA/133 (Drive related)
May 10 22:14:59 Tower kernel: scsi 5:0:0:0: Direct-Access     ATA      Hitachi HDS72302 MN6O PQ: 0 ANSI: 5 (Drive related)
May 10 22:14:59 Tower kernel: sd 5:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) (Drive related)
May 10 22:14:59 Tower kernel: sd 5:0:0:0: [sde] Write Protect is off (Drive related)
May 10 22:14:59 Tower kernel: sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00 (Drive related)
May 10 22:14:59 Tower kernel: sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
May 10 22:14:59 Tower kernel:  sde: (Drive related)
May 10 22:14:59 Tower kernel: sd 5:0:0:0: [sde] Attached SCSI disk (Drive related)
May 10 22:14:59 Tower emhttp: pci-0000:00:11.0-scsi-4:0:0:0 host5 (sde) Hitachi_HDS723020BLA642_MN1240F33PRKBD (Drive related)
May 10 22:23:21 Tower unmenu[1469]: Disk /dev/sde doesn't contain a valid partition table (Drive related)
May 10 22:27:47 Tower kernel:  sde: unknown partition table (Drive related)
May 10 22:29:20 Tower kernel:  sde: unknown partition table (Drive related)
May 11 09:13:46 Tower kernel:  sde: sde1 (Drive related)
May 11 19:57:06 Tower preclear_disk-diff[14546]: == invoked as: ./preclear_disk.sh /dev/sde (Misc)
May 11 19:57:06 Tower preclear_disk-diff[14546]: == Disk /dev/sde has been successfully precleared (Misc)
May 11 19:57:06 Tower preclear_disk-diff[14546]: ** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde (Misc)
May 11 19:57:06 Tower preclear_disk-diff[14546]: == S.M.A.R.T Initial Report for /dev/sde  (Misc)
May 11 19:57:06 Tower preclear_disk-diff[14546]: Disk: /dev/sde (Misc)
May 11 19:57:06 Tower preclear_disk-diff[14546]: == S.M.A.R.T Final Report for /dev/sde  (Misc)
May 11 19:57:06 Tower preclear_disk-diff[14546]: Disk: /dev/sde (Misc)
May 11 20:27:15 Tower kernel: md: import disk8: [8,64] (sde) Hitachi HDS72302 MN1240F33PRKBD size: 1953514552 (Drive related)
May 11 20:27:15 Tower kernel: md: disk8 new disk (unRAID engine)
May 11 20:27:42 Tower emhttp: shcmd (203): /usr/local/sbin/set_ncq sde 1 >/dev/null (Drive related)
May 11 20:27:42 Tower emhttp: clearing disk8* ... (Other emhttp)
May 11 20:27:42 Tower emhttp: writing mbr on disk 8 (/dev/sde) with partition 1 offset 64 (Drive related)
May 11 20:27:42 Tower emhttp: re-reading /dev/sde partition table (Drive related)
May 11 20:27:42 Tower kernel:  sde: sde1 (Drive related)
May 11 20:27:43 Tower kernel: md8: running, size: 1953514552 blocks (Drive related)
May 11 20:27:44 Tower emhttp: shcmd (212): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md8 /mnt/disk8 2>$stuff$1 | logger (Other emhttp)
May 11 20:27:44 Tower emhttp: disk8 mount error: 32 (Errors)
May 11 20:32:08 Tower emhttp: shcmd (235): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md8 /mnt/disk8 2>$stuff$1 | logger (Other emhttp)
May 11 20:32:10 Tower emhttp: shcmd (236): chmod 700 '/mnt/disk8' (Other emhttp)

preclear.txt

you just finished clearing the drive, and assigned it.  It is not yet formatted, therefore, the attempt to mount it failed.  This is entirely expected and normal at this point in the installation.

 

Joe L.