scubieman Posted March 2, 2020 Share Posted March 2, 2020 (edited) Just did a priority sync, and im getting about 186 errors, Just wondering if I could have help this is urgenet "need to watch" or what. Also could I fix so i dont see the errors anyways? jewel-diagnostics-20200302-0202.zip Edited March 2, 2020 by scubieman Quote Link to comment
scubieman Posted March 2, 2020 Author Share Posted March 2, 2020 Would this be from possible bad hard drive? or something else? prefer not to replace drives right now Quote Link to comment
Addy90 Posted March 2, 2020 Share Posted March 2, 2020 (edited) Errors there are read errors that were corrected on the fly, so at that moment, no files are damaged. Your Parity sdg disk definitely has read errors - critical medium error: Mar 1 09:15:52 Jewel kernel: sd 7:0:5:0: [sdg] tag#158 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 1 09:15:52 Jewel kernel: sd 7:0:5:0: [sdg] tag#158 Sense Key : 0x3 [current] [descriptor] Mar 1 09:15:52 Jewel kernel: sd 7:0:5:0: [sdg] tag#158 ASC=0x11 ASCQ=0x0 Mar 1 09:15:52 Jewel kernel: sd 7:0:5:0: [sdg] tag#158 CDB: opcode=0x88 88 00 00 00 00 01 d1 17 f7 38 00 00 01 d0 00 00 Mar 1 09:15:52 Jewel kernel: blk_update_request: critical medium error, dev sdg, sector 7802976056 op 0x0:(READ) flags 0x0 phys_seg 58 prio class 0 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802975992 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976000 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976008 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976016 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976024 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976032 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976040 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976048 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976056 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976064 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976072 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976080 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976088 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976096 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976104 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976112 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976120 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976128 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976136 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976144 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976152 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976160 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976168 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976176 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976184 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976192 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976200 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976208 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976216 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976224 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976232 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976240 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976248 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976256 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976264 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976272 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976280 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976288 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976296 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976304 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976312 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976320 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976328 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976336 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976344 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976352 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976360 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976368 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976376 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976384 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976392 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976400 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976408 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976416 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976424 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976432 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976440 Mar 1 09:15:52 Jewel kernel: md: disk0 read error, sector=7802976448 If you want, make a second Parity sync. Check if more errors come up after the run. If yes, it can be the cable or the disk. For me it looks like the disk because of Pending sectors, no cable should cause this. Be extra sure that there are not Party sync errors but only read errors on the disk. Parity sync errors means data can not be rebuild correctly, luckily your Parity disk does not contain data, but if another disk failes, you could end up with lost data because the Parity disk can not rebuild from the error sectors. This means, the corrected read errors are rebuild from the remaining disks on the fly. If another disk failes, these read errors will result in data loss as you only have one parity. If you want to be extra sure, replace cable and do another Parity sync (or replace cable before the second Parity sync). If there are any more read errors and it is not the cable: Replace disk. Nothing is worse than data corruption because a failing disk was there for too long. Really, replace it. You cannot rebuild your data from a faulty parity disk. I had this too, replaced my disk as it always showed errors during each Parity sync and now the errors are gone. Never had a faulty cable I have to admit... Edited March 2, 2020 by Addy90 Quote Link to comment
scubieman Posted March 2, 2020 Author Share Posted March 2, 2020 Im assuming its faulty disk, Just dont know what to replace it with, I cant go shuckable since I dont have the 3v3 mod Thinking just getting a red 6 tb Quote Link to comment
Addy90 Posted March 2, 2020 Share Posted March 2, 2020 Replace it with a disk at least as large as the current disk. So you need a 6 TB with no less sectors than the current one, or you use a bigger disk and are able to upgrade / replace another data disk later with a bigger one, too. Quote Link to comment
JonathanM Posted March 2, 2020 Share Posted March 2, 2020 7 minutes ago, scubieman said: I cant go shuckable since I dont have the 3v3 mod Kapton tape. It's not too hard. https://www.instructables.com/id/How-to-Fix-the-33V-Pin-Issue-in-White-Label-Disks-/ Quote Link to comment
scubieman Posted March 2, 2020 Author Share Posted March 2, 2020 Could of thinking a red, longer warranty. but cost more so IDK not ready to buy yet Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.