dmraid: unable to remove ddf1 metadata with CRC error
Robert Osowiecki <[email protected]> Tue, 8 Dec 2015 13:51:38 +0100
| Newsgroups | gmane.linux.ataraid |
|---|---|
| Message-ID | <CAPgkq_VSmOJ9HpypwONs-+LPLeAZ46xp3ikYoR0qt75jZN9SWw@mail.gmail.com> |
--===============1128442852411576490== Content-Type: multipart/alternative; boundary=047d7b10cd454031950526626fd4 --047d7b10cd454031950526626fd4 Content-Type: text/plain; charset=UTF-8 Hello, I hope it's a good place to submit problem with dmraid utility, maybe at least Mr Heinz Mauelshagen reads this mailing list? I had a bunch of 1T disks with following problem: ddf1: physical drives with CRC 7FFEB6, expected FFFFFFFF on /dev/sdf ERROR: ddf1: Cannot find physical drive description on /dev/sdf! ERROR: ddf1: setting up RAID device /dev/sdf >From my experience and from googling similar problems breaking CentOS/RedHat installation , I suspected removing metadata with dmraid -E might help, but it failed too: ERROR: ddf1: seeking device "/dev/sdc" to 512104901378048 ERROR: writing metadata to /dev/sdc, offset 1000204885504 sectors, size 0 bytes returned 0 ERROR: erasing ondisk metadata on /dev/sdc My coworker noticced, that dmraid tries to seek to position 512*1000204885504, which might be a bug caused by treating byte offset as number of sectors. Anyway, I manually zeroed those buggy metadata with dd, but I used dmraid dump metadata feature to save them in case anybody wishes to see them. Regards, Robert. --047d7b10cd454031950526626fd4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div><div><div><div><div>Hello,<br><br></div>I hope i= t's a good place to submit problem with dmraid utility, maybe at least = Mr Heinz Mauelshagen reads this mailing list?<br><br></div>I had a bunch of= 1T disks with following problem:<br><br>ddf1: physical drives with CRC 7FF= EB6, expected FFFFFFFF on /dev/sdf<br>ERROR: ddf1: Cannot find physical dri= ve description on /dev/sdf!<br>ERROR: ddf1: setting up RAID device /dev/sdf= <br><br></div>From my experience and from googling similar problems breakin= g CentOS/RedHat installation , I suspected removing metadata with dmraid -E= might help, but it failed too:<br><br>ERROR: ddf1: seeking device "/d= ev/sdc" to 512104901378048<br>ERROR: writing metadata to /dev/sdc, off= set 1000204885504 sectors, size 0 bytes returned 0<br>ERROR: erasing ondisk= metadata on /dev/sdc<br><br></div>My coworker noticced, that dmraid tries = to seek to position 512*1000204885504, which might be a bug caused by treat= ing byte offset as number of sectors.<br><br></div>Anyway, I manually zeroe= d those buggy metadata with dd, but I used dmraid dump metadata feature to = save them in case anybody wishes to see them.<br><br></div><div>Regards,<br= ></div><div>Robert.<br><br></div></div> --047d7b10cd454031950526626fd4-- --===============1128442852411576490== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ataraid-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/ataraid-list --===============1128442852411576490==--