Alexandro

Members
  • Posts

    321
  • Joined

  • Last visited

Everything posted by Alexandro

  1. I have just added a new 3tb drive to my array and assigned it to Media shares. (Unraid was restarted after the changes being made). Unraid doesn't calculate the new space and sees only the left space on the share without the additional and fresh 3 TB of free space. Here are some screenshots:
  2. After a pending sector appeared on one of my drives i decided to go safe and to buy another one and to exchange it with the "bad" drive. As I am not 100% sure in my Parity disk (last parity build showed 105 errors in reading from the "bad" drive) what is the best way to backup the "bad" drive: 1. To remove the "bad" drive and assign the new one and let the Parity to rebuild its data; or 2. To assign the new disk as a new data drive and using MC under telnet to move the content from the "bad" to the new one? Thanks
  3. Parity was updated 105 times to address sync errors but now I have a green parity and data drive. I am a bit scared to start a Parity-check. I ran a short self tesk on Disk1 which ended with a message that "Errors occurred". Beside this 1 Pending sector i have also a LBA error now which was presented in the SMART.log Are there any steps that I can take to clean it or I need to RMA this drive too? SMART.txt
  4. Thank you very much dgaschk being so helpful. I am on 65% rebuild parity process now and have something like 3 hours to complete (speed decreased to 96 MB/sec). I will let it finish and if failed i will buy another 3tb HDD to transfer the data from DISK1. Something very weird is happening here. Is it possible the cage to be the cause of tis bad sectors?
  5. I dont know. Currently I am doing parity sync after initconfig.
  6. Thank you very much. The SASLP-MV8 is with the most current firmware. I will update the mainboard this evening. After the experiment (drive cage) I have again a current pending sector on DISK1 It is time to stop experimenting and just to throw out the cage. Here is a smart report of DISK1 SMART.TXT
  7. This morning DISK1 was disabled (red) with a lot of I/O errors in the log file. It confirms that the cage is not working reliable with my motherboard. Probably the sata ports on the cage are not negotiating with the sata ports of the motherboard. Is there something more i can try or sell the cage or change the motherboard with something better? Currently I am doing Parity sync with 110 MB/sec with the disks attached directly to the MB. Please help. I am lost here.
  8. I did this with SNAP plugin. Attach the new drive (out of the array) and copy the needed content to it. Probably someone can have different approach and will share some experience to us.
  9. OK, here is what happened today. I was at the local supermicro dealer's premises to see the performance of my own cage. It was attached to a supermicro system, with a fancy (and very expensive) Raid controller. The cage was filled with 5 WD RE4 HDDs. The speed between the HDD's was around 750 MB/sec. and no problems in the log file during transfers. So I took the cage with the new cables which the guys provide me with and ran home to install it at my Unraid. I put the cables in, doubled checked everything and started the system. I decided to sync parity again and push the Parity Sync button. While the previous parity sync (with the drives directly attached to the motherboard) was performed with ~ 110 MB/sec. what i get now is something like 35-38 MB/sec. I explored the syslog and saw some strange warnings: The SASLP-MV8 controller is serving currently only the cache drive and the data and the parity HDD's are directly connected to the motherboard SATA ports. I am attaching the syslog here. Could you please put your thoughts about the situation here. I can't understand what might be the problem. syslog-2012-10-09.txt
  10. Today I spoke to the local Supermicro support where I returned my 2 weeks-old drive cage to be replaced. After massive test performed with 5 HDDs installed the cage didn't show any problems and the support informed me that they are going to send it back to me as a working device. I start thinking what may cause this problems and is it possible the 2 Molex connectors to be the reason for this issues? The sata cables are not faulty for sure as I am using them now connected directly to the mainboard and they perform well. My PSU is Corsair 430 (which is in the approved hardware list).
  11. I went back to RC5 and pulled out the disks from the Supermicro cage and all is fine (for now). Will RMA the cage too and will see what will happen. Currently preclearing the new parity drive and will add it in few hours. I think it is just a very bad coincidence....first my Parity showed bad sectors, than the data disk... and all this happen right after the uograde to RC8a. Probably just a bad luck. Lets see.
  12. Thank you dgaschk, The read-only problem was solved after I ran check-disk on the flash. Today I had the bad drive replaced by the seller and was rushing happily to install it as a new parity. My good mood was totally ruined when i got home and understood that DISK1 (data) is out of order too. The drive was kicked out of the array. I restarted the array and DISK 1 showed up as green too. When I decided to browse the shares I discovered that only the main folders are accessible and no way to see a single file. The disk just stops to respond. I start thinking that there is something wrong with RC8a version...or at least it does not work in my hardware. Now I am really scared because I still have no parity attached and my data is not protected. SMART test didn't show anything unusual....no errors, no pending sectors. What is interesting that there are some sata errors in my syslog file which I am attaching for review. Is it safe if I downgrade my fresh RC8a installation to RC5Aio? EDIT: I think I have found what is causing the problems. Two weeks ago I put a 3x5 Supermicro CSE-M35-T-1 drive cage and since then my problems started. I attached the HDDs directly to the sata ports and all is working (for now). Do you guys had experienced ever something like this? I am wondering now what may cause the errors: the Supermicro cage itself or the 4 pins molex connectors coming from the PSU? syslog-2012-10-03.txt SMART.txt
  13. I have just noticed that my flash drive is read only. I saw one log which was bigger than usually and decided to delete it when the system informed me it cant be done as the file-system is read-only. It seems to me that my entire system is getting slowly to dead. Am I safe to make a fresh install?
  14. After more then 17 hours preclearing of the drive I have the following message: SORRY: Disk /dev/sdc MBR could not be precleared. In addition no preclear log was saved in my log folder. I executed a smart test on the drive which showed 2 more Current_pending_sectors appeared (Log attached). Parity sync is not possible as it start with 1,7 MB/s and web interface stops responding. After I did everything possible to save the drive it is time to try to RMA it. It is the first failed drive in my 18 years computer experience. Thank you very much again for your support. SMART_Log.txt
  15. Thank you all. I will preclear the disk again...meanwhile I will speak to the seller to return it. Joe L.: I changed the data and power cables even before I wrote my first message here but this didnt solve the problem. All my disks are situated in a super micro hdd cage. I am wondering why parity sync starts with 6-7 MB/s. Will keep you informed. Best regards. Sent from my iPhone using Tapatalk
  16. Excuse me writing again but is this error due to a hardware error in the hdd and is it reparable somehow or is it irreversible? This error was not presented when I add it in unraid and 2 preclear cycles didn't show any errors and the disk is brand new. Is it possible to run some tools on the hdd to repair it? Thanks in advance. Sent from my iPhone using Tapatalk
  17. The parity build is failing because of errors 20 minutes after it starts. Then the system disable it. In case it is a hardware error I guess it is better to return this HDD and to use a new one.
  18. After a reboot the Parity disk is blue now. Please kindly find attached the SMART report log. EDIT: I started parity sync but the web interface become unresponsive and the speed is around 7 MB/s. log.txt
  19. I cant provide a SMART report. Here is what I have after I tried executing a smart test:
  20. Here is the new log. http://pastebin.com/VeudWn8j
  21. Thanks and sorry...we wrote in the same time. An excerpt from the syslog is attached on my previous post. As it is big i will upload it somewhere else.
  22. After following the advices of Joe L. from this two topics http://lime-technology.com/forum/index.php?topic=15385.0 http://lime-technology.com/forum/index.php?topic=5072.msg47122#msg47122 I finally have my Data Disk 1 green. I needed to put the command initconfig. After reassigning the drives a paritysync started automatically. What bothers me now is that it is doing it with 1.5 MB/s and the estimated remaining time is something like a few weeks. The web interface is almost not responding but I have access to my files. I will leave it this way never-mind how much time it will take to complete....but now I think something with the USB flash is not ok. Is it a good idea to start from scratch and get a new installation of the system? Thank you Joe L. Edit: The Pariti HDD is disabled now with a red dot. A new syslog is attached. log.txt
  23. Hi, I am using Unraid 5.0-rc8a on the following hardware: Asus P8H61-M-LE, CPU:Celleron G530, 4gb RAM. WD30EZRX- Parity WD30EZRX- Data Disk 1 WD7501AA- Data Disk 2 ST9500325AS- Cache All of the HDDs are attached to the mainboard sata ports except the cache disk which is attached to AOC- SASLP-MV8 controller. A red dot appeared on my Parity drive. I stopped the array and rebooted the server. A blue dot appeared next to the Parity drive and I start a parity sync. What I saw was a very slow and unusual speed at about 15-20 mb, while usually I have at arround 120. I did stop the parity sync and rebooted the server once more. What i saw was that this time not only the parity drive was orange, but also Data Disk-1 (WDEZRX) was red saying it is unformated. On the web interface for Disk 1 i see the following: File system type: unknown I rechecked all the cable connections and everything seems fine. All of the disks are visible in the Bios. I hope I did'nt lost everything I had. Please help me as I am lost here and dont know what to do next. Please find attached the syslog. log.txt