Page 2 of 2 FirstFirst 12
  1.    09 Apr 2015 #11
    Join Date : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM

    Quote Originally Posted by silv55 View Post
    i used an Iso of win7 that had 30 days to activate and done all updates then upgraded to win 10 tp throughout the update process, by shining up at MS ,everything went smooth and system is running just fine, what are my chances of keeping a copy of Win 10 RTM ?
      My ComputerSystem Spec
  2.    09 Apr 2015 #12
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    What OS was originally installed on the machine?

    I think there were some issues reported with the Intel chipset drivers causing HDD problems. You might try visiting Intel and 'updating' all of the Intel drivers related to your machine.

    Can you keep Win10 - not unless you go through legal channels (that's why I asked about the original OS)
    Technically you can do whatever you want with your machine .. just don't expect MS or the Designer Media forums (VistaX64, SevenForums, EightForums, TenForums, PC Help) to assist you after Win10 goes RTM when there are issues.

    There wasn't any need to install Win7 in 30 day trial mode - you could have just installed Win10 using the ISO after joining the Insider program. Still is was a worthwhile test.

    The Technical Preview agreement is a bit different from a licensed product - MS actually wants people to install Win10 to test drive it.
      My ComputerSystem Spec
  3.    13 Apr 2015 #13
    Join Date : Feb 2015
    Posts : 111
    Win 10 Preview
    Thread Starter

    Quote Originally Posted by NickTh View Post
    You still "owe" the results of GsmartControl. You can do the same from Ubuntu. Open a terminal and run
    Code:
    sudo apt-get install smartmontools --no-install-recommends
    sudo smartctl -a /dev/sdX
    Replace X with the actual disk leter (e.g. sda or sdb....).
    Post the results here inside [CODE] tags. Then we can inspect the results and conclude somewhere.
    Thanks.

    === START OF INFORMATION SECTION ===
    Model Family: Seagate Barracuda 7200.10
    Device Model: ST3320620AS
    Serial Number: 9QF78WVQ
    Firmware Version: 3.ADG
    User Capacity: 320,072,933,376 bytes [320 GB]
    Sector Size: 512 bytes logical/physical
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
    Local Time is: Tue Apr 14 00:08:11 2015 EDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled


    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: FAILED!
    Drive failure expected in less than 24 hours. SAVE ALL DATA.
    See vendor-specific Attribute list for failed Attributes.


    General SMART Values:
    Offline data collection status: (0x82) Offline data collection activity
    was completed without error.
    Auto Offline Data Collection: Enabled.
    Self-test execution status: ( 73) The previous self-test completed having
    a test element that failed and the test
    element that failed is not known.
    Total time to complete Offline
    data collection: ( 430) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 107) minutes.


    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 117 073 006 Pre-fail Always - 0
    3 Spin_Up_Time 0x0003 097 094 070 Pre-fail Always - 0
    4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 471
    5 Reallocated_Sector_Ct 0x0033 001 001 036 Pre-fail Always FAILING_NOW 57106
    7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 296546108
    9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 14608
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 449
    187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 65535
    189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
    190 Airflow_Temperature_Cel 0x0022 067 038 045 Old_age Always In_the_past 33 (33 104 34 33 0)
    194 Temperature_Celsius 0x0022 033 062 000 Old_age Always - 33 (0 13 0 0 0)
    195 Hardware_ECC_Recovered 0x001a 076 045 000 Old_age Always - 225328440
    197 Current_Pending_Sector 0x0012 095 094 000 Old_age Always - 116
    198 Offline_Uncorrectable 0x0010 095 094 000 Old_age Offline - 116
    199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 4
    200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
    202 Data_Address_Mark_Errs 0x0032 055 208 000 Old_age Always - 45


    SMART Error Log Version: 1
    ATA Error Count: 120 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.


    Error 120 occurred at disk power-on lifetime: 14556 hours (606 days + 12 hours)
    When the command that caused the error occurred, the device was active or idle.


    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 51 01 ae f4 49 e0 Error: UNC at LBA = 0x0049f4ae = 4846766


    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    42 00 01 ae f4 49 e0 00 04:32:41.155 READ VERIFY SECTOR(S) EXT
    42 00 02 ae f4 49 e0 00 04:32:41.146 READ VERIFY SECTOR(S) EXT
    42 00 02 ac f4 49 e0 00 04:32:41.130 READ VERIFY SECTOR(S) EXT
    42 00 04 ac f4 49 e0 00 04:32:39.878 READ VERIFY SECTOR(S) EXT
    42 00 04 a8 f4 49 e0 00 04:32:38.652 READ VERIFY SECTOR(S) EXT


    Error 119 occurred at disk power-on lifetime: 14556 hours (606 days + 12 hours)
    When the command that caused the error occurred, the device was active or idle.


    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 51 02 ae f4 49 e0 Error: UNC at LBA = 0x0049f4ae = 4846766


    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    42 00 02 ae f4 49 e0 00 04:32:41.155 READ VERIFY SECTOR(S) EXT
    42 00 02 ac f4 49 e0 00 04:32:41.146 READ VERIFY SECTOR(S) EXT
    42 00 04 ac f4 49 e0 00 04:32:41.130 READ VERIFY SECTOR(S) EXT
    42 00 04 a8 f4 49 e0 00 04:32:39.878 READ VERIFY SECTOR(S) EXT
    42 00 08 a8 f4 49 e0 00 04:32:38.652 READ VERIFY SECTOR(S) EXT


    Error 118 occurred at disk power-on lifetime: 14556 hours (606 days + 12 hours)
    When the command that caused the error occurred, the device was active or idle.


    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 51 02 ae f4 49 e0 Error: UNC at LBA = 0x0049f4ae = 4846766


    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    42 00 04 ac f4 49 e0 00 04:32:41.155 READ VERIFY SECTOR(S) EXT
    42 00 04 a8 f4 49 e0 00 04:32:41.146 READ VERIFY SECTOR(S) EXT
    42 00 08 a8 f4 49 e0 00 04:32:41.130 READ VERIFY SECTOR(S) EXT
    42 00 08 a0 f4 49 e0 00 04:32:39.878 READ VERIFY SECTOR(S) EXT
    42 00 10 b0 f4 49 e0 00 04:32:38.652 READ VERIFY SECTOR(S) EXT


    Error 117 occurred at disk power-on lifetime: 14556 hours (606 days + 12 hours)
    When the command that caused the error occurred, the device was active or idle.


    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 51 02 ae f4 49 e0 Error: UNC at LBA = 0x0049f4ae = 4846766


    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    42 00 08 a8 f4 49 e0 00 04:32:41.155 READ VERIFY SECTOR(S) EXT
    42 00 08 a0 f4 49 e0 00 04:32:41.146 READ VERIFY SECTOR(S) EXT
    42 00 10 b0 f4 49 e0 00 04:32:41.130 READ VERIFY SECTOR(S) EXT
    42 00 10 a0 f4 49 e0 00 04:32:39.878 READ VERIFY SECTOR(S) EXT
    42 00 20 a0 f4 49 e0 00 04:32:38.652 READ VERIFY SECTOR(S) EXT


    Error 116 occurred at disk power-on lifetime: 14556 hours (606 days + 12 hours)
    When the command that caused the error occurred, the device was active or idle.


    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    40 51 02 ae f4 49 e0 Error: UNC at LBA = 0x0049f4ae = 4846766


    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    42 00 10 a0 f4 49 e0 00 04:32:36.061 READ VERIFY SECTOR(S) EXT
    42 00 20 a0 f4 49 e0 00 04:32:36.060 READ VERIFY SECTOR(S) EXT
    42 00 20 80 f4 49 e0 00 04:32:36.058 READ VERIFY SECTOR(S) EXT
    42 00 40 80 f4 49 e0 00 04:32:39.878 READ VERIFY SECTOR(S) EXT
    42 00 40 40 f4 49 e0 00 04:32:38.652 READ VERIFY SECTOR(S) EXT


    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Short captive Completed: unknown failure 90% 14546 16453020
    # 2 Short offline Completed: unknown failure 90% 14546 325795665
    # 3 Short offline Completed: unknown failure 90% 14546 171868828
    # 4 Short offline Completed: unknown failure 90% 14388 33069049
    # 5 Short captive Completed: unknown failure 90% 14388 16453020
    # 6 Short offline Completed without error 00% 0 -


    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.


    frank@frank-ThinkCentre-M71e:~$
      My ComputerSystem Spec
  4.    14 Apr 2015 #14
    Join Date : Mar 2015
    Athens
    Posts : 96
    Windows 10 Pro 64bit build 14393

    Quote Originally Posted by silv55 View Post
    Code:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x000f   117   073   006    Pre-fail  Always       -       0
      3 Spin_Up_Time            0x0003   097   094   070    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       471
      5 Reallocated_Sector_Ct   0x0033   001   001   036    Pre-fail  Always   FAILING_NOW 57106
      7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       296546108
      9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14608
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       449
    187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       65535
    189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
    190 Airflow_Temperature_Cel 0x0022   067   038   045    Old_age   Always   In_the_past 33 (33 104 34 33 0)
    194 Temperature_Celsius     0x0022   033   062   000    Old_age   Always       -       33 (0 13 0 0 0)
    195 Hardware_ECC_Recovered  0x001a   076   045   000    Old_age   Always       -       225328440
    197 Current_Pending_Sector  0x0012   095   094   000    Old_age   Always       -       116
    198 Offline_Uncorrectable   0x0010   095   094   000    Old_age   Offline      -       116
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       4
    200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
    202 Data_Address_Mark_Errs  0x0032   055   208   000    Old_age   Always       -       45
    Yes, the Disk has a serious problem and it will likely fail in future. When exactly, nobody can say. Here are the attributes indicating the failure.
    Code:
      5 Reallocated_Sector_Ct   0x0033   001   001   036    Pre-fail  Always   FAILING_NOW 57106
      7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       296546108
    197 Current_Pending_Sector  0x0012   095   094   000    Old_age   Always       -       116
    When the reallocated sectors exhausted the Disk will stop functioning.
      My ComputerSystem Spec
  5.    14 Apr 2015 #15
    Join Date : Feb 2015
    Posts : 111
    Win 10 Preview
    Thread Starter

    Quote Originally Posted by NickTh View Post
    Yes, the Disk has a serious problem and it will likely fail in future. When exactly, nobody can say. Here are the attributes indicating the failure.
    Code:
      5 Reallocated_Sector_Ct   0x0033   001   001   036    Pre-fail  Always   FAILING_NOW 57106
      7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       296546108
    197 Current_Pending_Sector  0x0012   095   094   000    Old_age   Always       -       116
    When the reallocated sectors exhausted the Disk will stop functioning.

    Thanks Nickth; well i'll use it till it fails, i installed it with UBUNTU 14.04 and it doesn't show any symptoms of failure at this time,
    i put the HDD with Win10 aside and will try when RTM comes along and see what will happen if i have to pay much money,no way, since i only stream and browse and Ubuntu 14.04, is better for me then any Windows OPS, just my opinion.
      My ComputerSystem Spec

 
Page 2 of 2 FirstFirst 12


Similar Threads
Thread Forum
disk storage
This is a odd one for even a support geek like me. For some reason windows 10 is reporting my total storage as 983gb and that all 983 has been used up even though I deleted a bunch of stuff and uninstalled some programs. I might add i also have a...
Drivers and Hardware
Solved Error on shutdown concerning explore.exe Application Error
Upon every shutdown I get the following error message: The title bar states: I am running Windows 10 Build 10130. I have already tried the default troubleshooting procedures(clean boot, etc.) I attached an image of the error below: ...
General Support
W10 Disk Image Utility Reports Error After Image Creation.
I installed the 32 bit version of W10 on an old Acer laptop to get back up to speed with developments, and one of the first questions or issues that cropped up is when using W10's disk image utility to make a system image. I deliberately wished to...
General Support
Upgrade to 10122 gets error fbl_impressive Professional 10122 - Error
I upgraded to 10074 with no problems but trying to upgrade to 10122 gets error fbl_impressive Professional 10122 - Error 0xd0000225. I'm logged into my Microsoft account, so I don't think that's the problem. I've cleaned up all the files and...
Installation and Upgrade
Solved File explorer Error Its OK my error
Error -- looking in wrong directory cheers jimbo
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:38.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums