TonyTheTiger

Ok. So I wasn't overreacting. Probably more like procrastinating. And was lucky to get everything off it before it failed. I assume using it for anything else is courting disaster. Is the silly thing reusable? Recyclable? Should I try to preclear data (scrub) before I get rid of it? Trash or electronic waste dropoff? BTW - the fan on the top of the case has been acting up (new one on order). Do you think that the temps were merely "not good" for the system or is there a direct correlation with the life span of this drive? Or was it just (bad) luck? There are15 drives in the server - most much older. Thanks again in advance. Michael...

Hello all. I've had Errors from one of my drives for a while but the SMART overall-health report still says "Passed", and the Parity drives seemed to keep correcting the problem because the array wasn't dropping the drive. Finally had time to move the data off the drive and find room for it all (8TB). Now What? Was I worried for nothing? Procrastinating? Is the drive really ready to fail? Is the drive "fixable". Would preclearing it again help? What do you even do with a bad drive (out of warranty)? Use it as a door stop? Ran Fix Common Problems (a number of times), and extended tests were okay. Read most of the info on Understanding SMART Reports. Not unsurprisingly, it didn't really help. spent a couple hours browsing the forums. I could use a little advice. Please find attached smart report and syslog. And thank you in advance. Michael... leone4-smart-20180330-1313.zip leone4-syslog-20180330-1312.zip

OMG I went around and around for a week and a half trying to figure that out. Never even thought of a non-unraid problem. Its working now. Thanks johnnie.black

Hello Everyone I've been trying to upgrade my Parity Drives from 4TB to 8TB but can't figure out what I'm doing wrong. Each time I try I select to new drive(s), the screen refreshes, a warning states that "ALL DATA ON THIS DISK WILL BE ERASED WHEN ARRAY IS STARTED". No problem. I've done this on another server and expected it. But When I scroll down, the Start Button is "greyed-out". I still see the "Star will start Parity-Sync and/or Data-Rebuild" warning, but I can't click on it or the "Yes I want to do this" checkbox. I tried updating to v.6.3.5, ungrading only one parity drive, switching which drives I upgrade, preclearing again, parity checks, Fix Common Problems scans. Just can't start the array. If I put the 4TB drive back in, everything works fine. The Start button is also greyed-out if I just "no device" and "maintenance mood" is also missing. [HOWEVER the last time I replaced the 4TB and ran a scan, I received the following error: parity (ST4000DM000-1F2168_xxxxxxxx) has read errors If the disk has not been disabled, then unRaid has successfully rewritten the contents of the offending sectors back to the hard drive. It would be a good idea to look at the S.M.A.R.T. Attributes for the drive in question] Any ideas?

Hello everyone. This past week was spent trying to fix a household-wide network problem, where some computers/devices only connected to a couple others, and some of them couldn't connect to anything. While trying to isolate the problem, I saw that the unRaid web GUI was down. Needing to fix the Windows machines first, I logged into the unRaid server from the console (no GUI, Telnet, or SSH), and used "powerdown". Now that I've gotten almost everything working again, I still can't get the web GUI running. (No, I didn't get a syslog or diagnostic. At the time, my son's homework assignment was more important). Would a Clean Install fix my problems? I've already had a one Windows 10 reinstall, a Windows 7 reinstall, a FIOS cable box factory reboot, and upgraded bunch of device firmware - a parity check on the media server isn't really a big deal now. It was a pretty straight forward unRaid v6.2.4 installation. I hadn't started using Docker Containers nor VMs, yet; and I have a record of drive assignments, so that part won't be a chore. If I do do a clean install, should I make sure that I set the unRaid server to a Local Master? (never even new that was a "thing", but my suspensions are that my network problems originated with a Windows 10 update - and my ham-handed attempts to fix that) BTW Is "powerdown" correct? Or should it have been "poweroff"? Could I have just pressed the Power Button the the server? I usually use a "gracefull shutdown" (stop samba, terminate the busy processes, unmount the disks, and then stop). Thank you in advance.

That was a bit embarrassing. I hadn't noticed that my signature was so out of date. Sorry. My plan was to pull two of four drives from Server #1 (dual Parity). Run New Config. Run Parity Check. Meanwhile, insert those drives into Server #2 (also with dual parity). Run New Config and Parity Check on Server #2 (avoiding the disk clearing phases, the drive formatting, and the moving of data across the network). Repeat for the remaining two of four drives from Server #1 It seems that would be a little less time. But neither this idea, nor the traditional way of just starting Server #2 with fresh (but used) drives, is going to be exactly quick. Of course, that is if it even works. I guess Plan #2 would be to just set up Server #2 with a bunch of spare drives, move 24TB of data over the network, then shrink Server #1 two drives at a time (running New Config and Parity Check each time). @Frank1940 Thank you for mentioning your warning. While I was aware of your concern, someone else, searching the forum might have misunderstood. I know that I've been that person before. Often.

Hello Everybody. Just a quick question (couldn't find the answer by searching the forum): After running out of space in my current server case, and slowly upgrading to larger and larger drives, I've decided to just start a new (2nd) unRaid server. Can I start a new unRaid server with data already on drives and just move them over to the new computer, or do I need to start with empty (probably pre-clreared) drives and move the data with either Win10 or Midnight Commander? (or a good xfs command). I understand that I'll need to run the New Config Utility (and run a new Parity Check) on the first server, to shrink it. Would that same theory work on the 2nd server, to grow it? Its been I long time (v.4.?) since I started a new unRaid system. BTW I already have a spare unRAID Pro Registration Key. Thank you in advance. Michael

Another completely uneventful update. Everything is working fine. (6.17 -> 6.18) Thank you for all your hard work. Of course, now that I'm becoming used to everything going so smoothly....

trurl, your quick. I was reading that very page and was about to post the results of the reiserfsck status check when I saw your reply. Both drives respond with:[pre]reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md5 Will put log info to 'stdout' The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). [/pre](weird cut&paste) The instructions a "Check Disk Filesystems" are extensive for reiserfsck --rebuild-sb (Rebuilding Superblock), but that doesn't seem to be what I'm instructed to do. How do I "try writing to the bad blocks and see if the drive remaps the bad blocks"? Also, is "use badblock option (-B) the same as the badblock command from http://linux.die.net/man/8/badblocks or is there another command ing the reiserfs utils that I have to find? Any advice would be appreciated. TYIA

I missed your question. Both of these drive are still using ReiserFS.

The Second Server was just an idea to read the info off the drives. I'm not sure if there is any way to recover data from them. I attached the Smart Reports from the two drive in question. I have to admit, though, unless I see a glaring failure, I really don't know how to read them. They "look okay to me". Disk1 = ST3000DM001-1CH166_Z1F1HJ1V-20151207-2151 (sorry, I noticed I typed 4TB in the first post; it should have been 3TB) Disk5 = ST4000DM000-1F2168_Z300XJNY-20151207-2151 Any advice would be appreciated. TYIA ST3000DM001-1CH166_Z1F1HJ1V-20151207-2151.txt ST4000DM000-1F2168_Z300XJNY-20151207-2151.txt

Just an Out-OF-The-Box Idea. I have a second unRaid Pro License. Could I start up a new (small) sever with at least Disk1 (and maybe Disk5); and form a new Parity from them? Then transfer the info to newly replace drive in the old Server. I really don't want to lose that music. Some of it came from relatives who are no longer alive. Just an Idea.

Hello All. My server is full of drives. Mostly 4TBs. I had to pull Disk1 (leaving the Array Unprotected) to Preclear a new 6TB drive to replace/upgrade the my 4TB Parity Drive. It took most of the weekend, but it went okay (No Failures). Pulling the 6TB, and reinstalling Disk1, I restarted the Array and was told it need to rebuild Disk1 (Orange Triangle). No Problem. I expected this. THEN... 0.1% into the rebuild I notice that Disk5 Red-Balled (well, Red-Xed, now). It showed No Device, and wants to completely reformat Disk1 & Disk5. Taking a chance, I stopped the Array, powered-down, and re-checked and re-seated all the cables (SATA and power). Restarting the Server, but not the Array, I can re-assign Disk5 (Blue Square), and Disk1 is still an Orange Triangle. Restarting the Array gives me an Orange Triangle on both Disk1 & Disk5, but still wants me to reformat both drive. I don't want to. Niether drive holds Life Threatening Information. Disk1 has/had almost 4TB of music that can't easily be replaced. Disk5 has/had almost 4TB of TV Shows. What Now? Please let me know if I should upload the Diagnostics or not. Any advice would be appreciated. TYIA

kenneth_dart I had everything running for a couple days, and haven't found a problem with P20, yet. I've been moving files to and from unRaid v5.0.4 and my Win7 box. This morning I spent some time in case management (I had cables going all over the place), and it still seems okay. I've never been thrilled with the data transfer but diskspeed.sh hasn't shown anything unusual. My syslog looks pretty much the same, too. I've attached an (edited) excerpt from the txt log I keep whenever I do something to the computer. (I know its kinda geeky, but its saved my ass a couple of dozen times). @Moderator - please let me know if I should have attached this as a txt file instead of verbose text. It always amazes me that there are so many ways to do the same thing on a computer. I followed different internet advice than some on this thread (see below), and it worked for me. Bare in mind that I had an actual LSI card and a Supermicro MB. You mileage (and your Lenovo TS440) may vary ______________ 2:50 PM 5/3/2015 MODIFIED - Installing and flashing the LSI SAS9211-8i from whatever IR mode (Integrated RAID firmware) it shipped with to, P20 to IT mode (Initiator target mode). NOTE: I'm following advice on: http://linustechtips.com/main/topic/104425-flashing-an-lsi-9211-8i-raid-card-to-it-mode-for-zfssoftware-raid-tutorial/ http://brycv.com/blog/2012/flashing-it-firmware-to-lsi-sas9211-8i/ http://software.intel.com/en-us/articles/uefi-shell NOTE: I rebooted the server and made sure a got a copy of the syslog (just in case) 1. I removed the currently installed LSI SAS9211-8i from the SuperMicro (PCH) Slot 4 (the tutorial mentions not flashing a second card while the first is installed) and mounted the newer card in the SuperMicro (PCH) Slot 5 - (thats the PCI-Express 3.0 x4 in x8 Slot - the one nearest from the CPU). NOTE: the new card came with a low-profile case mounting bracket and wasn't long enough to attach correctly. I removed it all together and will need to eventually replace it. 2. I booted up the server and accessed the BIOS: a. Adjusted SuperMicro AMI BIOS > ADVANCED > PCI > PCH Slot 5 from [Legacy] to [EFI Only] The previous adjestments are staying the same. - Adjusted SuperMicro AMI BIOS > ADVANCED > PCI > Launch Storage OpROM from [Legacy] to [uEFI Only] - Adjusted SuperMicro AMI BIOS > ADVANCED > PCI > Other PCI Device OpROM from [Legacy] to [uEFI Only] b. I saved and exited. This started unRaid. Because the first LSI card wasn't installed (it's in an antistatic bag, right now), unRaid reported 8 RED BALLS for the missing drives. I logged into the webGUI and powered down. 3. Formated old Attache USB 512MB drive (yeah, MB) with FAT32 4. I downloaded "9211_8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows" from http://www.lsi.com/products/host-bus-adapters/pages/lsi-sas-9211-8i.aspx#tab/tab4 a. Pulled the file "2118it.bin" located in the directory Firmware/HBA_9211_8i_IT of the archive and put in on the Attache USB 512MB drive. b. Pulled the file "mptsas2.rom", located in the directory sasbios_rel inside of the archive and put in on the Attache USB 512MB drive. 5. I downloaded: Installer_P20_for_UEFI from http://www.lsi.com/products/host-bus-adapters/pages/lsi-sas m-9211-8i.aspx#tab/tab4 a. Pulled the file "Shell.efi" located in the directory sas2flash_efi_ebc_rel of the archive and put in on the Attache USB 512MB drive. NOTE: the tutorial still goes to alot of trouble to include a UEFI shell as well, but I think I got that one covered in the SuperMicro BIOS; so I'm skipping ahead (fingers crossed). 6. I replaced the the Sandisk 16GB internal drive (unRaid) with the PNY Attache USB drive in the the server and rebooted. 7. At the SuperMicro BIOS Menu, I pressed F11 to invoke the Boot Menu. 8. At the Boot Menu, I scrolled down to UEFI: Built-in EFI Shell. 9. On my machine, the first thing the shell did was diplay a nice list of all connected storage devices, with my Attache 256 MB USB drive labeled fs0 :Removable HardDisk Alias hd16b0f0band my HDDs and SSDs labled blk#. Unfortunately, I couldn't actually see the information because it scrolled off the top of my sceen. Google'n, I found the command I needed: map -b -This displayed a map of all the devices and waited at the the top of the screen form my to press ENTER to continue or 'q' to exit. 10. mount fs0: -to mount the drive 11. fs0: -change directories into the drive 12. ls -to list the contents of the directory (just to be sure) 13. sas2flash.efi -o -e 6 -command to erase/reset the card and prepare it for the new BIOS and firmware. The -o flag puts it in "advanced mode" The -e flag is the Erase command. The Erase Parameter 6 is to "Clean flash (erase everything except manufacturing area)" (fingers crossed) NOTE: CAREFUL: DO NOT TURN OFF OR REBOOT YOUR MACHINE AT THIS POINT. ALLEGEDLY YOU WILL HAVE A BRICKED CARD ON YOUR HANDS!!! NOTE: The display: LSI Corporation SAS2 Flash Utility Version 20.00.0.00 (2014.09.18) Copyright © 2008-2014 LSI Corporation. All rights reserved SAS2FLASH: Disconnecting the EFI Driver. Advanced Mode Set Adapter Selected is a LSI SAS: SAS2008(B2) Executing Flash Region... Erase Flash Region... Erase Flash Operation Successful! Resetting Adapter... Reset Successful! Finished Processing Commands Successfully. Exiting SAS2FLASH. fs0:\> 14. sas2flash.efi -o -f 2118it.bin -b mptsas2.rom -this flashes the new files. The -f flag is the firmware update file. The -b flag is the BIOS update file. (fingers crossed, again) 15. Both the Firmware Flash and the BIOS Flash were SUCCESSFUL! The display scrolled off the screen so I can't see it again; but I entered: sas2fllash.efi -list and received: Adapter Selected is LSI SAS SAS2008(B2) Controller Number : 0 Controller : SAS2008(B2) PCI Address : 00:02:00:00 SAS Address : 500605B-x-xxxx-xxxx NVDATA Version (Default) : 14.04.00.08 NVDATA Version (Persistent) : 14.00.00.08 Firmware Product ID : 0x2213 (IT) Firmware Version : 20.00.02.00 NVDATA Vendor : LSI NVDATA Product ID : SAS9211-8i BIOS Version : 07.39.00.00 UEFI BSD Version : N/A FCODE Version : N/A Board Name : SAS9211-8i Board Assembly : H3-xxxxx-xxx Board Tracer Number : SPxxxxxxxx (serial number) Finished Processing Commands Successfully. Exiting SAS2Flash. 16. exit -to exit UEFI Shell 17. Reboot (5:27 PM 5/3/2015) NOTE (8:01 PM 05/03/2015): reading some ofthe unraid forum posts I notice that other users had problems with P20. I'm kinda worried, now. I posted to the Forum and will wait for adive. In the meantime, I guess I'll just keep an eye on it. NOTE (05/06/2015): reading some of the unRaid forum posts, I notice that other users had problems with "Failed to validate Mfg 2 page" errors. I did see a message like that as well and the process seemed to stall for 10-15 seceond (an eternity when your fingers are still crossed) but it seemed to autocorrect itself (maybe in some subroutine?) and I think I saw either "Validated" or "Validation Successful" and continued on. Because it Finished Successfully, I didn't think to write it down at the time.

Thank you jbartlett. Your script (v.2.2) works great on my system. The web page shows the information eloquently. Facinating, really. I have all Seagate drives and you can really see the performance differences in the models. (I definitely know which one I'm going to replace.) Thanks, again. Michael