wewantrice Posted January 3, 2011 Share Posted January 3, 2011 Hello all, Been running unRAID server for about 3 years now without any problems. Currently running 4.6 Final. Tried to do a quick forum search but I didn't really see a solution. Today I decided to transfer the array into an Antec Twelve Hundred case. Stopped the array, powered down and uneventfully moved everything over. Booted up, reassigned drives and noticed a red ball next to one of my disks due to a replacement disk being too small. Completely perplexed here, as this is the same drive I've been using. I've rebooted the array, checked power and SATA cables to no avail. My syslog is attached, any input would be greatly appreciated. -Mark syslog.txt Quote Link to comment
BRiT Posted January 3, 2011 Share Posted January 3, 2011 You're a victim of HPA (Host Protected Area). You have it on multiple drives. You need to look into it and do a lot of reading before moving on to dealing with it. Odds are you have your drives connected to a Gigabyte motherboard or at one point in time had them in a system with a Gigabyte board. http://lime-technology.com/wiki/index.php?title=UnRAID_Topical_Index#HPA Jan 4 03:06:08 Tower kernel: ata5.00: HPA detected: current 1465147055, native 1465149168 Jan 4 03:06:08 Tower kernel: ata5.00: ATA-8: WDC WD7500AACS-00D6B1, 01.01A01, max UDMA/133 Jan 4 03:06:08 Tower kernel: ata5.00: 1465147055 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jan 4 03:06:08 Tower kernel: ata10.00: HPA detected: current 1953523055, native 1953525168 Jan 4 03:06:08 Tower kernel: ata10.00: ATA-8: WDC WD1001FALS-00J7B0, 05.00K05, max UDMA/133 Jan 4 03:06:08 Tower kernel: ata10.00: 1953523055 sectors, multi 16: LBA48 NCQ (depth 0/32) Jan 4 03:06:08 Tower kernel: ata10.00: configured for UDMA/100 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.