16 прямоугольников темно-желтых выдало выходит
Добавлено через 13 минут
00:00:23.00 — ——————————— New test process started ———————————
00:00:23.02 — Started «Writing test data» for drive F: 15199MB, «ADATA, USB Flash Drive, 1100, «, 512b
00:02:15.20 — ! Write recoverable (1/3) error at LBN = 1540096 — Превышен таймаут семафора. (121.)
00:16:00.33 — ! Write recoverable (1/3) error at LBN = 13238272 — Превышен таймаут семафора. (121.)
00:24:55.34 — ! Write recoverable (1/3) error at LBN = 20709376 — Превышен таймаут семафора. (121.)
00:25:00.21 — ! Write recoverable (1/3) error at LBN = 20742144 — Превышен таймаут семафора. (121.)
00:25:07.26 — ! Write recoverable (1/3) error at LBN = 20807680 — Превышен таймаут семафора. (121.)
00:25:14.29 — ! Write recoverable (1/3) error at LBN = 20873216 — Превышен таймаут семафора. (121.)
00:25:21.33 — ! Write recoverable (1/3) error at LBN = 20938752 — Превышен таймаут семафора. (121.)
00:25:37.26 — ! Write recoverable (1/3) error at LBN = 21069824 — Превышен таймаут семафора. (121.)
00:25:44.35 — ! Write recoverable (1/3) error at LBN = 21135360 — Превышен таймаут семафора. (121.)
00:26:18.19 — ! Write recoverable (1/3) error at LBN = 21430272 — Превышен таймаут семафора. (121.)
00:26:34.34 — ! Write recoverable (1/3) error at LBN = 21561344 — Превышен таймаут семафора. (121.)
00:26:41.59 — ! Write recoverable (1/3) error at LBN = 21594112 — Превышен таймаут семафора. (121.)
00:32:19.69 — ! Write recoverable (1/3) error at LBN = 26287744 — Превышен таймаут семафора. (121.)
00:32:57.37 — ! Write recoverable (2/3) error at LBN = 26678016 — Превышен таймаут семафора. (121.)
00:34:53.54 — ! Write recoverable (1/3) error at LBN = 28175488 — Превышен таймаут семафора. (121.)
00:35:14.33 — ! Write recoverable (1/3) error at LBN = 28344320 — Превышен таймаут семафора. (121.)
00:35:26.52 — ! Write recoverable (1/3) error at LBN = 28435200 — Превышен таймаут семафора. (121.)
00:36:34.33 — ! Write recoverable (1/3) error at LBN = 29229056 — Превышен таймаут семафора. (121.)
00:36:39.23 — ! Write recoverable (1/3) error at LBN = 29261824 — Превышен таймаут семафора. (121.)
00:36:44.21 — ! Write recoverable (1/3) error at LBN = 29294592 — Превышен таймаут семафора. (121.)
00:37:16.39 — ! Write recoverable (1/3) error at LBN = 29539328 — Превышен таймаут семафора. (121.)
00:37:41.37 — ! Write recoverable (1/3) error at LBN = 29799168 — Превышен таймаут семафора. (121.)
00:38:10.24 — ! Write recoverable (1/3) error at LBN = 30113792 — Превышен таймаут семафора. (121.)
00:38:38.42 — ! Write recoverable (1/3) error at LBN = 30448896 — Превышен таймаут семафора. (121.)
00:39:14.30 — ! Write recoverable (1/3) error at LBN = 30903808 — Превышен таймаут семафора. (121.)
00:39:31.33 — Completed «Writing test data» for drive F: 15199MB, «ADATA, USB Flash Drive, 1100, «, 512b
00:39:31.35 — Tested total 15199.999MB in 0:39:08 with 6.484MB/s
00:39:31.35 — Total write errors: Fatal=0, Recoverable=25
00:39:31.35 — Started «Reading and comparing data» for drive F: 15199MB, «ADATA, USB Flash Drive, 1100, «, 512b
00:49:53.35 — Completed «Reading and comparing data» for drive F: 15199MB, «ADATA, USB Flash Drive, 1100, «, 512b
00:49:53.35 — Tested total 15199.999MB in 0:10:21 with 24.447MB/s
00:49:53.35 — Total errors: Read fatal=0, Read recoverable=0; Write fatal=0, Write recoverable=25; Comparsion=0
If the .Read() method of a net.Conn returns an error, does this imply that future reads also will fail with an error? Or are there recoverable errors? If so, how do I know whether/when to retry reads?
asked Sep 13, 2019 at 12:54
1
In general, you’re not going to have any errors from a conn.Read operation that can be retried. Most uses of the io.Reader interface will assume that all errors are final.
Any net package errors that are assured to be retry-able will conform to the net.Error interface, and expose a Temporary method.
This is most often used in an Accept loop, like this paraphrased example from the http package
for {
rw, e := l.Accept()
if e != nil {
if ne, ok := e.(net.Error); ok && ne.Temporary() {
if tempDelay == 0 {
tempDelay = 5 * time.Millisecond
} else {
tempDelay *= 2
}
if max := 1 * time.Second; tempDelay > max {
tempDelay = max
}
time.Sleep(tempDelay)
continue
}
return e
}
}
Any other possible cases need to be handled on an individual basis, with knowledge of the protocol and situation at hand.
answered Sep 13, 2019 at 16:24
JimBJimB
101k13 gold badges249 silver badges240 bronze badges
4
Timeout is the only recoverable error on read from a net.TCPConn and that error will only be returned when a read deadline is set on the connection.
Use Error.Temporary() to check for errors that may resolve on retry and Error.Timeout() to check for timeouts:
n, err := c.Read(buf)
// process buf[:n] bytes
if e.(net.Error); ok && e.Timeout() && e.Temporary() {
// handle recoverable read deadline expiration
} else if err != nil {
// handle other errors
}
answered Sep 14, 2019 at 0:31
Cerise LimónCerise Limón
109k11 gold badges231 silver badges233 bronze badges
4
Question Very intermittent and recoverable «disk read error occurred»
-
Thread starterAndy27
-
Start dateJan 14, 2022
-
#1
It’s so infrequent that it’s hard to spot a pattern as to when it occurs. I can say that it only ever happens when my daughter is playing Sims 4, which she plays for an hour or two most evenings. This is the only time the h/w is «pushed» at all. The PC isn’t used for any other gaming, and the rest of the time it is used for «light duties» — mainly me working from home during the day over RDP, so the PC is on for 10+ hours per day, to put the infrequency of these crashes into context.
The latest crash was last night, and looking at Windows event viewer immediately before the crash, I can see quite a few errors over the space of 10-15 seconds, mainly a mix of
«The IO operation at logical block address 0x0….. for Disk 0 (PDO name: DeviceIdeIdeDeviceP1T0L0-2) was retried»
and
«The driver detected a controller error on DeviceIdeIdePort1»
Could these crashes be a sign that the SSD is starting to fail? It feels like problems would be more frequent if this was the cause.
Could loose/bad SATA cables produce these symptoms? Again it feels like the problem would be more frequent. As a precaution I’m going to order some new cables tonight, as that’s a cheap and easy fix to try.
Can SSDs overheat? Given that it only happens when the Sims is running, then eventually starts working again after a few minutes, my gut tells me that it could be heat. Having said this, the case does have good ventilation with front and back fans, and I don’t imagine that the Sims will be pushing the hardware to its limits! The SSD does sit in the bottom of the case underneath a HDD, so perhaps the air isn’t circulating very well down there, so I can try moving it to see if that helps. Are there any Windows utilities to report disk temps, and if so what is a «normal» range?
It’s an infrequent but frustrating issue, especially as my daughter is autistic, so when the PC crashes it triggers anxieties and worries about losing everything on the PC!
-
- Feb 8, 2021
-
- 5,633
-
- 867
-
- 11,440
- 398
-
#2
I fitted a SSD to my PC around 18 months ago, and since then it has been experiencing a very infrequent issue (once every 3-4 months), where Windows 10 will completely freeze (mouse, everything), and when I restart the PC it displays a black screen with «A disk read error occurred». Online articles seem to suggest that the disk has died, but I always find that the problem disappears after 4 or 5 restarts, and the PC is absolutely fine again (until next time). Occasionally we’ll see a BSOD rather than Windows just freezing, but I can’t recall the specific error message.It’s so infrequent that it’s hard to spot a pattern as to when it occurs. I can say that it only ever happens when my daughter is playing Sims 4, which she plays for an hour or two most evenings. This is the only time the h/w is «pushed» at all. The PC isn’t used for any other gaming, and the rest of the time it is used for «light duties» — mainly me working from home during the day over RDP, so the PC is on for 10+ hours per day, to put the infrequency of these crashes into context.
The latest crash was last night, and looking at Windows event viewer immediately before the crash, I can see quite a few errors over the space of 10-15 seconds, mainly a mix of
«The IO operation at logical block address 0x0….. for Disk 0 (PDO name: DeviceIdeIdeDeviceP1T0L0-2) was retried»
and
«The driver detected a controller error on DeviceIdeIdePort1»Could these crashes be a sign that the SSD is starting to fail? It feels like problems would be more frequent if this was the cause.
Could loose/bad SATA cables produce these symptoms? Again it feels like the problem would be more frequent. As a precaution I’m going to order some new cables tonight, as that’s a cheap and easy fix to try.
Can SSDs overheat? Given that it only happens when the Sims is running, then eventually starts working again after a few minutes, my gut tells me that it could be heat. Having said this, the case does have good ventilation with front and back fans, and I don’t imagine that the Sims will be pushing the hardware to its limits! The SSD does sit in the bottom of the case underneath a HDD, so perhaps the air isn’t circulating very well down there, so I can try moving it to see if that helps. Are there any Windows utilities to report disk temps, and if so what is a «normal» range?
It’s an infrequent but frustrating issue, especially as my daughter is autistic, so when the PC crashes it triggers anxieties and worries about losing everything on the PC!
Run a pass of crystaldiskinfo and post a screenshot of the results.
-
- Sep 13, 2002
-
- 7,155
-
- 1,400
-
- 29,590
-
- 431
-
#3
heat very well could be one issue
-
- Feb 8, 2021
-
- 5,633
-
- 867
-
- 11,440
- 398
-
#5
Nothing real bad shows.
It says your connected with a sata 2 port.
Is that how you have it connected?
-
#6
Nothing real bad shows.
It says your connected with a sata 2 port.
Is that how you have it connected?
I don’t know, is the honest answer! What would I need to look for? Is sata 2 good or bad, and if the latter how would I change it?
-
- Feb 8, 2021
-
- 5,633
-
- 867
-
- 11,440
- 398
-
#7
I don’t know, is the honest answer! What would I need to look for? Is sata 2 good or bad, and if the latter how would I change it?
What is this machine?…..make and model.
Sata 2 would be a bit of a throttle on the ssd perf.
-
#8
CPU is AMD FX-6300, 8Gb RAM, GeForce GT-640.
-
- Feb 8, 2021
-
- 5,633
-
- 867
-
- 11,440
- 398
-
#9
The motherboard is an Asus M5A78L-M LX3. I’ve just dug out the specs which say it only supports sata 2.
CPU is AMD FX-6300, 8Gb RAM, GeForce GT-640.
Ok…..that answers that.
Perhaps reseat the sata data cable at both ends and the power cable.
If no help try a different sata port on the mobo.
-
- Dec 26, 2012
-
- 30,270
-
- 4,315
-
- 141,190
- 5,241
-
#10
It’s also possible your ssd just has a bad control board that likes to glitch every now and then, possibly due to heat, possibly just because.
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics