Z170a slow boot windows 10, disk misalignment? |
Post Reply |
Author | |
Kladno
Newbie Joined: 15 Aug 2016 Status: Offline Points: 34 |
Post Options
Thanks(0)
Posted: 17 Dec 2017 at 4:36am |
Model : SAMSUNG SSD SM841 2.5" 7mm 256GB - O.K. Model: Hitachi HDS723030ALA640 - O.K. Model : MKNSSDTR500GB ID Cur Wor Thr RawValues(6) Attribute Name A3 100 100 __0 000000000011 Initial Invalid Blocks (factory bad blocks) C7 100 100 _50 0000000002D5 Ultra DMA CRC Error Rate raw value 2D5h = 725 CRC errors The ultra DMA CRC error count indicates problems with the transfer of data between the host and the disk. They can't be caused by software, and they don't indicate a problem with the disk itself. The most common cause for this is a faulty cable. Replace the SATA data cable and reseat all of the drive cables. Check if the CRC numbers increases over time. |
|
ron7000
Newbie Joined: 26 Sep 2015 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
one thing i just remembered was,
i do a lot of linux work so i typically had a second SSD {not necessarily the mushkin listed above} which had either SLES, RHEL, opensuse, centos, or any other linux distro on it. And when I needed i would boot that linux SSD, which had NTFS-3g installed so it could mount and read/write data from those hitachi disks which were NTFS formatted. And I do remember once in a while when going back to windows it would squawk about an error on my D: data or E: bkup drive and want to do a disk check on startup, sometimes i'd let it, sometimes i'd cancel it, either way I have never had a data problem with either of those hitachi disks. I had formatted them the one time years ago when i got them when running Win7 and the only other time was couple days ago fixing this win10 boot problem. And when i had been running Win7 prior to Win10, I was using some software that allowed windows 7 to access EXT3 formatted disks (was EST2FSD I think) and I remember that was flaky but it never should've accessed/touched those hitachi disks which were always NTFS. I think it was called the dirty flag or something being set within NTFS/Windows and was not uncommon when an ntfs disk was accessed from linux then reused by Windows. however i have not booted my linux ssd in months, and a bootup disk check file system dirty has not happened for an even longer period of time. Edited by ron7000 - 16 Dec 2017 at 1:25pm |
|
ron7000
Newbie Joined: 26 Sep 2015 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
I am positive both those 3tb hitachi disks were not connected during the windows 10 install,
whenever I have done a windows, or linux, install on anything over the last 10+ years step 1 is I always physically disconnect all other hard disks, especially any data disk, so there is zero risk of messing them up. I am positive only the Samsung SSD was connected when the Windows 10 install was done. fyi, the M: mushkin ssd has been flaky since i bought it last year so it is currently blank and not being used, and I only reconnected it and left it connected since couple days ago after i had reformatted the hitachi disks. since this post, my computer with this z170a has been much better with boot speeds, so I am pretty sure the re-initialize & reformat of those hitachi disks fixed whatever the problem was. [CODE] ---------------------------------------------------------------------------- CrystalDiskInfo 7.5.0 (C) 2008-2017 hiyohiyo Crystal Dew World : https://crystalmark.info/ ---------------------------------------------------------------------------- OS : Windows 10 [10.0 Build 16299] (x64) Date : 2017/12/15 23:39:39 -- Controller Map ---------------------------------------------------------- + Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller [ATA] - SAMSUNG SSD SM841 2.5" 7mm 256GB - MKNSSDTR500GB - Hitachi HDS723030ALA640 - Hitachi HDS723030ALA640 - HL-DT-ST BD-RE WH14NS40 - Microsoft Storage Spaces Controller [SCSI] -- Disk List --------------------------------------------------------------- (1) SAMSUNG SSD SM841 2.5" 7mm 256GB : 256.0 GB [0/0/0, pd1] - sg (2) MKNSSDTR500GB : 500.1 GB [1/0/1, pd1] - m2 (3) Hitachi HDS723030ALA640 : 3000.5 GB [2/0/2, pd1] (4) Hitachi HDS723030ALA640 : 3000.5 GB [3/0/3, pd1] ---------------------------------------------------------------------------- (1) SAMSUNG SSD SM841 2.5" 7mm 256GB ---------------------------------------------------------------------------- Model : SAMSUNG SSD SM841 2.5" 7mm 256GB Firmware : DXM02D0Q Serial Number : {deleted} Disk Size : 256.0 GB (8.4/137.4/256.0/256.0) Buffer Size : Unknown Queue Depth : 32 # of Sectors : 500118192 Rotation Rate : ---- (SSD) Interface : Serial ATA Major Version : ACS-2 Minor Version : ATA8-ACS version 4c Transfer Mode : SATA/600 | SATA/600 Power On Hours : Unknown Power On Count : 1569 count Host Reads : 5336 GB Host Writes : 4445 GB Wear Level Count : 148 Temperature : Unknown Health Status : Good (100 %) Features : S.M.A.R.T., 48bit LBA, NCQ, TRIM, DevSleep APM Level : ---- AAM Level : ---- Drive Letter : C: -- S.M.A.R.T. -------------------------------------------------------------- ID Cur Wor Thr RawValues(6) Attribute Name 05 100 100 _10 000000000000 Reallocated Sector Count 0C _98 _98 __0 000000000621 Power-on Count AF 100 100 _10 000000000000 Program Fail Count (Chip) B0 100 100 _10 000000000000 Erase Fail Count (Chip) B1 _95 _95 __5 000000000094 Wear Leveling Count B2 100 100 _10 000000000000 Used Reserved Block Count (Chip) B3 100 100 _10 000000000000 Used Reserved Block Count (Total) B4 100 100 _10 0000000023C0 Unused Reserved Block Count (Total) B5 100 100 _10 000000000000 Program Fail Count (Total) B6 100 100 _10 000000000000 Erase Fail Count (Total) BB 100 100 __0 000000000000 Uncorrectable Error Count C3 200 200 __0 000000000000 ECC Error Rate F1 _99 _99 __0 00022BA60587 Total LBAs Written F2 _99 _99 __0 00029B04C5F6 Total LBAs Read ---------------------------------------------------------------------------- (2) MKNSSDTR500GB ---------------------------------------------------------------------------- Model : MKNSSDTR500GB Firmware : O1126A Serial Number : {deleted} Disk Size : 500.1 GB (8.4/137.4/500.1/500.1) Buffer Size : Unknown Queue Depth : 32 # of Sectors : 976773168 Rotation Rate : ---- (SSD) Interface : Serial ATA Major Version : ACS-2 Minor Version : ---- Transfer Mode : SATA/600 | SATA/600 Power On Hours : 75 hours Power On Count : 294 count Host Reads : 1903 GB Host Writes : 1772 GB NAND Writes : 1122 GB Temperature : 10 C (50 F) Health Status : Good (100 %) Features : S.M.A.R.T., 48bit LBA, NCQ, TRIM APM Level : ---- AAM Level : ---- Drive Letter : M: -- S.M.A.R.T. -------------------------------------------------------------- ID Cur Wor Thr RawValues(6) Attribute Name 01 100 100 __0 000000000000 Raw Read Error Rate 05 100 100 __0 000000000000 Reallocated Sectors Count 09 100 100 __0 00000000004B Power-On Hours 0C 100 100 __0 000000000126 Power Cycle Count A0 100 100 __0 000000000000 Uncorrectable Sector Count A1 100 100 __0 000000000064 Valid Spare Blocks A3 100 100 __0 000000000011 Initial Invalid Blocks A4 100 100 __0 000000001188 Total TLC Erase Count A5 100 100 __0 00000000001C Maximum TLC Erase Count A6 100 100 __0 000000000001 Minimum TLC Erase Count A7 100 100 __0 000000000003 Average TLC Erase Count A8 100 100 __0 0000000003E8 Vendor Specific A9 100 100 __0 000000000064 Percentage Lifetime Remaining AF 100 100 __0 000000000000 Vendor Specific B0 100 100 __0 000000000000 Vendor Specific B1 100 100 _50 00000000004B Vendor Specific B2 100 100 __0 000000000000 Vendor Specific B5 100 100 __0 000000000000 Program Fail Count B6 100 100 __0 000000000000 Erase Fail Count C0 100 100 __0 000000000017 Power-off Retract Count C2 100 100 __0 00000000000A Temperature C3 100 100 __0 000000000000 Cumulative ECC Bit Correction Count C4 100 100 _16 000000000000 Reallocation Event Count C5 100 100 __0 000000000000 Current Pending Sector Count C6 100 100 __0 000000000000 Smart Off-line Scan Uncorrectable Error Count C7 100 100 _50 0000000002D5 Ultra DMA CRC Error Rate E8 100 100 __0 000000000064 Available Reserved Space F1 100 100 __0 00000000DD96 Total LBA Write F2 100 100 __0 00000000EDFD Total LBA Read F5 100 100 __0 000000008C40 Cumulative Program NAND Pages ---------------------------------------------------------------------------- (3) Hitachi HDS723030ALA640 ---------------------------------------------------------------------------- Model : Hitachi HDS723030ALA640 Firmware : MKAOA5C0 Serial Number : {deleted} Disk Size : 3000.5 GB (8.4/137.4/3000.5/3000.5) Buffer Size : Unknown Queue Depth : 32 # of Sectors : 5860533168 Rotation Rate : 7200 RPM Interface : Serial ATA Major Version : ATA8-ACS Minor Version : ATA8-ACS version 4 Transfer Mode : SATA/600 | SATA/600 Power On Hours : 5541 hours Power On Count : 3473 count Temperature : 43 C (109 F) Health Status : Good Features : S.M.A.R.T., APM, 48bit LBA, NCQ APM Level : 0080h [ON] AAM Level : ---- Drive Letter : D: -- S.M.A.R.T. -------------------------------------------------------------- ID Cur Wor Thr RawValues(6) Attribute Name 01 100 100 _16 000000000000 Read Error Rate 02 135 135 _54 000000000056 Throughput Performance 03 162 162 _24 000C017F023B Spin-Up Time 04 100 100 __0 000000000EE9 Start/Stop Count 05 100 100 __5 000000000000 Reallocated Sectors Count 07 100 100 _67 000000000000 Seek Error Rate 08 135 135 _20 00000000001A Seek Time Performance 09 100 100 __0 0000000015A5 Power-On Hours 0A 100 100 _60 000000000000 Spin Retry Count 0C 100 100 __0 000000000D91 Power Cycle Count C0 _96 _96 __0 000000001528 Power-off Retract Count C1 _96 _96 __0 000000001528 Load/Unload Cycle Count C2 139 139 __0 0032000D002B Temperature C4 100 100 __0 000000000000 Reallocation Event Count C5 100 100 __0 000000000000 Current Pending Sector Count C6 100 100 __0 000000000000 Uncorrectable Sector Coun Edited by ron7000 - 16 Dec 2017 at 1:08pm |
|
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
The slow Windows booting symptoms sounds like you had one or both of those HDDs connected to the Z97 PC when you installed Windows 7 on the SSD. The Windows installer, if it finds more than one drive operating during the installation, will put the Windows System/boot partition on another drive besides the target OS drive. MSoft has some reason for this, but it causes side affects, like Windows not booting if the drive with the System partition is removed or dies. Or if you move that drive to another PC, it now has two System/boot partitions. When Windows begins to start on the Z170 PC, it would find the System partition on the HDD, and use it instead of the System partition on the SDD. Or finding two partitions causes some confusion that takes time to sort out. If the HDDs had a partition misalignment, it might take longer for the System partition to be found, but since only one contiguous partition is being searched for, that should not take long even if not aligned correctly. Otherwise, who knows what caused the delay, without checking the disks before you formatted them again. The Fast Boot option is really a fast POST option. It reduces POST time, skipping some POST checks when set to Fast. When set to Ultra Fast, which can only be used with a UEFI booting Windows installation, POST is run in UEFI mode, not emulated BIOS mode (the default) so can complete much faster. |
|
Kladno
Newbie Joined: 15 Aug 2016 Status: Offline Points: 34 |
Post Options
Thanks(0)
|
Can you show the SMART values for both Toshiba disks?
You can use any Windows SW like CrystalDiskInfo |
|
ron7000
Newbie Joined: 26 Sep 2015 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
windows 10 64-bit installed on SSD, I have two 3TB hitachi hard disks as data drives, for ~5+ years, used on my previous computer which was windows 7 64-bit and that was when I had initially ntfs formatted these two disks. one is mounted as {data D:} and the second is mounted as {bkup E:}. Tthese drives worked great on previous computer, which was an Asrock Z97 Extreme6 with windows 7 on an ssd.
I now have a Z170a-X1/3.1 running windows 10 64-bit, installed windows on a new SSD then when finished connected my two 3TB hitachi drives which have all my data. Since then when mono boots I get the rotating circle thing for around 5-10 seconds before it jumps to windows 10 then immediately logs in. If i disconnect those hitachi drives the system boots very fast as I would expect it to, yesterday i did a diskpart - clean on both those hitachi drives windows forces me to Initialize those drives before I can format them, I initialize, have them as GPT, and format them in NTFS from windows 10, then copied all my data back to them. Now my Z170a-X1/3.1 will boot as fast as if those hitachi drives were not connected. What about those hitachi drives would have caused this boot delay? Could there have been a partition misalignment or something or other? I have basically out of the box uefi settings, set to fast boot not ultra fast, but even when i did try ultrafast the same delay happened. So i'm quite positive it was not a boot setting causing it, as well as problem was solved immediately when disconnecting those hitachi drives when diagnosing. And I have been running the latest UEFI version, 7.10 or whatever it is, for quite a while. Edited by ron7000 - 15 Dec 2017 at 4:24am |
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |