Timeline for Why does replacing drive with a dd clone cause machine to hang at boot?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2019 at 16:14 | comment | added | Rusi | Remember "dpkg --get-selections" to speed up making a new install replica of old. And thanks the accept even tho not exactly the solution | |
| Feb 26, 2019 at 10:41 | comment | added | Nick Bailey | Still booting from MBR of the new drive. Seems happy over USB. The machine locks up if the drive is plugged in to either the MB SATA controller or the additional PCI slot one. It locks up so early in the boot sequence you can't even get to the bios screen. The bad blocks on the old drive were actually in the swap partition, so I've essentially got a mirror of the entire system now. Since we've unfortunately had to start running Plex Media Server because the "smart" TV isn't, I shall end up rebuilding the machine in the medium term, so that's a solution for now. | |
| Feb 26, 2019 at 10:34 | comment | added | Rusi | So where's the working grub now? | |
| Feb 26, 2019 at 10:27 | comment | added | Nick Bailey | was quite right: in this case it was a hardware mismatch issue I have no total solution, but the new drive is now in an enclosure connected via USB. This ended up being bootable into the original media-server system, or a fresh install of Debian 9 with a desktop, selected from the grub menu at boot time. I also found some reports about SATA3 being incompatible with SATA1 from 2011. It isn't, but the symptoms were the same, so I'm blaming the 4k sectors for this. In the 2011 case, a bios upgrade resolved the issue, but I don't think that's available to me. | |
| Feb 26, 2019 at 10:21 | vote | accept | Nick Bailey | ||
| Feb 25, 2019 at 11:31 | comment | added | Rusi | In that case kindly upvote! | |
| Feb 25, 2019 at 11:28 | comment | added | Nick Bailey | Sure. If I do it at work it'll look like I'm working ;) I'll do a bit more testing and report back. Thanks for the comprehensive answer and the heads up on the gpt. Hoping it doesn't have to be partition 1, but p3 /boot is already before P1 so it needs a tidy up anyway. | |
| Feb 25, 2019 at 10:57 | comment | added | Rusi | «Old MB wont talk SATA-3»: Easy enough to verify (without multiplying variables) by: Fresh-install on Old MB+New Disk. Dont you think? | |
| Feb 25, 2019 at 10:49 | comment | added | Rusi | dd: Whatever works!!! BBP: Added clarification in reply. Yes it must be made and marked as such because that tells grub "you are free to mess around in here" | |
| Feb 25, 2019 at 10:49 | history | edited | Rusi | CC BY-SA 4.0 | BBP clarification |
| Feb 25, 2019 at 10:41 | comment | added | Nick Bailey | Thanks, Rusi! Yes, sorry to mention dd-ing disks in stack overflow ;) Asreply above, I tried to behave like a grown-up at first and did a dump restore into fresh partitions then grub at first. I don't understand how the disk "prefers" gpt? Does the BBP have to be an actual partition or can it be empty space? I left 6MB before part-1 having aligned them to 4K in case that was it (using gparted on a laptop with a USB-SATA interface). I can chroot into the new hd by booting from CD and hot plugging: the disk works. Will test on a machine at work and report. Maybe old MB won't talk SATA-3 (?) | |
| Feb 25, 2019 at 5:56 | history | answered | Rusi | CC BY-SA 4.0 |