Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265432
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: 1 Currently unreadable (pending) sectors How worried should I be? |
| Date | 2024-01-03 02:00 +0100 |
| Message-ID | <HRXLX-o3M-7@gated-at.bofh.it> (permalink) |
| References | <HRVK9-mRQ-1@gated-at.bofh.it> <HRW3v-ngX-5@gated-at.bofh.it> <HRWwx-npV-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Charles Curley wrote: > On Tue, 2 Jan 2024 17:47:18 -0500 > Dan Ritter <dsr@randomstring.org> wrote: > > root@tiassa:~# smartctl -a /dev/sda > smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-amd64] (local build) > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE > 1 Raw_Read_Error_Rate 0x0032 100 100 050 Old_age Always - 0 > 5 Reallocated_Sector_Ct 0x0032 100 100 050 Old_age Always - 1 > 9 Power_On_Hours 0x0032 100 100 050 Old_age Always - 764 > 12 Power_Cycle_Count 0x0032 100 100 050 Old_age Always - 25 > 178 Used_Rsvd_Blk_Cnt_Chip 0x0032 100 100 050 Old_age Always - 1 > 194 Temperature_Celsius 0x0022 100 100 050 Old_age Always - 45 > 195 Hardware_ECC_Recovered 0x0032 100 100 050 Old_age Always - 0 > 196 Reallocated_Event_Count 0x0032 100 100 050 Old_age Always - 0 > 197 Current_Pending_Sector 0x0032 100 100 050 Old_age Always - 1 > 198 Offline_Uncorrectable 0x0032 100 100 050 Old_age Always - 0 > 199 UDMA_CRC_Error_Count 0x0032 100 100 050 Old_age Always - 0 > 232 Available_Reservd_Space 0x0032 100 100 050 Old_age Always - 96 > 241 Total_LBAs_Written 0x0030 100 100 050 Old_age Offline - 13943 > 242 Total_LBAs_Read 0x0030 100 100 050 Old_age Offline - 5610 These are the values that can indicate health problems with the disk. None of them look bad except the temperature - which is only bad because of the specs on the disk - and > 197 Current_Pending_Sector 0x0032 100 100 050 Old_age Always - 1 which confirms that something is stuck, but it's just one sector. I would not worry about this unless some new symptom emerges. Make backups, but only because you should pretty much always have backups. -dsr-
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-02 23:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Dan Ritter <dsr@randomstring.org> - 2024-01-03 00:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-03 00:40 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Dan Ritter <dsr@randomstring.org> - 2024-01-03 02:00 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Tixy <tixy@yxit.co.uk> - 2024-01-03 08:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Dan Purgert <dan@djph.net> - 2024-01-03 00:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-03 00:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Andy Smith <andy@strugglers.net> - 2024-01-03 01:40 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-03 04:20 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-03 12:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-03 21:30 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-04 00:30 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? <tomas@tuxteam.de> - 2024-01-04 12:00 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-04 15:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Andy Smith <andy@strugglers.net> - 2024-01-05 22:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-06 00:30 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? David Christensen <dpchrist@holgerdanske.com> - 2024-01-06 02:30 +0100
Secure erase [was: Re: 1 Currently unreadable (pending) sectors How worried should I be?] Max Nikulin <manikulin@gmail.com> - 2024-01-06 03:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-06 06:20 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? David Christensen <dpchrist@holgerdanske.com> - 2024-01-06 09:40 +0100
Re: reinstallation and restore after catastrophic mistake or failure; was: 1 Currently unreadable (pending) sectors How worried should I be? Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-06 13:40 +0100
Re: reinstallation and restore after catastrophic mistake or failure; was: 1 Currently unreadable (pending) sectors How worried should I be? David Christensen <dpchrist@holgerdanske.com> - 2024-01-07 00:40 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Max Nikulin <manikulin@gmail.com> - 2024-01-04 16:20 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-04 17:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Andy Smith <andy@strugglers.net> - 2024-01-03 14:30 +0100
csiph-web