3 ms·

I don't think I agree with any of this. There's no need to be storing anywhere near that amount as a hobbyist. 1) Learning to be more selective in the pictures

by trwhite 11y ago

I don't think I agree with any of this. There's no need to be storing anywhere near that amount as a hobbyist. 1) Learning to be more selective in the pictures you take forces you to be a better photographer. Shoot film for a month and you'll learn this. 2) Learning to edit (in the sense of choosing your best) photographs also forces you to be a better photographer. In realising what makes a better picture, you'll learn what looks good and what doesn't.

PStamatiou 11y ago
If you read my post you'll see that I ruthlessly edit and cull before posting any of my photos. It's not about that, it's just about keeping the original set. I want to keep everything on hand as I sometimes go back and make videos like this: https://www.youtube.com/watch?v=8fR4MjImSU0 https://www.youtube.com/watch?v=8fR4MjImSU0 Or now that I imported them to Google Photos it creates a bunch of GIFs and other fun things for me. If I didn't have the 5 shots of that same thing, etc ,etc, I wouldn't have any of this.
- barrkel 11y ago
  Replying here so that you'll hopefully see it: WD Red drives do not have head parking disabled. In fact this is a matter of some annoyance in the NAS world, because the default settings (8 second timeout) lead to astronomical SMART Load_Cycle_Count numbers when used in a typical NAS. Google around and you'll see. Run smartctl on your drives and check the value of Load_Cycle_Count. That's the number of times the drive has come out of head parking. Most of my WD Reds were over 100K before I noticed - the duty limit is 600K. idle3-tools on Linux comes with idle3 tool, which can read and alter the head park timeout.
  - PStamatiou 11y ago
    I remember reading about this issue when I was setting the NAS up and I kept monitoring the load cycle counts but saw nothing out of the norm. Wondering if this was updated in recent drive firmware? I will take a look at that tool though, thanks!
    - PStamatiou 11y ago
      Hey again, so I just checked the Load_Cycle_Count on all the drives. I've been running this setup pretty much 24/7 since February and they all have a count of just 108. It looks like WD fixed this in recent Red batches.
      - barrkel 11y ago
        Cool, good to know. I have 11 4TB WD Reds, 10 of which are all in the 100k range (the other one is a warm spare). I was pretty upset when I saw the numbers.

by trwhite 11y ago

PStamatiou 11y ago

If you read my post you'll see that I ruthlessly edit and cull before posting any of my photos. It's not about that, it's just about keeping the original set. I want to keep everything on hand as I sometimes go back and make videos like this: https://www.youtube.com/watch?v=8fR4MjImSU0 https://www.youtube.com/watch?v=8fR4MjImSU0 Or now that I imported them to Google Photos it creates a bunch of GIFs and other fun things for me. If I didn't have the 5 shots of that same thing, etc ,etc, I wouldn't have any of this.

barrkel 11y ago
Replying here so that you'll hopefully see it: WD Red drives do not have head parking disabled. In fact this is a matter of some annoyance in the NAS world, because the default settings (8 second timeout) lead to astronomical SMART Load_Cycle_Count numbers when used in a typical NAS. Google around and you'll see. Run smartctl on your drives and check the value of Load_Cycle_Count. That's the number of times the drive has come out of head parking. Most of my WD Reds were over 100K before I noticed - the duty limit is 600K. idle3-tools on Linux comes with idle3 tool, which can read and alter the head park timeout.
- PStamatiou 11y ago
  I remember reading about this issue when I was setting the NAS up and I kept monitoring the load cycle counts but saw nothing out of the norm. Wondering if this was updated in recent drive firmware? I will take a look at that tool though, thanks!
  - PStamatiou 11y ago
    Hey again, so I just checked the Load_Cycle_Count on all the drives. I've been running this setup pretty much 24/7 since February and they all have a count of just 108. It looks like WD fixed this in recent Red batches.
    - barrkel 11y ago
      Cool, good to know. I have 11 4TB WD Reds, 10 of which are all in the 100k range (the other one is a warm spare). I was pretty upset when I saw the numbers.