April 7, 201115 yr Hey guys i was going to upgrade to the 5.0 unraid i see said to go to 4.7 so i did by following steps - Copy the files bzimage and bzroot from the zip file to the root of your flash device, overwriting the same-named files already there. If present, delete these files from the flash (sorry, you will have to re-enter all your users after booting this release): config/passwd config/shadow config/smbpasswd I did not change the hard drives and when i reloaded i got this message on the webgui for one of my hard drives "Stopped. Replacment disk is too small." I dont know if you need hardware info or not i imagine this is all software related since everything has been working fine. thanks for taking your time to help...
April 7, 201115 yr looks as though you must be running a gigabyte mobo and you have theHPA issue that many speak of and I just dealt with myself. I recommend reverting to a pre 4.7 version to address the HPA issue and then upgrade. Same thing happened to me when I went from 4.6 to 4.7. I went back to 4.6, fixed HPA and then upgraded without issue. 4.7 I hear is a bit more strict so it throws this error while the earlier versions do not.
April 7, 201115 yr Author this is the mother board i have ASRock 890FX DELUXE3 AM3 AMD 890FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard but ill still look into what you said for sure thanks
April 7, 201115 yr Author from the looks of it the hpa is some type of option in the bios? can you tell me if im heading in the right track? thanks again (=
April 7, 201115 yr ASrock is not known to have the HPA problem. Was the drive ever in a gigabyte MB? In any case, see this thread: http://lime-technology.com/forum/index.php?topic=10866.0
April 7, 201115 yr Author so i tried some of these steps and aside from being confused/overwhelmed by this info i dont think its working out for me. very possible its user error..i typed in hdparm -N p1953513496 /dev/sde and i got this back /dev/sde: setting max visible sectors to 1953513496 (permanent) HDIO_DRIVE_CMD(identify) failed: Invalid exchange HDIO_DRIVE_CMD(identify) failed: Invalid exchange root@Whoshouse:~# any idea? At this point since i cant recall if this hdd was ever hooked up to a Gigabyte Mobo we arent even sure if this is my problem..any other avenues to explore?
April 7, 201115 yr Author ok just thought of something. so from what im reading about hpa it has something to do with creating a smaller partition? correct me if im wrong. but if you look back to my screen shot you will notice the sice disk 2 is the same in both locations so does this mean its probably not the HPA issue? thanks again sorry im a pest just anxious to figure this out so i can upgrade my UNRAID O.S.
April 7, 201115 yr Is the drive still red on the disk status page? Other methods are detailed. Have you tried them?
April 7, 201115 yr Author no drive is not still red. i started with v 4.5.6 but tried to go to 4.7 to make my way to 5.0 was suggested i DG to lower Version and fix hpa issues so im back to 4.6 no problems. but like i said i want to make my way to the newer version if at all possible. i dont really know what the issue is so dont know what exactly to try. i kind of think its not HPA issue but could be wrong..
April 7, 201115 yr It has all of the symptoms of HPA. There are other methods to try because the built-in command that can fix it doesn't always work. It depends on the drive and possibly MB. EDIT: Do you have this in your syslog: HPA detected: current 1953523055, native 1953525168 Follow the instructions for using HDAT2 described in the thread I posted earlier. Edit2: What does this command show: hdparm -N /dev/sde
April 7, 201115 yr Author i will try to do the hda2t thing or whatever it is ha. hdparm -N /dev/sde says /dev/sde: HDIO_DRIVE_CMD(identify) failed: Invalid exchange So i took out my flashdrive and opened up syslog is this the correct thing to do? well if it is no where in there does it say hpa at all...?
April 7, 201115 yr Are you absolutely sure that your disk2 is sde? From what you say, I'm guessing that sde is your flash drive. Try the command: hdparm -N /dev/sdX with X=a,b,c,d I'm guessing that sdc will report that HBA is enabled. I also note that your disk2 is an EADS model, when all the others are EARS. This suggests that disk2 may be older than the others and, possibly, has a history of use in other machines (one of which did have a Gigabyte motherboard).
April 8, 201115 yr Author first of all i would like to apologize for all my ignorance and stupid questions lol @PeterB no i am not sure my hidsk2 is sde? infact i only copied and pasted the command prompt from previously mentioned link. i do not know what all that is referring to sorry. when you say "with X=a,b,c,d" i am not sure what the letters are refering to? is it a=1 as in disk1? i tried a through d and here is what i got "/dev/sdb: max sectors = 3907029168/14715056(18446744073321613488?), HPA setting seems i nvalid (buggy kernel device driver?) root@Whoshouse:~# hdparm -N /dev/sda /dev/sda: max sectors = 3907029168/14715056(18446744073321613488?), HPA setting seems i nvalid (buggy kernel device driver?) root@Whoshouse:~# hdparm -N /dev/sdb /dev/sdb: max sectors = 3907029168/14715056(18446744073321613488?), HPA setting seems i nvalid (buggy kernel device driver?) root@Whoshouse:~# hdparm -N /dev/sdc /dev/sdc: max sectors = 3907027055/14715056(18446744073321613488?), HPA setting seems i nvalid (buggy kernel device driver?) root@Whoshouse:~# hdparm -N /dev/sdd /dev/sdd: max sectors = 3907029168/14715056(18446744073321613488?), HPA setting seems i nvalid (buggy kernel device driver?) root@Whoshouse:~#" as far as eads being older than ears im not sure entirely possible im sure you know the models better than i do so no argument there. I haven't been able to try the had2t yet @dgaschk was i correct in the location of sys log? found it in flash drive directory. and if so i searched for hpa and found nothing
April 8, 201115 yr Regardless of whether HPA is the cause, you can see that sdc is too small: /dev/sdc: max sectors = 3907027055 All of the other 2TB drives show the correct value of 3907029168. I suggest you try using HDAT2 to correct the size of sdc and the rebuild the contents. This disk has to be remedied in order to upgrade.
April 8, 201115 yr FYI, go to the devices page and for each disk you will see (sda), (sdb) etc as part of the data in the pull-down to select the hard drive. You can figure out which sdx device you need to use by looking there. Peter
April 8, 201115 yr Author The more i think about it the more im positive this HDD has never been on a gigabyte board but thats neither here nor there..did the HDAT2 thing and HPA was detected. Removed it. Just need to hook back up the system and let it rebuild the drive. then upgrade to 5.0 im sure this will work. you guys are awesome thanks for all your help. once i know its all good i will change title to SOLVED. Thanks again
April 11, 201115 yr Author ok so i was able to go to 4.7 now im trying to go to 5.0 which is the whole reason this started. heres what i did. stopped and powered down my system..put flash in my comp. replaces bzimage and bzroot overwriting the other files. deleted config/super.dat i know i would have to reassign the disks which is fine. i try to log in with the webgui and it wont connect will connect on server itself my user name is still the same i have an ipaddress i can see the server through my network however only the flash folder is available. so thats where im at cant log into webgui and cant see my user shares. please help thanks. i didnt create a new post incase the history of what i have done prior to this is important? thanks again ok so it started working randomly? thanks everyone for all your help i hope it continues to work well i will mark this as solved. @lionelhutz thanks for your info on sda.b.c. etc...my new drive however is hda and i dont know why?
April 11, 201115 yr I believe hda indicates an IDE device or in your case a SATA drive on a controller running in IDE emulation mode. You might be able to switch the controller to AHCI mode instead and possibly see a performance boost. Peter
April 12, 201115 yr Author interesting. any idea why this would happen? its brand new hdd its of course sata none of the others have done this? and im assuming this is taken care of in bios so ill look into thanks again appreciate it...takes so long to format 2tb then do parity ha (=
April 12, 201115 yr interesting. any idea why this would happen? its brand new hdd its of course sata none of the others have done this? and im assuming this is taken care of in bios so ill look into thanks again appreciate it...takes so long to format 2tb then do parity ha (= WinXP and prior have no SATA drivers, therefore the motherboard BIOS will often default to a legacy emulation of an IDE drive so the disks can be used to boot MS-windows. You do not want the legacy emulation mode in the BIOS. You want AHCI mode. (translation, it will work as an SATA drive, and take advantage of the higher speed interface available)
April 12, 201115 yr Author awesome thanks joe! this is probably the best community forum ive been to. no one has yelled at me for stupid questions...lol **so i found some options for ahci ide and i think something else i put everything i saw to ahci and it still says hda on my description? ill go back and look for more options but i was pretty sure i took care of all of them.? found one other setting in case someone refers back to this some time it was ide combined mode i changed everything else but that one and it did the trick. thanks again
Archived
This topic is now archived and is closed to further replies.