From nobody Sun Oct 16 16:51:00 2022 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Mr5jv1ljVz4fbxw for ; Sun, 16 Oct 2022 16:51:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mr5jt0tjPz3mlc for ; Sun, 16 Oct 2022 16:51:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ed1-x529.google.com with SMTP id r14so13018248edc.7 for ; Sun, 16 Oct 2022 09:51:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9WEplfKO6IAzUgGYX9/0MjDaBzD3LzYoDLxWzqrHjc4=; b=xmDZfWaIqbklUq3EcVEr4j/X565WgTAFe+yXm0K/x3VEQHPMZdX7CmhnSViymA3n3n vi7EaZrPwj7rHA9B5Cwkcwc5+FtVo4feekqzxYPnCgbFjmS1dzRKtt9rFR0uTdd0++Fp gkghslo6cHUw9aHfQrRZTHH3Njf5N8nWjc9rZqN+mmZgBNwr3tM0sQBL/B5bDi/YNcAB D9hns63bivlhygmuK17r3/vkrUlTEyxFhBtNpI3YY4yDo0Z2fuy8fm7sYQQsdTMyBJCG tD9yu9t8I1Gaswuw1qosVCC1m+EhDBmGfxFwa2B1Ts0av+MWR5flX4oYdpmMbG97ckjz eZIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9WEplfKO6IAzUgGYX9/0MjDaBzD3LzYoDLxWzqrHjc4=; b=pRoPtuqXC4Ux7SgJNTClhVGkB4GuBadONaWt7zaY+zvTctpSY2JhaHJSBlxeY410Br 4hxw1qO2EOQLNpG+BuoTgFFLRVdrfJ9Ys0pDKBuYdzalVpspxrRWe9YwUa00+wXJq+H0 KKh8SqcUuRhjiFGaD2PEDjeY8QS1ruJ20jY+81AATYfcikwrjJD8bPAVlZqgj1nilaCq CZFW03b+M+c8BkR0KqUpyGITbP+95MuI+1kiDkUz7XUaH3qrBSBbdJtkNA7vouY9r0he JgejMNwboHjL18FYKxNlbllBj3pY53Fowf3+r6g9KaYaQFqcg7tfwmPTu78HvAV0MA4M geJw== X-Gm-Message-State: ACrzQf3rcze9CiLnvsyLkGkLLvx3gaXc2f5fYIN3CT1ZHbGJ2P37Chak /4sp+qlihyJB6be2pGDoUEKjPb0drZUgrcqwky0syA== X-Google-Smtp-Source: AMsMyM6RzE+Yacnl8wdUtYejeLd5p0kQgpqPCF2eo0Ju7hBZ7mydZWDzhRuptGKWJeJnGOHFGj/AZ1aY2DVvvtiNZaA= X-Received: by 2002:a05:6402:2687:b0:45d:3a94:348f with SMTP id w7-20020a056402268700b0045d3a94348fmr6795028edd.48.1665939072062; Sun, 16 Oct 2022 09:51:12 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 References: <1625dc7b-81c4-4350-8f86-1b65f5a860d9@app.fastmail.com> <64a0af42-630d-4f42-8b8c-921b68b03078@app.fastmail.com> In-Reply-To: <64a0af42-630d-4f42-8b8c-921b68b03078@app.fastmail.com> From: Warner Losh Date: Sun, 16 Oct 2022 10:51:00 -0600 Message-ID: Subject: Re: zfs with operations like rm -rf takes a very long time recently To: void Cc: freebsd-fs Content-Type: multipart/alternative; boundary="0000000000009baec005eb29aabc" X-Rspamd-Queue-Id: 4Mr5jt0tjPz3mlc X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=xmDZfWaI; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::529) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.997]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_TO(0.00)[f-m.fm]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::529:from]; DMARC_NA(0.00)[bsdimp.com]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --0000000000009baec005eb29aabc Content-Type: text/plain; charset="UTF-8" On Sun, Oct 16, 2022 at 10:41 AM void wrote: > On Sun, 16 Oct 2022, at 16:07, Alan Somers wrote: > > Gstat is showing that your disk is fully busy. It's also showing read > > latency as high as 128 ms, which is extremely slow. > > I ran another gstat with -I 5s and have omitted -d as > per your last email. How did you calculate latency? > > There's zfs-stats installed too. Would pasting some output here be useful? > > # gstat -opC -I 5s > > timestamp,name,q-depth,total_ops/s,read/s,read-KiB/s,ms/read,write/s,write-KiB/s,ms/write,other/s,ms/other,%busy > 2022-10-16 17:23:47.080118413,da0,3,0,0,0,0.0,0,0,0.0,0,0.0,0.0 > 2022-10-16 > 17:23:52.088745392,da0,4,93,45,246,26.4,49,3974,12.7,0,154.4,97.8 > 2022-10-16 > 17:23:57.167503039,da0,3,82,41,164,25.5,40,3193,17.3,1,153.2,99.2 > 2022-10-16 > 17:24:02.176759152,da0,3,81,43,176,22.8,38,2704,13.3,0,252.6,98.6 > 2022-10-16 > 17:24:07.189364538,da0,2,90,35,140,27.9,55,3371,15.9,1,146.9,99.4 > 2022-10-16 > 17:24:12.190874083,da0,3,95,42,170,23.3,52,3486,13.2,0,167.0,96.6 > 2022-10-16 > 17:24:17.212769876,da0,4,85,33,134,30.6,52,3508,22.3,1,164.9,100.7 > 2022-10-16 > 17:24:22.286986167,da0,3,89,42,168,23.2,46,3149,12.7,1,127.3,97.2 > 2022-10-16 > 17:24:27.295992137,da0,3,88,40,160,25.4,48,3978,15.6,0,147.4,101.3 > 2022-10-16 > 17:24:32.406662934,da0,2,90,46,254,27.1,44,3554,12.9,0,159.3,97.9 > 2022-10-16 > 17:24:37.426033077,da0,3,87,42,177,23.3,45,2835,15.4,1,112.8,98.0 > 2022-10-16 > 17:24:42.455203661,da0,3,95,43,170,23.1,52,3770,11.9,0,153.5,98.8 > 2022-10-16 > 17:24:47.468741642,da0,3,71,36,144,27.9,35,2510,19.7,1,243.7,99.3 > 2022-10-16 > 17:24:52.471973107,da0,3,80,34,138,29.1,46,3630,17.6,0,266.6,99.2 > 2022-10-16 > 17:24:57.490425268,da0,3,79,35,141,28.1,43,3372,18.6,1,297.8,98.3 > 2022-10-16 > 17:25:02.589730547,da0,4,68,30,123,32.7,36,2318,22.4,3,105.2,97.9 > ^C > Your disk is doing ~90 IOPs. ~60 read ~30 write with an average queue depth of 4, and a 95+% busy factor (which is kinda misleading, but in this case not so much). So a crapton of traffic to the disk is making the disk slow. Why that's happening, I'm unsure, but your disk is slow because it's fairly loaded. I'm not sure what the 'other operations' are that aren't read, write or trim. At a guess, I'd say that's BIO_FLUSH slowing things down a bit (but not a huge amount). > > I suspect a > > problem with your disk. FYI, ZFS naturally has a 5-second rhythm > > (unless you changed vfs.zfs.txg.timeout), > > # sysctl vfs.zfs.txg.timeout > vfs.zfs.txg.timeout: 5 > > > so gstat's output is > > sometimes more consistent if you use "-I 5s". You can also omit "-d" > > for magnetic HDDs, since they don't have anything like TRIM. > > > I suggest checking dmesg to see if there are any messages about errors > > from da0. It would also be worth running "smartctl -a /dev/da0", from > > sysutils/smartmontools. > > Unfortunately, no errors seen in either dmesg or smartctl. there's been a > long smartctl test relatively recently, also came back clean. > > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining > LifeTime(hours) LBA_of_first_error > # 1 Short offline Completed without error 00% 39253 > - > # 2 Extended offline Completed without error 00% 39176 > - > # 3 Short offline Completed without error 00% 39172 > - > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED > WHEN_FAILED RAW_VALUE > 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always > - 0 > 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline > - 0 > 3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always > - 2595 > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always > - 1487 > 5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always > - 0 > 7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always > - 0 > 8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline > - 0 > 9 Power_On_Hours 0x0032 002 002 000 Old_age Always > - 39254 > 10 Spin_Retry_Count 0x0033 128 100 030 Pre-fail Always > - 0 > 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always > - 1263 > 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always > - 4 > 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always > - 426 > 193 Load_Cycle_Count 0x0032 029 029 000 Old_age Always > - 710616 > 194 Temperature_Celsius 0x0022 100 100 000 Old_age Always > - 54 (Min/Max 16/65) > 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always > - 0 > 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always > - 0 > 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline > - 0 > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always > - 0 > 220 Disk_Shift 0x0002 100 100 000 Old_age Always > - 0 > 222 Loaded_Hours 0x0032 075 075 000 Old_age Always > - 10367 > 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always > - 0 > 224 Load_Friction 0x0022 100 100 000 Old_age Always > - 0 > 226 Load-in_Time 0x0026 100 100 000 Old_age Always > - 260 > 240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline > - 0 > > SMART Error Log Version: 1 > No Errors Logged > The only thing that looks high here is the load cycle count and maybe the power off retract count. With 40k power on hours, that's a power off every 90 hours? That seems a little weird. And the load cycle is almost 20 times the power on hours, suggesting it's going on every few minutes. That's higher than I'd expect as well. The power cycle count is also high for the number of hours. Your disk is pushing 4 years old too, which may mean its past expected life. So this profile suggests possible signs of fatigue. Warner --0000000000009baec005eb29aabc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Oct 16, 2022 at 10:41 AM void= <void@f-m.fm> wrote:
On Sun, 16 Oct 2022, at 16:0= 7, Alan Somers wrote:
> Gstat is showing that your disk is fully busy.=C2=A0 It's also sho= wing read
> latency as high as 128 ms, which is extremely slow.=C2=A0

I ran another gstat with -I 5s and have omitted -d as
per your last email. How did you calculate latency?

There's zfs-stats installed too. Would pasting some output here be usef= ul?

# gstat -opC -I 5s
timestamp,name,q-depth,total_ops/s,read/s,read-KiB/s,ms/read,write/s,write-= KiB/s,ms/write,other/s,ms/other,%busy
2022-10-16 17:23:47.080118413,da0,3,0,0,0,0.0,0,0,0.0,0,0.0,0.0
2022-10-16 17:23:52.088745392,da0,4,93,45,246,26.4,49,3974,12.7,0,154.4,97.= 8
2022-10-16 17:23:57.167503039,da0,3,82,41,164,25.5,40,3193,17.3,1,153.2,99.= 2
2022-10-16 17:24:02.176759152,da0,3,81,43,176,22.8,38,2704,13.3,0,252.6,98.= 6
2022-10-16 17:24:07.189364538,da0,2,90,35,140,27.9,55,3371,15.9,1,146.9,99.= 4
2022-10-16 17:24:12.190874083,da0,3,95,42,170,23.3,52,3486,13.2,0,167.0,96.= 6
2022-10-16 17:24:17.212769876,da0,4,85,33,134,30.6,52,3508,22.3,1,164.9,100= .7
2022-10-16 17:24:22.286986167,da0,3,89,42,168,23.2,46,3149,12.7,1,127.3,97.= 2
2022-10-16 17:24:27.295992137,da0,3,88,40,160,25.4,48,3978,15.6,0,147.4,101= .3
2022-10-16 17:24:32.406662934,da0,2,90,46,254,27.1,44,3554,12.9,0,159.3,97.= 9
2022-10-16 17:24:37.426033077,da0,3,87,42,177,23.3,45,2835,15.4,1,112.8,98.= 0
2022-10-16 17:24:42.455203661,da0,3,95,43,170,23.1,52,3770,11.9,0,153.5,98.= 8
2022-10-16 17:24:47.468741642,da0,3,71,36,144,27.9,35,2510,19.7,1,243.7,99.= 3
2022-10-16 17:24:52.471973107,da0,3,80,34,138,29.1,46,3630,17.6,0,266.6,99.= 2
2022-10-16 17:24:57.490425268,da0,3,79,35,141,28.1,43,3372,18.6,1,297.8,98.= 3
2022-10-16 17:25:02.589730547,da0,4,68,30,123,32.7,36,2318,22.4,3,105.2,97.= 9
^C

Your disk is doing ~90 IOPs. ~60 rea= d ~30 write with an average queue depth of
4, and a 95+% busy fac= tor (which is kinda misleading, but in this case not so much).
So a crapton of traffic to the disk is making the disk slow.= =C2=A0 Why that's happening, I'm unsure,
but your disk is= slow because it's fairly loaded. I'm not sure what the 'other = operations'
are that aren't read, write or trim. At a gue= ss, I'd say that's BIO_FLUSH slowing things
down a bit (b= ut not a huge amount).
=C2=A0
> I suspect a
> problem with your disk.=C2=A0 FYI, ZFS naturally has a 5-second rhythm=
> (unless you changed vfs.zfs.txg.timeout),

# sysctl vfs.zfs.txg.timeout
vfs.zfs.txg.timeout: 5

> so gstat's output is
> sometimes more consistent if you use "-I 5s".=C2=A0 You can = also omit "-d"
> for magnetic HDDs, since they don't have anything like TRIM.

> I suggest checking dmesg to see if there are any messages about errors=
> from da0.=C2=A0 It would also be worth running "smartctl -a /dev/= da0", from
> sysutils/smartmontools.

Unfortunately, no errors seen in either dmesg or smartctl. there's been= a long smartctl test relatively recently, also came back clean.

SMART Self-test log structure revision number 1
Num=C2=A0 Test_Description=C2=A0 =C2=A0 Status=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Remaining=C2=A0 LifeTime(hours)=C2=A0 LB= A_of_first_error
# 1=C2=A0 Short offline=C2=A0 =C2=A0 =C2=A0 =C2=A0Completed without error= =C2=A0 =C2=A0 =C2=A0 =C2=A000%=C2=A0 =C2=A0 =C2=A039253=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0-
# 2=C2=A0 Extended offline=C2=A0 =C2=A0 Completed without error=C2=A0 =C2= =A0 =C2=A0 =C2=A000%=C2=A0 =C2=A0 =C2=A039176=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0-
# 3=C2=A0 Short offline=C2=A0 =C2=A0 =C2=A0 =C2=A0Completed without error= =C2=A0 =C2=A0 =C2=A0 =C2=A000%=C2=A0 =C2=A0 =C2=A039172=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0-

ID# ATTRIBUTE_NAME=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 FLAG=C2=A0 =C2=A0 =C2= =A0VALUE WORST THRESH TYPE=C2=A0 =C2=A0 =C2=A0 UPDATED=C2=A0 WHEN_FAILED RA= W_VALUE
=C2=A0 1 Raw_Read_Error_Rate=C2=A0 =C2=A0 =C2=A00x000b=C2=A0 =C2=A0100=C2= =A0 =C2=A0100=C2=A0 =C2=A0050=C2=A0 =C2=A0 Pre-fail=C2=A0 Always=C2=A0 =C2= =A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 2 Throughput_Performance=C2=A0 0x0005=C2=A0 =C2=A0100=C2=A0 =C2=A010= 0=C2=A0 =C2=A0050=C2=A0 =C2=A0 Pre-fail=C2=A0 Offline=C2=A0 =C2=A0 =C2=A0 -= =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 3 Spin_Up_Time=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0027=C2=A0= =C2=A0100=C2=A0 =C2=A0100=C2=A0 =C2=A0001=C2=A0 =C2=A0 Pre-fail=C2=A0 Alwa= ys=C2=A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A02595
=C2=A0 4 Start_Stop_Count=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0032=C2=A0 =C2=A0100= =C2=A0 =C2=A0100=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2= =A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A01487
=C2=A0 5 Reallocated_Sector_Ct=C2=A0 =C2=A00x0033=C2=A0 =C2=A0100=C2=A0 =C2= =A0100=C2=A0 =C2=A0050=C2=A0 =C2=A0 Pre-fail=C2=A0 Always=C2=A0 =C2=A0 =C2= =A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 7 Seek_Error_Rate=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00x000b=C2=A0 =C2= =A0100=C2=A0 =C2=A0100=C2=A0 =C2=A0050=C2=A0 =C2=A0 Pre-fail=C2=A0 Always= =C2=A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 8 Seek_Time_Performance=C2=A0 =C2=A00x0005=C2=A0 =C2=A0100=C2=A0 =C2= =A0100=C2=A0 =C2=A0050=C2=A0 =C2=A0 Pre-fail=C2=A0 Offline=C2=A0 =C2=A0 =C2= =A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 9 Power_On_Hours=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0032=C2=A0 =C2= =A0002=C2=A0 =C2=A0002=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Alw= ays=C2=A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A039254
=C2=A010 Spin_Retry_Count=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0033=C2=A0 =C2=A0128= =C2=A0 =C2=A0100=C2=A0 =C2=A0030=C2=A0 =C2=A0 Pre-fail=C2=A0 Always=C2=A0 = =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A012 Power_Cycle_Count=C2=A0 =C2=A0 =C2=A0 =C2=A00x0032=C2=A0 =C2=A0100= =C2=A0 =C2=A0100=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2= =A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A01263
191 G-Sense_Error_Rate=C2=A0 =C2=A0 =C2=A0 0x0032=C2=A0 =C2=A0100=C2=A0 =C2= =A0100=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2=A0 =C2=A0= =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A04
192 Power-Off_Retract_Count 0x0032=C2=A0 =C2=A0100=C2=A0 =C2=A0100=C2=A0 = =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2=A0 =C2=A0 =C2=A0 =C2= =A0-=C2=A0 =C2=A0 =C2=A0 =C2=A0426
193 Load_Cycle_Count=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0032=C2=A0 =C2=A0029=C2= =A0 =C2=A0029=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2=A0= =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A0710616
194 Temperature_Celsius=C2=A0 =C2=A0 =C2=A00x0022=C2=A0 =C2=A0100=C2=A0 =C2= =A0100=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2=A0 =C2=A0= =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A054 (Min/Max 16/65)
196 Reallocated_Event_Count 0x0032=C2=A0 =C2=A0100=C2=A0 =C2=A0100=C2=A0 = =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2=A0 =C2=A0 =C2=A0 =C2= =A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
197 Current_Pending_Sector=C2=A0 0x0032=C2=A0 =C2=A0100=C2=A0 =C2=A0100=C2= =A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2=A0 =C2=A0 =C2=A0 = =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
198 Offline_Uncorrectable=C2=A0 =C2=A00x0030=C2=A0 =C2=A0100=C2=A0 =C2=A010= 0=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Offline=C2=A0 =C2=A0 =C2= =A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A00
199 UDMA_CRC_Error_Count=C2=A0 =C2=A0 0x0032=C2=A0 =C2=A0200=C2=A0 =C2=A020= 0=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2=A0 =C2=A0 =C2= =A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
220 Disk_Shift=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0002=C2=A0= =C2=A0100=C2=A0 =C2=A0100=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2= =A0Always=C2=A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
222 Loaded_Hours=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0032=C2=A0 =C2= =A0075=C2=A0 =C2=A0075=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Alw= ays=C2=A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A010367
223 Load_Retry_Count=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0032=C2=A0 =C2=A0100=C2= =A0 =C2=A0100=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Always=C2=A0= =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
224 Load_Friction=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00x0022=C2=A0 =C2= =A0100=C2=A0 =C2=A0100=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Alw= ays=C2=A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A00
226 Load-in_Time=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x0026=C2=A0 =C2= =A0100=C2=A0 =C2=A0100=C2=A0 =C2=A0000=C2=A0 =C2=A0 Old_age=C2=A0 =C2=A0Alw= ays=C2=A0 =C2=A0 =C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A0260
240 Head_Flying_Hours=C2=A0 =C2=A0 =C2=A0 =C2=A00x0001=C2=A0 =C2=A0100=C2= =A0 =C2=A0100=C2=A0 =C2=A0001=C2=A0 =C2=A0 Pre-fail=C2=A0 Offline=C2=A0 =C2= =A0 =C2=A0 -=C2=A0 =C2=A0 =C2=A0 =C2=A00

SMART Error Log Version: 1
No Errors Logged

The only thing that lo= oks high here is the load cycle count and maybe the power off retract count= . With
40k power on hours, that's a power off every 90 hours?= That seems a little weird. And the load cycle
is almost 20 times= the power on hours, suggesting it's going on every few minutes. That&#= 39;s higher than
I'd expect as well. The power cycle count is= also high for the number of hours. Your disk is pushing 4 years
= old too, which may mean its past expected life. So this profile suggests po= ssible signs of fatigue.

Warner
--0000000000009baec005eb29aabc--