juspifool

Members
  • Posts

    25
  • Joined

  • Last visited

Everything posted by juspifool

  1. Thank you for this plugin!
  2. Finished the rebuild overnight. So far the logs look a lot cleaner after moving the drives off of the Marvell controller and disabling it. Thanks for the help!
  3. I'm attaching the proper diagnotics but after moving the sata cables and disabling the Marvell controller the drive showed back up. I am currently doing a read-check of the array. tower-diagnostics-20180709-0908.zip
  4. Thanks for the quick reply. I'll be sure to grab diagnostics after I boot it back up. I'll also move the drives off of that controller.
  5. One of my WD Red Pros has disabled itself for the 2nd time in a month. The first time I ran an extended SMART test and everything passed. It just failed again this morning so I was hoping to have someone look over the the logs before I take any additional actions. Thanks in advance! tower-syslog-20180709-0815.zip
  6. I ended up moving my parity drive off of the Marvell port. Everything went well after that. Thanks for the suggestion!
  7. Not sure how that happened. I am at 23% on my latest parity sync. Once that either finishes or fails I will upload the correct SMART report. -Mark
  8. All 3 WD drives completed their SMART test without any issues. Attaching the reports. tower-smart-20170216-0752.zip tower-smart-20170216-0755.zip tower-smart-20170216-0758.zip
  9. It definitely made it further into the parity check this time but still failed. I'm going to replace the SATA cable for the drive but was hoping someone could take a look at the new diagnostics file and let me know if there is anything else I should check. -Mark tower-diagnostics-20170216-0704.zip
  10. Thanks for the check. I opened the case and disconnected/reconnected all the drives to be sure the cables were properly engaged. I can now see SMART reports for all WD drives and am currently running a parity rebuild. -Mark
  11. I recently upgraded my server with a new motherboard, CPUs, and ram. Previous to that I upgraded to a 6TB parity drive. This morning I noticed that my parity drive was disabled so I stopped the array, removed it, started the array, stopped the array, added it back, and finally started the array to do a parity rebuild. That lasted a couple minutes then it was disabled again. Looking for suggestions on what to check next. OS: Unraid 6.3.1 Mobo: ASRock Rack EP2C602-4L/D16 CPU: 2x Xeon E5-2670s Partity Drive: WD Red Pro 6TB I've also attached the diagnostics file from the server. Thanks, Mark tower-diagnostics-20170215-1629.zip
  12. I was able to get the drive mounted. I pre-cleared it again, formatted, and let it do a data rebuild. Looks like I lost all the data on the drive (which I didn't have backed up ) but it is back in the array. Thanks for all the help.
  13. I believe this is due to my motherboard treating 2 of the SATA ports as IDE ports. One of my drives is actually an IDE drive so the fact that there are three makes sense to me. Would it be better to remove those two drives from the on-board ports and put them on the AOC-SASLP-MV8 instead?
  14. Completed the rebuild and the drive was still not mounted. I ran the following as suggested: root@Tower:~# fdisk -lu /dev/sde Disk /dev/sde: 1500.3 GB, 1500301910016 bytes 1 heads, 63 sectors/track, 46512336 cylinders, total 2930277168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 64 2930277167 1465138552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# Looking at the results I am guessing this drive isn't correctly partitioned but can anyone confirm?
  15. It's off and running. I'll update with the status once it completes.
  16. I was not exporting the disk shares so I turned that on and I can not see \\tower\disk1. I removed the drive from the array once again and re-added it. Now it is asking if I want to "Start - will bring the array on-line, start Data-Rebuild, and then expand the file system (if possible)." Do I want to take that action to restart the array?
  17. Yeah when I did the rebuild and expand it prompted me to format the drive as well. Which I did do. Thanks for the help so far. Hopefully others can assist as well.
  18. Here is how I got to the point: Ran reiserfsck -- check Ran reiserfsck -- rebuild-tree as suggested in the prior step Stopped Array, Removed disk 1 from the array, Restarted Array Pre-Cleared disk 1 so it would show as new drive Stopped Array, Re-Added Disk 1, restarted array Disk 1 showed as a new disk, performed a data rebuild and expand as if I replaced a drive That is pretty much what got me to where I am now. With Disk 1 not mounting on boot but all the data seemingly available since I did have a valid parity drive before all of this happened.
  19. Recently I've been having some trouble with one of my drives. At first it was mounted as read-only and I ended up googleing solutions for that. I ran reiserfsck -- check then reiserfsck -- rebuild-tree which I now know might not have been a good idea. It still would not mount correctly and I was seeing errors in the log so I decided to remove it from the array, pre-clear the drive, and then re-add it to the array allowing the system to rebuild the data on the drive. After re-adding the drive to the array it is now not mounting on boot-up and there are errors in the log. It is also saying unformatted disks are present. I decided it was time to post a question on this. Any help is appreciated. syslog-2013-12-29.txt
  20. Thanks for answering my question. Perhaps someday teaming will be available in Unraid. -Mark
  21. I was hoping to connect them both to the same network to increase the available bandwidth to the server. Sounds like it isn't possible at this time. Still seems odd to me that one will work and the other won't when connected individually. -Mark
  22. I have an ECS A790GXM-A motherboard. Been running my Unraid Pro server for about 8 months with this board. Everything has been working well. The only issue I have is that I can not use both of my LAN connections at the same time. If I plug the cable into port 1 it works just fine. If I plug it into port 2 I have no network connection. I have tested both of the ports using an Ubuntu boot disc and the are both functional. According to the specs the LAN chipsets are both Realtek 8111C which is supported by Unraid. I am looking for someone to help me enable the second port so I can use them both at the same time. -I also have my Unraid server set to a static IP. Could that have anything to do with it? Thanks, Mark