adamgwaps

Nah i am serious, if ever i am going to hand it unsealed and just to be sure the recipient can test if its a real deal HDD.

Hi fellow unraiders, I’m hoping someone can help me out here. A while ago, a friend gifted me a Seagate HDD, but I’ve run into an issue with the RMA process. Seagate has agreed to honor the RMA, but only if the drive is shipped from a US address. The problem is, I’m based in Metro Manila, Philippines, and none of my friends are traveling to the US anytime soon. To make things even more complicated, shipping the drive from the Philippines to the US is tough because of corrupt customs practices here, and they require a lot of paperwork, which is nearly impossible to get. So, I’m reaching out to see if anyone here in the US is planning a trip to the Philippines soon and would be willing to help me with this? The plan would be for you to bring the drive back to the US, and Seagate will cover the shipping costs for the RMA. I’d be more than happy to make any arrangements to cover any fees and make it as easy as possible. Thanks so much in advance! I really appreciate any help you can offer! Best, Adam

Thank you so much for being with me in this journey Got it!

Thanks @JorgeB you are the best! any maintenance i should do? or can i proceed using my server normaly?

YAY! Is this real? what to do next can i just remove the damaged disk and replace with the rescued disk then import the zfs? Thanks in advance @JorgeB

HI guys, is this real? or will it eventually get faster as it gets to other part of the platter?

Just another update

Yup here is the smart of the failed drive.

Hi @JorgeB it restarted again and changed drive letter and again i resumed. (Just another Update)

Hi @JorgeB it did it again i think the drive is the culprit it seems it reset by itself i think it is safe to resume now.(Just an Update)

@JorgeB Perfect! I will redo it now then again i will update this thread if anything happens and again thanks for the fast reply!

@JorgeB asside from changing the ddrescue log file location is there anything else i should do?, do i need to format the destination drive or can i just start over just change the log file directory?

@JorgeB I meant i think while running ddrescue the disk identifier changed and it my have copied from another drive thus tainting the data and now that i reboot and it returned it may resume but the data cloned may be from another drive when the id changed and it resumed now to the correct drive thus the rescue data may not be reliable anymore(sorry if i cant explain it clearly)

Hi again @JorgeB i did and it resume to this is this correct? or should i start over? is this is normal?

Got it i read online that i should use -D if i encounter this error should i or should i proceed with your recommended command? Thanks again for the fast reply @JorgeB