Seonac

Members
  • Posts

    24
  • Joined

  • Last visited

Everything posted by Seonac

  1. One thing that isn't clear to me... maybe I missed it seeing it stated or listed somewhere. Is the Parity still valid during a Scatter, Move operation? I have a disk that may fail soon and don't have a spare but have plenty of space within the array to move the data to, so I was going to shrink the array. I realize that I will have to create a new config and rebuild the parity after removing the disk. I started a scatter, move operation following SpaceInvaderOne's instructions and realized after starting the operation I'm not sure if the parity is maintained during the move.
  2. Thank you very much JorgeB. I was able to try the card in another computer and it was dead. I was able to get a M.2 SATA adapter with a JMB585 chip today and the array is going again. Thank very much for all of the information you provided in the Recommended Controllers for Unraid thread! Very helpful in finding a new card that wasn’t overkill for my system 😁
  3. I moved all of the old hardware, motherboard included to the new case. There is no old server or motherboard to test the card on. The card has worked without issue since I bought it about 3 years… until now…
  4. Unraid - 6.2.9 HBA - LSI 9207-8i - 6 / 8 drives connected. I switched all of my hardware to a much needed new case. After booting UNRAID the array configuration was invalid and none of the disks connected to the LSI card were detected. The cache pool and the parity drive is connected to the motherboard SATA ports were detected by UNRAID. I tried reseating the card, disconnected and reseated all cables at both ends. I tried switch the card to another PCIe slot on the motherboard. During at least a couple of the boots I saw the following error: mpt2sas_cm0: _base_spin_on_doorbell_int: failed due to timeout count As well as other failures related to mpt2sas, which is what prompted me to reseat and change the card to another PCIe slot. After changing the card to another PCIe slot the card was detected and UNRAID showed the configuration was valid. When I tried to start the array, it never actually started… really hoping the data on the drives is ok… UNRAID didn’t show any errors that I saw. It just sat “Starting Array” for an extremely LONG time. I should’ve grabbed a syslog or diagnostic but didn’t even think. I shutdown and checked the seating of the card again and now the card is not showing up at all… I did grab a diagnostic log from this boot up. This is bundle attached. I tried to boot into the BIOS for the card but never saw an option for it come up, tried CTRL+G during boot but UNRAID boot menu just ended up eventually came up. I bought the card 3 years ago off Amazon and it was already flashed to IT mode so maybe possible the BIOS was wiped/removed? Am I right thinking that the card dead or is there something else going on in the logs?unfortunately I don’t have another board to test it on. mrnas-diagnostics-20221219-2220.zip
  5. Thank you very much! That explains it! Have never had run into that until now.
  6. Thank you JorgeB! As expected, the shares did come back after a reboot. I’m planning on moving the hardware into a new case today, paranoia and worry that something was wrong got me LOL
  7. Using Unraid 6.9.2 All of my user shares disappeared! I was browsing shares and all of a sudden was I was disconnected and could no longer access any of the shares over the network. I logged into the webgui expecting to see at least a disabled disk but there aren’t any red ball disks and the user share section is empty. I ran a short smart test for all disks including disks in the cache pool, all completed without error. I’ve downloaded the diagnostics and attached it. So far I have only stopped all dockers and the one VM I run. I have not rebooted yet. Wanted to wait incase th Any help would be greatly appreciated! mrnas-diagnostics-20221218-0943.zip
  8. Thank you! I started the array and was able to browse the emulated contents of disk6. I stopped the array and replaced disk6 with a new precleared drive already in the server and started the rebuild process.
  9. I don't see the disk listed anywhere in the WebUI, I also checked System Devices under Tools as well. The drive is connected to a LSI SAS card so I didn't expect that it would show in the BIOS. I physically swapped the 'Unassigned Device' drive and drive that was disk6 to rule out bad cable or bad connector and the 'Unassigned Device' drive was detected but the drive that was assigned to disk6 was still not detected. Should/Can I start the array with the disk missing? I wasn't sure if that would unassign the slot, making a drive rebuild impossible. The Array Operations shows 'Stopped. Configuration valid.' Array Devices, shows the disk 'Device is missing (Disabled), contents Emulated'. Here's a new diagnostics just incase it's useful. mrnas-diagnostics-20220813-1744.zip
  10. Powered down, checked all connections and here's a new diagnostics. mrnas-diagnostics-20220813-1636.zip
  11. I rebooted after getting the diagnostics. So the Diagnostics are pre-reboot and the screenshots are post-reboot.
  12. Thanks trurl! I noticed that the SMART report for disk6 was missing and just thought that that it was missing because it was disabled and couldn't be accessed by unraid. Here's the screenshot of Unassigned Devices, it's a precleared drive. Here's the screenshot of the Array Devices, the only drive available in the dropdown list for drive6 is the same drive in the unassigned disks.
  13. This morning I received a notification my unraid server (v6.9.2) that Disk 6 was disabled and 'in error state'. I've be very lucky and have not had to deal with any drive failures in many many years, I've replaced drives over the last few years due to age usually around 4-5 years rather then failures as they were not NAS drives. I prefer the proactive approach but probably due to paranoia more then anything LOL I was going to run a File System Check, following the instructions in the Manual, Drive_shows_as_unmountable. Steps I've followed so far: - Ran Diagnostic Tool - Stopped the Array - Powered Down Server - Checked cables in Drive Trays and to LSI Card - Powered Server back on, I have auto mount set as off I was going to start in 'Maintenance Mode' but the Disk now shows as 'Unassigned' and the drive is no longer listed, I assume because it is not longer considered to be a valid drive for assignment? I have not started the array in maintenance mode or otherwise. Looking for some direction before I do anything further. Do I leave the disk as 'Unassigned' and start the array in maintenance mode and do the File System Check, and repair the File System if needed? Or should I just replace the drive and start the rebuild? The drive is question was next to be replaced, so I already have a replacement drive pre-cleared and ready. First thing I did was run the diagnostic tool, results attached. Maybe if someone could take a look? I've also attached the post-reboot syslog in case it might be helpful. I appreciate any help and advice! mrnas-diagnostics-20220813-1149.zip mrnas-syslog-20220813-1349.zip
  14. Will do. New PSU is already ordered and on route, should receive it tomorrow, hopefully will get it installed tomorrow night. Got a great deal on a single rail 650W with 54A on 12V rail, CORSAIR HX650 $119.99 CAD + 25USD rebate. http://www.newegg.ca/Product/Product.aspx?Item=N82E16817139012
  15. The parity did rebuild successfully but during the rebuild disk 5 showed 31 errors. I assume that these would be read errors since nothing was being written to the array during the rebuild. After the parity rebuild was complete, a parity check NOCORRECT completed successfully. Parity Valid Last checked on Wed Jul 10 18:12:50 2013 ADT, finding 0 errors. However, now there is 138 errors showing for disk 5. I know that ANY errors during a rebuild is bad but I'm just not sure exactly what this means. Is the disk bad/have corrupt sectors? Is this caused by the power issues experienced earlier? I've attached a smart test for the disk in question and a new syslog. In the log there are quite a few of these lines, which would've occured during the rebuild: Jul 10 02:15:42 MR_NAS kernel: md: disk5 read error Jul 10 02:15:42 MR_NAS kernel: handle_stripe read error: 1974783248/5, count: 1 Jul 10 02:15:42 MR_NAS kernel: md: parity incorrect: 1974783248 Later there are these, which would've occured during the Parity Check: Jul 10 12:01:07 MR_NAS kernel: md: disk5 read error Jul 10 12:01:07 MR_NAS kernel: handle_stripe read error: 1974783248/5, count: 1 FYI - I've also ordered a new psu: Corsair HX650 - http://www.newegg.ca/Product/Product.aspx?Item=N82E16817139012 smart.txt syslog.txt
  16. Ok, thanks! Maybe time to purchase that new PSU. In the meantime, I'll shutdown pull the cache drive, check the connections again and try another parity rebuild. FYI - I also confirmed that I only have 1 drive connected to the SY-PEX40008. I appreciate the help!
  17. Thanks again for the help! The parity rebuild failed. A new syslog is attached. Also a new smart test for the parity drive. My cache drive seems to have disappeared as well now... the cache drive slot is now set to 'unassigned' and there are no options in the menu. It was an old 250 GB drive... no data of value if the drive is lost. But the fact it's disappeared may help... smart.txt syslog-2013-07-09.2.zip
  18. I removed the 3 drives and rebooted the server. Here's a fresh syslog. I have not yet started the array. Can the parity be recovered or will I have to rebuild it? syslog-2013-07-09.txt
  19. Thanks for your help! The last physical change was in early June, about 2 weeks before I moved. I had pre-cleared drives as spares set aside (3 hdds) and I added them to the server but not the array to keep them safe during the move. I used hdparm -y during the go script to put the drives in standby using 'preclear_disk.sh -l to grep the /dev assignment of the drive using the serial #. That way they wouldn't draw any power and would be available if/when needed. lines from go: for sparesn in W1E26DXP JP2940HD046Y1C S13PJ90S328879 do /boot/./stdbyspare.sh $sparesn done stdbyspare.sh: ##Get /Dev/sdX - Works Since Drive is OUTSIDE of the Array, using S/N to parse /dev Location #Serial Number of Spare Drive sparelog=/boot/spare.txt sparesn=$1 # Uses preclear_disk.sh script to list Drives Ouside of Array | Get Line containing Supplied drive S/N | Parses line with '=' as delimiter and returns first feild | Removes ALL spaces spare="$(/boot/./preclear_disk.sh -l | grep $sparesn | cut -d = -f1 | tr -d ' ')" echo "Drive S/N: $1" >> $sparelog echo "Spare Drive: $spare" >> $sparelog /usr/sbin/hdparm -C $spare >> $sparelog /usr/sbin/hdparm -y $spare >> $sparelog /usr/sbin/hdparm -C $spare >> $sparelog H/W: MB - ECS A780GM-M3 CPU - AMD Athlon X2 250 PSU - OCZ ModXStream Pro 700W RAM - 4 GB PCI-E SAS - AOC-SASLP-MV8 PCI SATA - SY-PEX40008 Flash - 4GB Seagate (2.0A Startup): 3TB - ST3000DM001 2TB - ST2000DM001 x 5 (4 in use - 1 put in standby using hdparm -y during 'go' script) 2TB - ST3200542AS 1TB - ST31000528AS 250GB (cache) - ST3250310AS (2.8A Startup) Samsung (2.4A Startup) : 1TB - HD103UJ x 2 (1 in use the other put in standby using hdparm -y during 'go' script) Hitachi (2.0A Startup): HDS721010CLA332 (put in standby using hdparm -y during 'go' script) I think that you are right in thinking that it may be a power issue... I checked to see if the 3 disks that should be in standby and none of them are... So I'm way well over the 25A rail for the PSU (@ 31 A currently ).... Without those 3 drives I'm at 19.2A + 5A for the mobo I thought I'd be good, as long as the drives stayed in Standby. Yes, I am looking to purchase a better PSU - SeaSonic G Series SSR-550RM 550W (http://www.newegg.ca/Product/Product.aspx?Item=N82E16817151119). I've just been waiting for a sale/rebate or price drop. Would it be safe to shutdown the Server and remove those 3 drives. Is there any way to get the parity drive back without a complete rebuild? Or is the parity completely invalid now? What would you recommend as the next steps?
  20. UNRAID Ver: 5 rc11 PRO I'm sure I made some mistakes attempting to fix the problem myself and I'll try to provide as much information as possible hoping someone can help me out. I run various plugins: SickBeard, CouchPotato, Sabnzbd, Transmission, mysql (for XBMC Shared Library) are the major ones. All seems to have been stable on my system for quite sometime now, at least a few months. I've rebooted multiple times, parity check is completed weekly with zero errors. The NAS was rebooted about 2 1/2 weeks ago when I moved. I also use cron to monitor Directories and add torrents to Transmission. Today I started receiving Input/Output error notices via email every minute for hours - of course I wasn't home so I couldn't check on the NAS to find out what the issue was. I unfortunately do not have a syslog for any of these events only the most recent reboot. 'sh: /mnt/cache/.scripts/transmission/watchdir.sh: Input/output error' is the msg I was receiving. Finally when I was able to get home I commented out the line in the go file that added the cronjob until I could figure out what exactly was causing the issue. I stopped the array, rebooted and left to go do something else. I didn't check to make sure the NAS went down and came back up successfully. I'm not sure if it did and I can't confirm it. The emails did stop so I assume that it did successfully reboot. When I did come back to check a few hours later I was unable to load the Webgui (waited a few minutes for the page to load). So I tried 'killall emhttp' (I killed unmenu), which did kill the process but when I tried to restart it, 'nohup /usr/local/sbin/emhttp &' which resulted in a Segmentation Fault. SO I tried 'powerdown'.... This is where everything went downhill... After I waited a little while, about 10-15 mins, I noticed that the cache drive was still mounted. I realized that Sickbeard, Couchpotato, mysql and Transmission were still running - I was unable to access their web pages earlier to shutdown them down. SO I killed the running processes - which I had done in the past and resulted in the successful shutdown and restart of the NAS. Not so lucky this time. I waited for another 20 mins - went and did other things and came back to find the NAS had not yet powered down. Whenever I reboot and I want to make sure I always run 'ping x.x.x.x -t'. I tried to telnet back into the NAS and was unable to reconnect but it was still responding to pings. So, I left it again for another 10 minutes and patiently waited for the power off to occur. I came back and it was still responding but I couldn't telnet in or access any shares. SO I did what I thought was my last option and last resort - I went to the box and gave it the ol' 1 finger salute and it shutdown. I took out the flash drive and commented out everything not stock and renamed the plugins directory so I would have a stock UNRAID when it booted back up. I have a SYSLOG from here on. (attached) When the system rebooted, it of course started a parity check - Which I let run but when I came back to it probably about 1/2 - 1 hour later (I'm really not sure) the parity failed and it said there 758 errors and the parity disk was red balled. I stopped the array and now the parity disk is reported as 'New parity disk installed.' I've run a short smart test. (attached) A long test is running now. I will post once the test is complete. I have not done anything else and will patiently wait for some advice on what to do from here... syslog.zip smart.txt
  21. UhClem Thanks for the script! @ Johnm - I looked into and you are right! HighPoint is certainly not known for their support! Just for kicks I ran UhClem's script on my setup: I currently have a 4 port PCI Vantec card (this is the card I'm replacing) and it's certainly to WeeboTech's level But I at least expected to get 100 MB/s... almost but not quite and not even close on 1 hdd... ./dskt.sh X g h i j sdg SAMSUNG HD103UJ = 92.91 MB/sec sdh SAMSUNG HD103UJ = 3.71 MB/sec sdi ST31000528AS = 93.64 MB/sec sdj ST31000333AS = 93.38 MB/sec ./dskt.sh g h i j sdg = 86.99 MB/sec sdi = 62.74 MB/sec sdh = 13.00 MB/sec sdj = 63.26 MB/sec Here are the results of my 6 motherboard hdd's... I expected that they would all get above 110MB/s, some of them are rather old and may replaced in the near future. Would the age of the drive (3+years) have a bearing on these results? root@MR_NAS:/boot# ./dskt.sh a b c d e f sdd = 80.42 MB/sec sdf = 112.34 MB/sec sda = 68.28 MB/sec sde = 127.13 MB/sec sdb = 77.44 MB/sec sdc = 76.36 MB/sec root@MR_NAS:/boot# ./dskt.sh X a b c d e f sda ST32000542AS = 107.95 MB/sec sdb ST3500830AS = 77.95 MB/sec sdc ST3320620AS = 77.36 MB/sec sdd SAMSUNG HD501LJ = 82.54 MB/sec sde ST31000528AS = 128.61 MB/sec sdf SAMSUNG HD103UJ = 115.60 MB/sec
  22. I realize that most people here use Supermicro cards, seems to be the most popular choice by far! They way I see it: HP 2720SGL - PCI-e 2.0 x 8, 6Gb/s (no I don't have 6Gb/s drives but any drive that I replace will be with 6G HDDs), 3TB support @ $129 vs. SM AOC-SASLP-MV8 - PCI-e (1? not sure about this) x 4, 3Gb/s, 3TB @ 120 Just seems that for the price the HP card is the better choice but whether or not it's supported by UNRAID is the question.... I have read posts that suggested that hdd's would never see the benefit of 6Gb/s but even if this true, x4 vs x8 PCI-e means a potential throughput of 2GB/s vs 4GB/s. I haven't been able to find what chipset the HP card is based on so To be honest I'll probably go with the SM card because there is so much knowledge is here about that particular card and I certainly don't feel the urge to compile a custom kernel for UNRAID
  23. I've been looking to add a SATA Controller and I've been trying to find out if this card is compatible with UNRAID - HighPoint RocketRAID 2720SGL - http://www.newegg.ca/Product/Product.aspx?Item=N82E16816115100 but haven't had much luck. It seems like everyone on here uses the SUPERMICRO cards but I've haven't been able to find out if the HighPoint RocketRAID controller is compatible or not. Is there anyone that uses this HighPoint card or at least tried to?
  24. @prongATO: Did you end up getting the RocketRAID 2720 card? How did it work out for you? http://www.newegg.ca/Product/Product.aspx?Item=N82E16816115100 @ $150 +shipping I'm considering buying this card myself and would like to hear from someone else as well.