Darronn

Members
  • Posts

    13
  • Joined

  • Last visited

Darronn's Achievements

Noob

Noob (1/14)

1

Reputation

1

Community Answers

  1. Just to update on my issue. @JorgeB Thanks for all your help and time responding. I'll mark your response of "dropping offline and reconnecting" as the cause/solution. After testing different drives connected in different positions I realized that the cause was two of the 5.25" drive caddys I recently purchased. My tower case only held a small number of 3.5" drive spaces so I was using the 5.25 bays with caddys. Two I purchased a long time ago and have had no issues, but the recent two I purchased both are causing the intermittent issues. I bought a Rosewill server chassis & higher wattage PS. Moved everything into it and then ran new pre-clears on each drive before adding to the array. All have been running perfect with no errors now. I've also added a second parity drive which is currently syncing / data rebuild. Three of the drive are well used between 20k and 28K power on hours. So I thought it was a good idea to add the extra data protection. I'm going to go though previous drives that were pulled because of errors because I think they may actually be fine.
  2. Yeah, I agree it seems that way, but it doesn't do exactly the same when connected to the LSI card. Is the LSI just handling the problem better? The dropping offline and reconnecting is basically the same symptom just not as bad?
  3. Ok, I see. Is that log from when it first boots up? I have tried putting the drive back on the onboard controller, but it's worse there. When the drive is connected to that it spins up/down and chirps. Doesn't matter what port. It's possible that the LSI card i bought is faulty, but since the motherboard seems to be having issues I've ordered a new board to start there. If I have issues after that with the LSI card, I'll try the new onboard ports which should be good. Thanks for your help looking at it.
  4. I've already tried that. It doesn't make a difference which port that drive is on on it always shows up as an unmountable drive in the array and an Unassigned device. I can mount that drive outside the array and read the data on it. Wouldn't there be a log of this dropping offline and reconnecting? I really don't think that is happening. Moving the drive from the onboard SATA to the SAS card caused something to identify this drive differently. Now there is a ghost twin that the array tries to mount, which doesn't exist and obviously fails. Right now I've added new drives outside the array and am copying the data off the array. Fortunately DIsk4 was recently purchased and added (less than two weeks ago) and only a small portion of data is on it. Once it's all copied off. I'll New Config the array. Start over and copy it back.
  5. This is the only odd thing I can find. When the array is started. Disk4 is unmountable. It's showing (sdg) which doesn't exist. # hdparm -I /dev/sdg /dev/sdg: No such file or directory The duplicate unassigned device (sde) does. # hdparm -I /dev/sde /dev/sde: ATA device, with non-removable media Model Number: WDC WD40EDAZ-11SLVB0 Serial Number: WD-WX22D410YDUL Any ideas what is causing that and how to fix it?
  6. Disk 2 is missing. So yes it's unmountable because of that. That's what started this for me. I had trouble replacing the drive because of slowness. It was stating that it was going to take 57 days to repair & the web interface was extremely slow. Pretty sure the SATA controller on the board is failing. Disk1 I was mistaken, it's mounted, but not sure why it's showing up as an Historical device. Disk4 is flipping around and showing up as sdc, sdf, sdg, sdh. I've run short & extended smart tests and it's not showing any errors but the array seems to think there are 2 read errors. The Mini SAS cables are brand new and seated well. Last night I tried to put them in the same order as they were before so they've been moved around and still same state. Just trying to get to a point that I can try and add the new replacement Disk2 and rebuild. Then I'll be replacing the motherboard.
  7. I bought an LSI SAS 9210-8i card and moved my drives off the motherboard onto it. After putting the card in and cabling it up I have 2 drives that are showing as unmountable. (Disk1 & Disk4). When I start the array I see that: - Disk4 is also seen as an Unassigned Device (sdc) - Disk1 is seen as an historical device (sdc) When I stop the array I see that: - Both Disk1 & Disk4 show up as Historical Devices. Not sure how to resolve it. D iwursrv-diagnostics-20220320-1116.zip
  8. Thanks. I think based on the strange issues I've previously had and the current ones I'm having again, which are very similar, I have the feeling the onboard SATA is the cause. I've bought a new card so hopefully this resolves it. I'll probably end up getting a new motherboard if that's the case.
  9. How does Unraid handle moving a drive from a motherboard SATA port to a PCIe SATA card? Does it see it as the same drive, or think the drive is missing and the new SATA port it's connected to as an unassigned drive? Thanks
  10. It has a requirement. You need to have "Unassigned Devices" installed. Then the install will show up on the "Unassigned Devices Preclear".
  11. Thanks for the reply. I was able to figure it out and fixed it. I stopped and started the array and disk 5 showed up as unmountable. Ran xfs_repair and that fixed the disk/permissions issue but the Dockers were still messed up. Restored appdata from last backup and all is working fine again.
  12. Hi, I had a drive fail (disk5) and replaced it. Unraid did it's thing and completed this afternoon stating "Parity sync / Data rebuild finished (0 errors)" My PLEX docker is unable to run properly. Logs show "PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server". Same with DiskSpeed. Both won't open the WebGUI. I attempted to remove/reinstall Diskspeed but the install failed badly and it doesn't even start now. When I open the Plex user console, the /mnt directory is seen as empty. I also noticed this with disk5 (the new drive) while looking around trying to figure out what the problem is: drwxrwxrwx 3 nobody users 48 Mar 2 16:21 disk4/ d????????? ? ? ? ? ? disk5/ drwxrwxrwx 1 nobody users 244 Mar 2 16:21 user/ Any ideas what caused that or how to fix it? Would this likely be related to the Docker permissions problem? I'm thinking if I attempt to manually configure permissions on disk5 I could really break something or maybe lose data. Thanks.