husky55
-
Posts
73 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by husky55
-
-
There are 5 sata connectors at 6Bbps on the ECS A885GM-A2. I do not see any option. I did remove the dvd burner and used the spin down and again, the system crashed. So dvd burner had nothing to do with it. I think I just give up at this point. The HP uses HP MB proliant for intel.
Thanks again.
-
This not an HP server. I have 2 servers. The HP is my main server and I have not touched it. The test server has the ECS MB which has the latest firmware.
-
Very perceptive Patilan. I did install a DVD burner into the sata ata1, probably had an extra burner. I will remove it. The BIOS settings are OK, no fancy stuff, sata was set to AHCI, no raid at all. Will check again though. This is quite an education for me. Did memtest already. No errors. Just wonder why the beta 5 did not have any problem if it was the sata controller issue. Is there something in 5 final which triggers the crash.
Let me see if removing the dvd burner will do the trick. Thanks again for your utility keeplogs. I would never get this far without it.
-
Wow, I was so sure that changing the sata cable would do the trick. But it crashed again. Here is the new syslog after the new crash.
UPDATE:
I did some more diagnostic. Have an extra sata connector on the ECS A885GM-A2 (V1.1) so I switched the Seagate cable into the new connector. 5.0 Final boots up fine, again, config and parity are valid. So I hit spin down and that exactly what I expected, system crashed again. Thanks for the keeplogs utils, I was able to recover the syslog:
Sep 19 09:25:52 Tower2 emhttp_event: svcs_restarted
Sep 19 09:25:57 Tower2 kernel: mdcmd (15): nocheck
Sep 19 09:25:57 Tower2 kernel: md: md_do_sync: got signal, exit...
Sep 19 09:25:57 Tower2 kernel: md: recovery thread sync completion status: -4
Sep 19 09:27:34 Tower2 emhttp: Spinning down all drives...
Sep 19 09:27:34 Tower2 kernel: mdcmd (16): spindown 0
Sep 19 09:27:35 Tower2 kernel: mdcmd (17): spindown 1
Sep 19 09:27:35 Tower2 kernel: mdcmd (18): spindown 2
Sep 19 09:27:36 Tower2 kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
Sep 19 09:27:36 Tower2 kernel: ata2: irq_stat 0x00400000, PHY RDY changed
Sep 19 09:27:36 Tower2 kernel: ata2: SError: { RecovComm Persist PHYRdyChg 10B8B }
So to summarize, new sata cable, new sata connector, same problem system crashed when spin down all drive occurred. So I plugged in the old beta 5.14 and went to the same boot up and spin down, no crash. From this, I can only reach the conclusion that 5.0 final is not compatible with the ECS MB somehow. I do not want to mess with my HP media server so I will keep it with the beta Unraid.
-
@dgaschk, thank you so much for the diagnostic. The SATA cable has latches so it was not loose, probably bad. I have replaced it with a brand new SATA cable also with latches. The Seagate is my disk2. I looked at the syslog after the crash. Noticed that the last few lines seemed to identify the problem but I am not sure how to interpret them:
"Sep 18 08:49:30 Tower2 kernel: mdcmd (16): spindown 0
Sep 18 08:49:30 Tower2 kernel: mdcmd (17): spindown 2
Sep 18 09:18:01 Tower2 kernel: mdcmd (18): spindown 1
Sep 18 09:18:03 Tower2 kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
Sep 18 09:18:03 Tower2 kernel: ata5: irq_stat 0x00400000, PHY RDY changed
Sep 18 09:18:03 Tower2 kernel: ata5: SError: { RecovComm Persist PHYRdyChg 10B8B }
Sep 18 09:18:03 Tower2 kernel: ata5: hard resetting link
Sep 18 09:18:03 Tower2 kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
Sep 18 09:18:03 Tower2 kernel: ata3: irq_stat 0x00400000, PHY RDY changed
Sep 18 09:18:03 Tower2 kernel: ata3: SError: { RecovComm Persist PHYRdyChg 10B8B }"
The problem occured after spindown. I assumed that ATA5 was the problem because PHY RDY changed and caused ATA3 to be frozen also.
Essentially, I am clueless.
Anyway, I will report if replacement of the SATA cable will do the trick. Thanks again for your help.
-
OK, my test server finally crashed and Patilan's keeplogs worked perfectly. Here is the syslog after the crash. Can this be fixed?
-
So I have been waiting for the 5.0 final to crash this morning. So far it hasn't. I ran Patilan keeplogs.sh so when it crashes I will upload the syslog hopefully. I really don't know why this is all happening. Attached is the syslog just downloaded (not crashed yet) So I don't think it tells the why and the how.
-
Just some clarification:
I assigned static IP to both servers outside the DHCP range. Same subnet different ip addresses. There are 2 repeater bridges with ddwrt and an Asus RT-N66U as the main router. There was no conflict of IP and/or IRQ.
The Main server is the HP Proliant in my signature. The test server has the ECS A885GM-A2 recommended by Raj in his various build prototypes. LAN is a gigaLAN Controller Realtek 8111DL, 8 MB RAM, DVD burner.
The test server crashed repeatably (5 times) with 5.0 final so this is not a random crash. On the other hand with beta 14 no crash no problem and, it was repeated about 5 times.
I downloaded Patilan's syslog utility and will use it when I have some time. I did use the beta 14 again on the test server, absolutely no problem of any kind. Configuration valid. Parity no error. All disk spinning green, no error read or write. No IP conflict ( wished there was one so I can fixed it, lol)
Could it be that 5.0 final does not like me?
-
I have read the last 15 pages of this forum and did not find an answer. I have struggled with this problem for more than a week. First off, I have an Unraid setup running very well as a media server with 5.14 beta.
I have built another unraid server just for testing the new 5.0 final. I have 3X2TB drives (parity, disk1 and disk2) in this server. This is just stock 5.0 final. All drives were precleared and the system boot up fine. Both the management utility and web control work fine. Parity check out perfect.
The problem was about half and hour after the parity check or add files to the drives, I can no longer access the server. By that, I mean no web access and no telnet and no console. Nothing. So I suspected hardware problem. but after doing intensive diagnostic for 2-3 days I am sure that the hardware is OK. So reloaded 5.0 final again, configuration valid, parity check no error again no access at all even with KB and mouse and monitor, screen just blank, no signal after about 20 minutes.
I checked the ECS MB and enabled all the wakeup funtions. Same results.
As mentioned above, my original Unraid media server is working fine. The problem is mainly with the test server and 5.0 final. When loaded with the 5.14 beta, the test server run perfectly. I have run parity check over and over. For the server I assigned a static IP so I can find it. That was not a problem as right after loading 5.0 final, I can access the server and can transfer files and stream. I did install unmenu in the 5.0 final. It was working fine. And then after a while with no activity, everything stopped.
-
Can the Popbox V8 be the problem? With 5.0Beta14, I had no problem with the V8.
-
You're creating your own issues. If you're running the RC's and have run the new permission script and have your shares set to public then any computer has full access them.
Are you running programs or doing work directly on the server? I haven't had one permission issue that wasn't self inflicted by doing file work directly on the server.
My disks are set to public, ran the new permission script, when my Popbox V8 tried to access, I got the log on screen demanding user ID and password which I have never used. Tried to create a new user with password, Cannot sign with new user!!! 5RC11 did something bad since the 5Beta14 worked perfectly, no log on ever showed up. Please some body tell me how to get rid of this log on screen since I would want to build a newer server using the new 5 final and not my 5Beta.
-
I have a Popcorn V8 connected to my Unraid to play movies. Unraid 5.0 Beta14 ran perfectly. But I heard that Unraid 5.0-RC11 was pretty stable so I upgraded. I have spent the better part of 2 days trying to get rid of the log on screen on my Popbox V8 to Unraid. With version 5 beta 14 there was no log on screen. I ran the new permission several times to the same effect. I tried to add a new user and PW and can not sign in with that either.
So I reverted back to 5Beta14 and got rid of the log on screen. I never had any user ID nor PW. I am nobody-users as per the new permission. One day soon, I need to upgrade to 5 Final, how do I get rid of the log on screen?
Update: So I tried again. Installed 5.0-RC11, ran the new permission, check that all the disks were set to public. In short everything were the same settings as in 5.0Beta14. And same results again, new log on screen, Tried to create a new user with password, cannot sign in no matter what.
Does anybody know how to get rid of the log on screen except by reverting back to 5.0Beta14? Thanks in advance.
Update 2: No matter what 5.0-RC11 did something to my server (details in my signature below), the damned log on screen prevent any use of my server. I just found it exasperating to have problem with a near final release. May be it's not happening to anybody else since nobody seems to have any idea of what I am talking about.
-
That's normal and setup by default by the Seagate firmware. I actually used 254 to reduce the chirping noise and head parking and not to shutdown the APM. There was some talk that Seagate engineers knew about the problem but elected to use 128 APM because of reliability issues. Not sure about that, but I am just playing it safe.
-
I am fairly sure that the APM (Advanced Power Managment) of these drives were defaulted to ON and caused clicking sound when idle i.e. head parking. If anybody knows how to disable the APM of these Seagate drives already installed in Unraid please let me know.
Some have reported that HDPARM utility can disable the APM. I am unfamiliar with this and alread posted in the Support section.
"HDD APM explained in brief
The Advanced Power Management feature present in virtually all modern hard disk drives is aimed to save energy and power supply by regulating the performance of the hard disk drive. Power consumption is reduced by parking the drive heads when the disk is not in use, by adjusting spin speeds, and disabling internal components when not in use. Aggressive power saving settings allow the hard disk drive to stop its spindle motor and park heads more frequently, which allows saving as much energy as possible, but leads to increased deterioration of mechanics and delays on drive reads caused by waiting the magnetic disks to spin up to the necessary speed. In other words saving energy is achieved by decreasing performance and to a certain extent shortens drive life."
Did you have any luck turning it off? hdparm -Z /dev/xxx didn't seem to do the trick for me.
FYI:
== Last Cycle's Pre Read Time : 6:02:43 (137 MB/s)
== Last Cycle's Zeroing time : 15:48:04 (52 MB/s)
== Last Cycle's Post Read Time : 12:46:29 (65 MB/s)
Try hdparm -B 255 /dev/xxx
Verify with -I . Let me know if that works for you.
-
Thank you Joe. I really appreciate your help. I have learnt so much from you. My server is running fine right now. I am really apprehensive about fixing what's not broken !!! But I am a tinkerer by nature !!!
-
I am fairly sure that the APM (Advanced Power Managment) of these drives were defaulted to ON and caused clicking sound when idle i.e. head parking. If anybody knows how to disable the APM of these Seagate drives already installed in Unraid please let me know.
Some have reported that HDPARM utility can disable the APM. I am unfamiliar with this and alread posted in the Support section.
"HDD APM explained in brief
The Advanced Power Management feature present in virtually all modern hard disk drives is aimed to save energy and power supply by regulating the performance of the hard disk drive. Power consumption is reduced by parking the drive heads when the disk is not in use, by adjusting spin speeds, and disabling internal components when not in use. Aggressive power saving settings allow the hard disk drive to stop its spindle motor and park heads more frequently, which allows saving as much energy as possible, but leads to increased deterioration of mechanics and delays on drive reads caused by waiting the magnetic disks to spin up to the necessary speed. In other words saving energy is achieved by decreasing performance and to a certain extent shortens drive life."
-
I recently installed a couple of Seagate drives in my Unraid 5.14B. The Seagates have APM (Advanced Power Management) ON by default. To disable it (clicking noise, head parking etc...), one can use HDPARM tool or so I was led to believe.
My question is " Does Unraid support the HDPARM utility?" Can I just use Putty to connect to my server and use HPPARM on each drive? Or is there an easier method?
There is a Windows version of HDPARM, can I use this to disable APM in my Unraid drives if Unraid does not support HDPARM?
-
Thanks guys, all upgraded and whatnot. Parity rebuild on the 3Tb running now. Have kept the old parity drive out of the array till I am 100% up and running with the new drive but it all looks peachy so far.
Thanks again for the help
PS: How do I mark the thread solved?
Click on the Modify at the right hand side of your post and changed your title to SOLVED.
-
Same here. Working fine in Unraid, fast and cool. Here is the info on the drive:
=== START OF INFORMATION SECTION ===
Device Model: ST3000DM001-9YN166
Serial Number:
LU WWN Device Id: 5 000c50 *****
Firmware Version: CC9E
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Sun Jul 15 09:40:10 2012 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
-
Seagate 3TB Goflex Desk Usb 3.0 $119.99 after $20 IR - Starting July 22nd thru August 5th at Costco BM.
-
A word of caution about this drive, I ordered 4 to add to my server, 1 was DOA, the 2nd died 10 hours into preclear, the other 2
are still preclearing, at a 50% failure rate so far, I am not sure I want to trust these drives, YMMV.
Look at the date of manufacture on the drive. I have 2 of the ST3000DM001 manufactured in China on 04/2012 firmware CE9E with the power down option turned off by default. The 2 drives have been precleared and added as data drives. They seem to be OK so far. There is apparently some firmware available for older drives.
-
Thank you. That is exactly what I will do.
-
Only the original disk1 and disk2 data drives (3TB drives) have data that I do not want to lose. The newer disks ( 1 and 2 TB drives) have only test data and movies that were duplicates so can be deleted.
-
Thank you so much. I have 2 data drives full of music and movies and do not want to lose it. I was having both servers going but would like to simplify my life (or complicate it further) by combining them into one.
Very strange and frustrating problem...
in unRAID 5.x OS Issue List
Posted
Assuming that the ECS (EliteGroup) A885GM-A2 (V1.1) sata controller is somehow at fault, what MB would you recommend for an unraid 5.0 final trouble free build. I understand that there is always the possibility of problems/gliches but I really do want to upgrade to 5.0 final as I know that Tom has been working on it for years. Frankly I love the 4.7. I had to upgrade because of the 3tb hd issue. All I ever wanted from unraid was a reliable media server, although I realize that there are many who want security etc...My problem is I am hesitant to commit to a beta version (which is serving me well on 2 servers) for the future so I am willing to build a new server for the 5.0 final.