Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[Solved] GSmart Partition Error on Install?

Post Reply
Message
Author
rej
Forum Regular
Forum Regular
Posts: 149
Joined: Thu Mar 09, 2017 11:11 pm

[Solved] GSmart Partition Error on Install?

#1 Post by rej » Tue Jul 10, 2018 6:51 am

Upon installation, there is a box indicating that Gsmart has determined that the partition will fail whether installing MX or antiX.

This drive is new.

After running the GSmart extended test, Western Digital Lifeguard extended test, Seatools extended test, Christaldiskinfo and about 8 other tests, there were no errors at all. All passed. The WD and ST tests were each 3-4 hours long.

Yet there is still the notification every time on installation.

Two times on other drives, this notification turned out to be accurate.

Are there other reasons for this to be occurring?

[This is unrelated to my other post regarding MX update - that PC has no update issues]

Thank you.
Last edited by rej on Sat Jul 14, 2018 9:16 am, edited 1 time in total.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1156
Joined: Wed Apr 11, 2018 5:09 pm

Re: GSmart Partition Error on Install?

#2 Post by fehlix » Tue Jul 10, 2018 12:32 pm

rej wrote:
Tue Jul 10, 2018 6:51 am
Upon installation, there is a box indicating that Gsmart has determined that the partition will fail whether installing MX or antiX.
You can use from the cli the command the installer checks the health-status of the device:

Code: Select all

smartctl -H "your-devicename-here" 
According to smartctl's man-page:

If the device reports failing health status, this means either that the device has already failed, or that it
is predicting its own failure within the next 24 hours. If this happens, use the ´-a´ option to get more
information, and get your data off the disk and to someplace safe as soon as you can
Or here a bit more:

Code: Select all

 man smartctl | sed -n '/--health/,/ log\./p'
       -H, --health
              Prints the health status of the device or pending TapeAlert messages.

              If  the device reports failing health status, this means either that the device has already failed, or that it
              is predicting its own failure within the next 24 hours.  If this happens, use the  ´-a´  option  to  get  more
              information, and get your data off the disk and to someplace safe as soon as you can.

              [ATA]  Health status is obtained by checking the (boolean) result returned by the SMART RETURN STATUS command.
              The return value of this ATA command may be unknown due to limitations or bugs in some layer (e.g.  RAID  con‐
              troller  or  USB  bridge firmware) between disk and operating system.  In this case, smartctl prints a warning
              and checks whether any Prefailure SMART Attribute value is less than or  equal  to  its  threshold  (see  ´-A´
              below).

              [SCSI]  Health status is obtained by checking the Additional Sense Code (ASC) and Additional Sense Code Quali‐
              fier (ASCQ) from Informal Exceptions (IE) log page (if supported) and/or from SCSI sense data.

              [SCSI tape drive or changer] TapeAlert status is obtained by reading the TapeAlert log page.  Please note that
              the  TapeAlert log page flags are cleared for the initiator when the page is read.  This means that each alert
              condition is reported only once by smartctl for each initiator for each activation of the condition.

              [NVMe] [FreeBSD, Linux, Windows and Cygwin only] [NEW EXPERIMENTAL SMARTCTL FEATURE] NVMe status  is  obtained
              by reading the "Critical Warning" byte from the SMART/Health Information log.
You might check the drive on another computer to be sure about the reported status.

rej
Forum Regular
Forum Regular
Posts: 149
Joined: Thu Mar 09, 2017 11:11 pm

Re: GSmart Partition Error on Install?

#3 Post by rej » Sat Jul 14, 2018 9:15 am

Hi fehlix -

Thanks! Did not know about this terminal option.

Went to the smartctl website and was able to get a lot of information.

The command you gave indicated "passed".

Ran the GSmart Control "Extended self-test" again and the "Conveyance self-test" - both passed.

I will trust that the drive is OK. Don't know why MX install is indicating otherwise. Was best to check it out though.

Thanks again.

User avatar
Adrian
Forum Veteran
Forum Veteran
Posts: 8699
Joined: Wed Jul 12, 2006 1:42 am

Re: [Solved] GSmart Partition Error on Install?

#4 Post by Adrian » Sat Jul 14, 2018 9:52 am

There are two commands that are run by the installer:
smartctl -H your-device-here|grep -w FAILED

And then if that passes it runs this to check for some specific errors:
smartctl -A your-device-here | grep -E "^ 5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'

You should see some errors if you run these commands if the installer reports problems.

rej
Forum Regular
Forum Regular
Posts: 149
Joined: Thu Mar 09, 2017 11:11 pm

Re: [Solved] GSmart Partition Error on Install?

#5 Post by rej » Tue Jul 17, 2018 12:24 pm

Thank you, Adrian.

Since running these commands, I have been trying to determine what the results mean. Particularly the results of "smartctl -A /dev/sda".

The "196 Reallocated_Event_Count 0x000f 100 100 030 Pre-fail Always - 492 (53962 0)", also appears in smartctl -A /dev/sda | grep -E "^ 5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'.

Specifics of "-A" on the smartctl site, with my current knowledge, are not clear to me.

Re-tested 12 other hard drives of various usage with these 2 commands. One of these, "new" - purchased months ago, had failed the WesternDigital Lifeguard extended test and repaired it by reallocating sectors, which did not appear in its "smartctl -A" results. All 12 passed - including a 1T WD drive that has confirmed irrepairable read errors.

The particular hard drive, that prompted this post, purchased as "new" a few months ago, tested thoroughly when arrived, never used, sitting motionless on a shelf since then, maybe is not "new" at all.

Cloned the drive and will use that if it fails.

Thanks again. Would need to look into this much more in-depth to make sense of it.
__________________________________________________
root@mx17:/home/rj# smartctl -H /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

____________________________

root@mx17:/home/rj# smartctl -A /dev/sda | grep -E "^ 5|^196|^197|^198" | awk '{ if ( $10 != 0 ) { print $1,$2,$10} }'
196 Reallocated_Event_Count 494
____________________________

rj@mx17.1:~
$ sudo smartctl -A /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
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 118 100 034 Pre-fail Always - 181950720
3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 392
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 5351155
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 495 (193 106 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 392
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 3
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 059 048 045 Old_age Always - 41 (Min/Max 30/41)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 2
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 39
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 842
194 Temperature_Celsius 0x0022 041 052 000 Old_age Always - 41 (0 18 0 0 0)
196 Reallocated_Event_Count 0x000f 100 100 030 Pre-fail Always - 492 (53962 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 9
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0

User avatar
m_pav
Forum Guide
Forum Guide
Posts: 2659
Joined: Sun Aug 06, 2006 3:02 pm

Re: [Solved] GSmart Partition Error on Install?

#6 Post by m_pav » Thu Jul 19, 2018 3:22 am

S.M.A.R.T attribute numbers can be easily read and explained, so keeping to the simplest items......

4 = how many times the drive has started and stopped. Compare with Attribute 12 and 193 to get a picture of how the drive was used.

5 = the count of reallocated sectors. Every spinning platter drive had reserved space for reallocated sectors, yours has reservations for 36 before the drive should be replaced and it's current count is 0, so nothing has been reallocated. That can be both a good or a bad thing, depending on what the numbers say in other areas.

9 = the raw "power on value" in completed hours, yours has done a full 495 operational hours, so it's not new by any stretch.

12 = how many times the drive has been powered up. This coupled with Attribute 4 above shows the drive was almost fully utilised every time it was powered up and when checked against attribute 9, it shows the average run time per power on was about 1H 15m and 40s and based on 193, on average, it spun down roughly 2.15 times per power-on cycle. To me, that looks like it was a backup drive that had the power disconnected 39 times while the drive was still active, taken from 192.

190 = the temperature, both current and maximum. Yours has reached 41C, the maximum recommended temp for safe operation is 42C. Converted to Fahrenheit, that's 105.8F with a threshold of 107.6F.

191 = the number of significant bumps the drive has encountered during its lifetime, usually resulting in a sudden head retraction to avoid surface contact.

196 = how many times the drive has attempted to reallocate damaged sectors.
197 = the number of sectors that have potential faults which either being monitored, or have not yet been reallocated, or marked as clean.
198 = the number of faulty sectors which have been marked as unusable
254 = how many times the drive has been in a free-fall, yours is 0.

There are many others, but I've already said enough so I'll stop at this.

Attributes from 194-198 are the ones that really determine whether a drive is good or not. Usually, for attributes 195-198, any value other than 0 indicate a damaged drive. It has been my experience that a Windows system with any value other than a 0 in 195-198 will have had some type of read/write fault resulting in lost data and they are usually broken in some point. Often a value of 3 or more will have had a windows system suddenly crash. On the other hand, I've seen Linux continue almost flawlessly for 18 months because it doesn't thrash the disk like Windows does.

196 on your system has 2 results, it shows both 492 and a bracketed number. That is usually a manufacturer added customisation matched to their particular disk health application, e.g. Seagate, Western Digital, Toshiba or Lenovo proprietary tool reads this value and obtains the correct value, which has been adapted from the original,but a generic standards based tool like smartctl gets a flawed result.

This is most likely where your error code is being pulled from. It can read the 492, but it can't interpret the bracketed value.
Mike P

Regd Linux User #472293
(Mine)Lenovo T560, i7-6600U, 16GB, 2.0TB SSHD, MX17 64-bit
(Wifes) Asus M4A88TD-M, AMD Phenom II x4 955 CPU, nVidia GF610, 6Gb, 500GB+320GB, MX17 + KDE
(Kids) Intel NUC, J1900, 4GB, 64GB SSD, MX17

rej
Forum Regular
Forum Regular
Posts: 149
Joined: Thu Mar 09, 2017 11:11 pm

Re: [Solved] GSmart Partition Error on Install?

#7 Post by rej » Fri Jul 20, 2018 2:53 pm

m_pav-

Thank you!! This is extremely helpful - the most important details in understandable terms.

This certainly proves to be the best program to run on a newly purchased drive. Only takes a minute for all that information.

I really appreciate your time and effort put into explaining this. Especially well laid out, making it easier to follow the rest of it and information on the smartctl site.

Thanks again.

User avatar
m_pav
Forum Guide
Forum Guide
Posts: 2659
Joined: Sun Aug 06, 2006 3:02 pm

Re: [Solved] GSmart Partition Error on Install?

#8 Post by m_pav » Sat Jul 21, 2018 4:32 am

You don't have to use the command line version, GSmartControl is a GUI version and it's installed by default. Once you've selected your drive it will read the S.M.A.R.T data and present it to you in a very nice GUI. Click on the Attibutes tab and pause your mouse over any attribute to see a description of its purpose.

When I had an IT repair shop, I wouldn't work on any Windows machine without first checking the drives S.M.A.R.T data, especially on all Toshiba laptops with a 650GB HDD becasue I couldn't see the point of operating on faulty hardware.
Mike P

Regd Linux User #472293
(Mine)Lenovo T560, i7-6600U, 16GB, 2.0TB SSHD, MX17 64-bit
(Wifes) Asus M4A88TD-M, AMD Phenom II x4 955 CPU, nVidia GF610, 6Gb, 500GB+320GB, MX17 + KDE
(Kids) Intel NUC, J1900, 4GB, 64GB SSD, MX17

rej
Forum Regular
Forum Regular
Posts: 149
Joined: Thu Mar 09, 2017 11:11 pm

Re: [Solved] GSmart Partition Error on Install?

#9 Post by rej » Sat Jul 21, 2018 1:29 pm

Mike P-

This is great - the GUI version is quick and the hovering feature is very handy.

Thank you!

Post Reply

Return to “Software / Configuration”