Jump to content

lovswr

Members
  • Content Count

    83
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lovswr

  • Rank
    Advanced Member
  • Birthday 04/30/1967

Converted

  • Gender
    Male
  • AIM
    arcvswr

Recent Profile Visitors

598 profile views
  1. Well this was really bugging me so I kept at it. I swapped the LSI controller card for the spare I have on hand. Still the same symptom. This morning, I took the case apart. Since my drive bay enclosures are for SATA drives, they have SATA power connectors. I have a modular PS & I was using MOLEX connectors with MOLEX to SATA adapters. I removed the adapters & am running SATA cables straight from the PS. Rebooted & the rebuild is running at about 172.5M/s as I type these words. I really hope that fixes my problem.
  2. So, itimpi since you gave me direction to investigate, this is what i did: I have this Mediasonic 4-disc drive bay holding 3 discs, including the aforementioned disk1. It is vertically orientated & sits at the top of my case. Just beneath it is a 5-disc drive bay holding 4 discs that is horizontal in nature. Both are connected to a LSI 8-port controller. First I shutdown & checked/reseated all SATA connectors & power leads. Rebooted & I got rebuild speeds of mid 50M for about 15 minutes, then it tricked back down to less than a k & the log showed the same errors as before. Shutdown again & completely frogged the SATA cables; that is to say I unplugged the 4 cables from the Mediasonic drive bay & plugged those cables into the other drive bay & vise-versa. This time I got acceptable speeds for about 30 minutes, then, again, it made its way back to sub 1000 B/sec. After I thought about this some, I realized that all of my drive failures over the last 2 years or so have come from drives installed in the Mediasonic drive bay. I have a second Mediasonic bay that I am going to install to see if that is the issue. I have a Corsair 750W PS which is less than a year old & I believe it sufficient to power 7 SATA drives, one USB jump drive, & about 5 fans. However, all the drives are essentially coming from one "rail" on the PS so I will have to divvy that up better.
  3. unRAID v 6.71 - Had a drive fail, so replaced it with a new one. The rebuild rate is 809 KB/sec or 59 days for an array consisting of 6 4TB drives & 1 parity drive. I then looked at the log & thought my Parity drive was also failing. However, after looking through the forums here, I have concluded that I have no idea what is wrong. So I have included my diagnostics. Thanks in advance.valhalla-diagnostics-20191205-2244.zip
  4. Just wanted to say that my old APC Back-UPS 550 finally bit the dust. I had it for over 5 years & the battery has been replaced once. I just bought a new APC Back-UPS 1100 & made no changes to apc-deamon. It appears to be working just fine.
  5. So put the array back into maintenance & run the disk check with the command above?
  6. Whoops! I knew I was forgetting something. valhalla-diagnostics-20190913-1341.zip
  7. My disk 1 failed about 6 or 7 weeks ago. Well I just replaced it a few days ago with a new Seagate ST4000NM0035. Pre-clear was fine & added it to my array. After a successful parity-check, all my little triangles are green. Everybody's happy, right! Well I went to save something to a share on disk 1 & now I keep getting 'Disk is write-protected'. After mucking around a bit, I decide to do a maintenance mode check of disk 1. I have included the output because I don't even know where to begin. It is a 4TB drive with 52% utilization. Thanks in advance for any solutions or input on how to fix this problem disk1-check.txt
  8. I had a similar problem and my guide refused to update & I could no longer access my Plex server outside my house. Did as you instructed to move over to the Linuxserver version. It is now updating the guide & it also appears that remote access has been restored. Kudos & thanks!
  9. Thanks johnnie.black. I did as you instructed & I now have over 50G of free space on my SSD cache. I will be watching closely over the next 3-5 days to see how it performs.
  10. As requested. valhalla-diagnostics-20190704-1341.zip
  11. Hello, I started getting this error about 4 days after I upgraded to v6.7.1. I have 4 docker containers (duckdns, openvpn-as, PlexMediaServer, & smokeping) & they all stopped & will not restart (reports Execution Error when I try to restart them). At first I thought the problem was related to the advanced server tuning that I did after watching this most excellent video by Spaceinvader One. However, after reading here that BTRFS errors tend to imply some kind of problem with the cache drive & after looking at the recent red alerts on my server all showing disk space low on my cache drive, I'm pretty sure the problem is with my cache drive. A simple restart of my server will get the dockers running again, but if anybody has any ideas on how to fix this problem I would certainly appreciate it. The full error reads like the below & just kept repeating
  12. I have the same issue. No sound at all. I also would like to commend the OP for this excellent tutorial. Really easy to follow AND he explains things. Having said that it was not obvious (at least not to me) that if you try to get Windows 10 from Microsoft while using a Windows machine, that download page will try to force you to use that horrible tool. The trick is to change the User Agent in the browser session of the download page. For example if one is using Chrome, here is how to do it. Last thing. Did anyone actually manage to buy a working Windows Pro license from that website? That price seems too good to be true.
  13. Yep, I just found it about 1 minute before your response. Parity is rebuilding now without that empty 4TB drive. After rebuild I will just swap out the mostly full 3TB for the empty 4tB. Thank you for your excellent & speedy assistance.
  14. Thank my lucky stars (I think). I found that diagnostic file on my desktop. I searched around several files & it seems that df.txt has useful info. It has all drives listed but not the serial correlated to the assignment that the drive controller gave. It does have used & free space, but how do I figure out which drive goes where?