Hi Matt,
The ext4 don't have data checksum, but have metadata checksum, which would
probably be corrupted as well, as I reinstalled my Linux over the same
partition the FreeBSD was using, and by
now I have a lot more files on it than I had on FreeBSD.
If you look at the forum post I created, you'll see that I ran the command
smartctl as well, and it shows that there's no problem with the SSD, it's a
new SDD, some months of use.
I ran the command inside FreeBSD:
=== START OF INFORMATION SECTION ===
Model Family: WD Blue and Green SSDs
Device Model: WDC WDS480G2G0B-00EPW0
Serial Number: 183541800480
LU WWN Device Id: 5 001b44 8b9628e44
Firmware Version: UK450000
User Capacity: 480.113.590.272 bytes [480 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: M.2
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Sep 2 12:34:29 2019 -03
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: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 32) The self-test routine was interrupted
by the host with a hard or soft reset.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x15) SMART execute Offline immediate.
No Auto Offline data collection support.
Abort Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No 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: ( 85) minutes.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0032 100 100 000 Old_age
Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age
Always - 3281
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 570
165 Block_Erase_Count 0x0032 100 100 000 Old_age
Always - 1025
166 Minimum_PE_Cycles_TLC 0x0032 100 100 --- Old_age
Always - 7
167 Max_Bad_Blocks_per_Die 0x0032 100 100 --- Old_age
Always - 0
168 Maximum_PE_Cycles_TLC 0x0032 100 100 --- Old_age
Always - 15
169 Total_Bad_Blocks 0x0032 100 100 --- Old_age
Always - 204
170 Grown_Bad_Blocks 0x0032 100 100 --- Old_age
Always - 0
171 Program_Fail_Count 0x0032 100 100 000 Old_age
Always - 0
172 Erase_Fail_Count 0x0032 100 100 000 Old_age
Always - 0
173 Average_PE_Cycles_TLC 0x0032 100 100 000 Old_age
Always - 7
174 Unexpected_Power_Loss 0x0032 100 100 000 Old_age
Always - 112
184 End-to-End_Error 0x0032 100 100 --- Old_age
Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age
Always - 2
188 Command_Timeout 0x0032 100 100 --- Old_age
Always - 0
194 Temperature_Celsius 0x0022 063 053 000 Old_age
Always - 37 (Min/Max 6/53)
199 UDMA_CRC_Error_Count 0x0032 100 100 --- Old_age
Always - 0
230 Media_Wearout_Indicator 0x0032 100 100 000 Old_age
Always - 0x025c0128025c
232 Available_Reservd_Space 0x0033 100 100 005 Pre-fail
Always - 100
233 NAND_GB_Written_TLC 0x0032 100 100 --- Old_age
Always - 3227
234 NAND_GB_Written_SLC 0x0032 100 100 000 Old_age
Always - 11545
241 Total_Host_GB_Written 0x0030 100 100 000 Old_age
Offline - 4632
242 Total_Host_GB_Read 0x0030 100 100 000 Old_age
Offline - 4956
244 Temp_Throttle_Status 0x0032 000 100 --- Old_age
Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Short offline Aborted by host 90% 3166 -
# 2 Short offline Completed without error 00% 2522 -
# 3 Short offline Interrupted (host reset) 90% 2070 -
# 4 Short offline Interrupted (host reset) 90% 2040 -
# 5 Short offline Interrupted (host reset) 90% 2011 -
# 6 Short offline Interrupted (host reset) 90% 2011 -
# 7 Short offline Aborted by host 80% 2011 -
# 8 Short offline Completed without error 00% 624 -
# 9 Short offline Aborted by host 30% 433 -
#10 Short offline Aborted by host 90% 401 -
#11 Short offline Completed without error 00% 400 -
#12 Short offline Completed without error 00% 321 -
#13 Short offline Completed without error 00% 106 -
#14 Short offline Self-test routine in progress 20% 106 -
#15 Short offline Aborted by host 90% 11 -
Selective Self-tests/Logging not supported
Em seg., 24 de fev. de 2020 às 16:50, Matt Garber <matt.gar...@gmail.com>
escreveu:
> On Mon, Feb 24, 2020 at 2:44 PM Mario Olofo <mario.ol...@gmail.com> wrote:
>
>> Hi Pete, in the logs there's nothing wrong, I only see the problem on
>> zpool
>> status after the first scrub, even if I just
>> reinstall the FreeBSD and some basic packages (didn't even need a lot of
>> files as I thought).
>
>
> Mario,
>
> Out of curiosity, how are you able to tell for sure you aren’t also
> experiencing corruption under Linux or Windows on the same hardware? Have
> you been able to run a ZFS scrub using ZFS on Linux?
>
> Both default file systems, ext4 and NTFS, are completely unable of letting
> you know if corruption has occurred — they’ll just corrupt silently — so
> I’m wondering how you’ve ruled that out.
>
>
> Thanks,
> —
> Matt
>
>
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
