Jump to content

swells

Members
  • Posts

    150
  • Joined

  • Last visited

Posts posted by swells

  1. Ok. So I ran the post read portion of the preclear and it was fine. So I trusted the new 8TB disk and wanted to replace that failed 2TB disk asap. I did the swap and everything went fine. After the swap I started a nocorrect parity check and so far, at 27% complete (2.2TB or so), there are 4201 sync errors. My first thought is to let this run and then do it again and see if it is the same. If it is, do I correct it? How should I proceed at this point?

  2. Alright, i'll run with that then. Should I do a full preclear again or just a post read? Thats where it was when it disconnected from the controller last night. As far as I can tell, everything was ok with the preclear up to that point. With the plug in it looks like I can just do the post read and save a couple days, but I have no problem doing it all again if need be. Just not sure about leaving that bad disk there a while longer.

  3. Nothing I can't afford to lose on this server. Entirely media. I would however rather be safe than sorry, so will probably try to replace that disk before I do anything else. I do however wish to continue with my move to bigger 8TB drives. Any problems with the below plan? With the last couple steps, is there a way to expand the file system once the larger parity drive is in place or do I need to remove it and put it back in like a new disk to utilize the space?

     

    My current plan is something like:

    1) Ensure 8TB disk is fine

    2) Rebuild bad 2TB disk onto precleared 8TB disk.

    3) Order another 8TB disk and preclear it.

    4) Replace current 3TB disk with new 8TB disk.

    5) Replace 8TB data disk previously used to replace failed 2TB disk with 3TB former parity disk.

    6) Utilize full 8TB of original 8TB disk in array.

     

     

  4. Ok, I need some help.

     

    I picked up a new 8TB Seagate drive to serve two purposes. I have a few 2TB WD20EARS drives still in play and one of them has 1 sector pending relocation. I also am getting low on space and need to expand soon. The 8TB drive will become my new parity drive to replace a 3TB drive in use currently and the 3TB parity drive will replace this 2TB WD drive so I can retire it (it has been in use for ~5 years in this server). So that is the background.

     

    The drive was finishing up a single pass of preclear on the post read phase and was about 70% complete last night. I was about to go to bed and figured I would kick off a parity check and make sure all was well before the preclear finished and I could continue on. I woke up to the preclear complete, but the 8TB disk was spun down and would not spin up. It was basically not available any longer. I checked the logs and it was full of errors. Looks like two drives had some issues, ATA12 is the 2TB WDEARS drive I would like to replace, it reconnected to the controller and is fine now from what I can tell. And ATA15 (sdn) is the 8TB Seagate and it did not and is offline. I have no idea what I should be looking at. Is there a huge problem here? Did i over stress something by running a parity check while running the preclear? If someone could please take a look at the logs you will see everything of relevance I believe. I have removed a bunch of crap that was spamming the logs, which I have also never seen before, but it was basically thousands of lines of this:

     

    Feb 24 23:47:49 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

    Errors.txt

  5. Quick question... I just added this to my unRAID install. It is working perfectly except for one detail. I have some files that are more than 5 folders deep. Which numbers in the go script do i need to edit? Both of the 5's or just one of them? My current structure is below, I just need to up it to 6 i believe.

     

    Media>TV>Completed>Show>Season>Episodes

     

    The 'episodes' is the actual video files within the Season X folder, not another folder. I thought that would technically be 5 levels deep but the drives were spinning up when i got this deep. I added the line listed in the wiki to my go script so it looks like....

     

    /boot/cache_dirs  -d  5  -m  3  -M  5  -w

     

    Thanks guys!

     

×
×
  • Create New...