February 20, 201115 yr Hi All, I had HPA on all 4 data drives except my parity. I removed it with the hdparm command, rebooted, accepted the new disk sizes, checked parity, it corrected 265 errors on each disk and is now fine. However whenever i start the share or reboot im getting 1 error on each of the drives that HPA was on. see below. anyone know what this means? Feb 20 19:54:23 SERVO kernel: attempt to access beyond end of device Feb 20 19:54:23 SERVO kernel: sdc1: rw=0, want=3907029104, limit=3907026991 (Drive related) Feb 20 19:54:23 SERVO kernel: md: disk4 read error (Errors) Feb 20 19:54:23 SERVO kernel: handle_stripe read error: 3907029096/4, count: 1 (Errors) Feb 20 19:54:23 SERVO kernel: attempt to access beyond end of device Feb 20 19:54:23 SERVO kernel: sdb1: rw=0, want=3907029104, limit=3907026991 (Drive related) Feb 20 19:54:23 SERVO kernel: attempt to access beyond end of device Feb 20 19:54:23 SERVO kernel: sdf1: rw=0, want=3907029104, limit=3907026991 (Drive related) Feb 20 19:54:23 SERVO kernel: attempt to access beyond end of device Feb 20 19:54:23 SERVO kernel: sdd1: rw=0, want=3907029104, limit=3907026991 (Drive related) Feb 20 19:54:23 SERVO kernel: md: disk1 read error (Errors) Feb 20 19:54:23 SERVO kernel: handle_stripe read error: 3907029096/1, count: 1 (Errors) Feb 20 19:54:23 SERVO kernel: md: disk2 read error (Errors) Feb 20 19:54:23 SERVO kernel: handle_stripe read error: 3907029096/2, count: 1 (Errors) Feb 20 19:54:23 SERVO kernel: md: disk3 read error (Errors) Feb 20 19:54:23 SERVO kernel: handle_stripe read error: 3907029096/3, count: 1 (Errors) Feb 20 19:54:23 SERVO kernel: reiserfs_resize: can't read last block Feb 20 19:54:23 SERVO last message repeated 3 times
February 20, 201115 yr Hi All, I had HPA on all 4 data drives except my parity. I removed it with the hdparm command, rebooted, accepted the new disk sizes, checked parity, it corrected 265 errors on each disk and is now fine. However whenever i start the share or reboot im getting 1 error on each of the drives that HPA was on. see below. anyone know what this means? Feb 20 19:54:23 SERVO kernel: attempt to access beyond end of device Feb 20 19:54:23 SERVO kernel: sdc1: rw=0, want=3907029104, limit=3907026991 (Drive related) Feb 20 19:54:23 SERVO kernel: md: disk4 read error (Errors) Feb 20 19:54:23 SERVO kernel: handle_stripe read error: 3907029096/4, count: 1 (Errors) Feb 20 19:54:23 SERVO kernel: attempt to access beyond end of device Feb 20 19:54:23 SERVO kernel: sdb1: rw=0, want=3907029104, limit=3907026991 (Drive related) Feb 20 19:54:23 SERVO kernel: attempt to access beyond end of device Feb 20 19:54:23 SERVO kernel: sdf1: rw=0, want=3907029104, limit=3907026991 (Drive related) Feb 20 19:54:23 SERVO kernel: attempt to access beyond end of device Feb 20 19:54:23 SERVO kernel: sdd1: rw=0, want=3907029104, limit=3907026991 (Drive related) Feb 20 19:54:23 SERVO kernel: md: disk1 read error (Errors) Feb 20 19:54:23 SERVO kernel: handle_stripe read error: 3907029096/1, count: 1 (Errors) Feb 20 19:54:23 SERVO kernel: md: disk2 read error (Errors) Feb 20 19:54:23 SERVO kernel: handle_stripe read error: 3907029096/2, count: 1 (Errors) Feb 20 19:54:23 SERVO kernel: md: disk3 read error (Errors) Feb 20 19:54:23 SERVO kernel: handle_stripe read error: 3907029096/3, count: 1 (Errors) Feb 20 19:54:23 SERVO kernel: reiserfs_resize: can't read last block Feb 20 19:54:23 SERVO last message repeated 3 times please attach your entire syslog. It is impossible to know what is happening without it. Joe L.
February 22, 201115 yr Feb 20 20:17:22 SERVO kernel: attempt to access beyond end of device Feb 20 20:17:22 SERVO kernel: sdc1: rw=0, want=3907029104, limit=3907026991 It loks as if you used the wrong value in the hdparm command. See here: http://lime-technology.com/forum/index.php?topic=10866.0 And here: http://lime-technology.com/forum/index.php?topic=10858.msg103515#msg103515
February 22, 201115 yr Author I am almost 100% positive that i used the right value, i checked my old syslog log for the native value and also checked what was printed on the drive itself. It is almost as if the system can now see the hpa area but cannot access it, if that makes sense?
February 22, 201115 yr I am almost 100% positive that i used the right value, i checked my old syslog log for the native value and also checked what was printed on the drive itself. It is almost as if the system can now see the hpa area but cannot access it, if that makes sense? What does hdparm -N /dev/sdX now show for that drive?
February 22, 201115 yr Author Hi Joe, root@SERVO:~# hdparm -N /dev/sdb /dev/sdb: max sectors = 3907029168/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?) root@SERVO:~#
February 22, 201115 yr Author Joe, I ran that command for the rest of my drives, including parity and a brand new pre cleared 2tb ears and it came up with the same result for all of them...?
February 22, 201115 yr Joe, I ran that command for the rest of my drives, including parity and a brand new pre cleared 2tb ears and it came up with the same result for all of them...? I'll agree with the output... The HPA as read by the kernel seems invalid. I'd use a different tool to set the HPA on that drive. It appears as if on your disk controller/motherboard/disk/linux version, hdparm is not working. Joe L.
February 22, 201115 yr Author Joe, Should i use a different tool and set it for all drives (since its showing invalid on all of them) or just the drives that originally had HPA? ps, i really appreciate your help and knowledge
February 22, 201115 yr Joe, Should i use a different tool and set it for all drives (since its showing invalid on all of them) or just the drives that originally had HPA? ps, i really appreciate your help and knowledge Don't worry about the weird values drives. (With impossibly large values) Only need to do it with those originally identified. (The tools should only work on one drive at a time, and you should too, since unRAID will consider them new drives since their size changes. If you do not have them assigned to the array is is not an issue, but if assigned, only change one, then re-start the array, let it re-construct the one drive, then do the next, etc...)
February 24, 201115 yr Author Hi all, thought i would give an update So i removed 1 of my 2tb drives (a seagate with CC35). i tried removing the hpa with dos seatools. It didnt work I then used hdat2 tools for dos and tried a 48 bit permanent removal. that didnt work then i tried the 28 bit removal, that also didnt work, i tried several combinations of the two as per the hdat forums without success, i also tried the automatic method. I then tried doing a factory restore using hdat2, this seemed to permanately wreck my drive and it could no longer be read properly. So ive just bought a new eads 2tb to replace it, and it is now currently rebuilding. Has anyone else ever had Hdat2 not be able to remove HPA?
February 24, 201115 yr Hi all, thought i would give an update So i removed 1 of my 2tb drives (a seagate with CC35). i tried removing the hpa with dos seatools. It didnt work I then used hdat2 tools for dos and tried a 48 bit permanent removal. that didnt work then i tried the 28 bit removal, that also didnt work, i tried several combinations of the two as per the hdat forums without success, i also tried the automatic method. I then tried doing a factory restore using hdat2, this seemed to permanately wreck my drive and it could no longer be read properly. So ive just bought a new eads 2tb to replace it, and it is now currently rebuilding. Has anyone else ever had Hdat2 not be able to remove HPA? Did you remove power from the disk in between each attempt at setting the HPA. The disk itself will only allow one change per power cycle. Glad you are re-constructing the disk. Sometimes it is just the easiest route. Joe L.
February 24, 201115 yr Author Hi Joe, yes as per instructions for hdat i completely removed power from the disk (disconnected power cable) after each operation the sad thing is, i still have another 3 discs in the same situation (with hpa), i might just leave them for the time being...
February 24, 201115 yr Hi Joe, yes as per instructions for hdat i completely removed power from the disk (disconnected power cable) after each operation the sad thing is, i still have another 3 discs in the same situation (with hpa), i might just leave them for the time being... Just checking... Oh well, I see an RMA in your future
February 24, 201115 yr If hdparm, hdat2, and Seatools all fail to remove HPA I hope that you can RMA the drives. I've not heard of Seatools failing before, perhaps the manufacturer can advise you.
Archived
This topic is now archived and is closed to further replies.