| 1 |
A point to keep in mind - if you can feel the drive moving it may be |
| 2 |
generating errors! Depending on the drive, the errors may just be |
| 3 |
handled internally and I can see it slowing things down though probably |
| 4 |
would be barely noticeable. I have seen it myself with random errors |
| 5 |
from a WD green drive disappearing when properly immobilised. When |
| 6 |
investigating I ran across articles discussing the problem, one of which |
| 7 |
fastened the drives to a granite slab for tests! Also see discussions |
| 8 |
on NAS seups and vibrations affecting co located drives. |
| 9 |
|
| 10 |
BillK |
| 11 |
|
| 12 |
** Interesting read |
| 13 |
https://www.ept.ca/features/everything-need-know-hard-drive-vibration/ |
| 14 |
|
| 15 |
|
| 16 |
On 27/12/21 22:15, Dale wrote: |
| 17 |
> Wols Lists wrote: |
| 18 |
>> On 27/12/2021 13:40, Michael wrote: |
| 19 |
>>> On Monday, 27 December 2021 11:32:39 GMT Wols Lists wrote: |
| 20 |
>>>> On 27/12/2021 11:07, Jacques Montier wrote: |
| 21 |
>>>>> Well, i don't know if my partitions are aligned or mis-aligned... How |
| 22 |
>>>>> could i get it ? |
| 23 |
>>>> fdisk would have spewed a bunch of warnings. So you're okay. |
| 24 |
>>>> |
| 25 |
>>>> I'm not sure of the details, but it's the classic "off by one" |
| 26 |
>>>> problem - |
| 27 |
>>>> if there's a mismatch between the kernel block size and the disk block |
| 28 |
>>>> size any writes required doing a read-update-write cycle which of |
| 29 |
>>>> course |
| 30 |
>>>> knackered performance. I had that hit a while back. |
| 31 |
>>>> |
| 32 |
>>>> But seeing as fdisk isn't moaning, that isn't the problem ... |
| 33 |
>>>> |
| 34 |
>>>> Cheers, |
| 35 |
>>>> Wol |
| 36 |
>>> I also thought of misaligned boundaries when I first saw the error, |
| 37 |
>>> but the |
| 38 |
>>> mention of Seagate by the OP pointed me to another edge case which |
| 39 |
>>> crept up |
| 40 |
>>> with zstd compression on ZFS. I'm mentioning it here in case it is |
| 41 |
>>> relevant: |
| 42 |
>>> |
| 43 |
>>> https://livelace.ru/posts/2021/Jul/19/unaligned-write-command/ |
| 44 |
>>> |
| 45 |
>> that might be of interest to me ... I'm getting system lockups but |
| 46 |
>> it's not an SSD. I've got two IronWolves and a Barracuda. |
| 47 |
>> |
| 48 |
>> But I notice the OP has a Barra*C*uda. Note the different spelling. |
| 49 |
>> That's a shingled drive I believe, which shouldn't make a lot of |
| 50 |
>> difference in light usage, but you don't want to hammer it! |
| 51 |
>> |
| 52 |
>> Cheers, |
| 53 |
>> Wol |
| 54 |
>> |
| 55 |
>> |
| 56 |
> I don't recall seeing this mentioned but this may be part of the issue |
| 57 |
> unless I'm missing something that rules this out. Could it be a drive |
| 58 |
> is a SMR drive? I recently made a new backup after wiping out the |
| 59 |
> drive. I know the backup drive is a SMR drive. At first, it copied at |
| 60 |
> a fairly normal speed but after a short time frame, it started slowing |
| 61 |
> down. At times, it would do only about 50 to 60MBs/sec. It started out |
| 62 |
> at well over 100MBs/sec which is fairly normal for this rig. I would |
| 63 |
> stop the copy process, let it catch up and restart just to give it some |
| 64 |
> time to process. I can't say it was any faster that way tho. |
| 65 |
> |
| 66 |
> The way I noticed my drive was SMR, I could feel the heads going back |
| 67 |
> and forth by putting my hand on the enclosure. It had a bumpy feel to |
| 68 |
> it. You can't really hear it tho. If you can feel those little bumps |
| 69 |
> even when the drive isn't mounted, I'd be thinking it is a SMR drive. |
| 70 |
> There are also sites that you can look this sort of thing up on too. If |
| 71 |
> needed, I can go dig out some links. |
| 72 |
> |
| 73 |
> Just thought it worth a mention. |
| 74 |
> |
| 75 |
> Dale |
| 76 |
> |
| 77 |
> :-) :-) |
| 78 |
> |
Archives