Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.mint    |    Looks pretty on the outside, thats it!    |    30,566 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 29,329 of 30,566    |
|    RobH to Paul    |
|    Re: Cloned disk won't boot    |
|    19 Oct 25 10:04:19    |
      From: rob@despammer.com              On 16/10/2025 19:06, Paul wrote:       > On Thu, 10/16/2025 11:40 AM, RobH wrote:       >> On 16/10/2025 10:54, Paul wrote:       >>> On Thu, 10/16/2025 5:33 AM, Edmund wrote:       >>>       >>>> Appart ftom you confusing abbriviations... NUC HO G4.....so computers       right?       >>>> Cannot get in BIOS? what does the manual tell you, F12 F10 DEL check it       out.       >>>> First thing I would do is somehow COPY the files you need to a safe place.       >>>> Then try to fix the bootsector of the original SSD if it works       >>>> Then clonzilla       >>>       >>> I think there are now no files whatsoever on either drive, after a "dd       accident".       >>>       >>> There is no point blaming the UEFI for something, if       >>> the drives are actually empty.       >>>       >>> Using a LiveCD to boot the computer, I would examine the       >>> disks for "signs of life". The "gnome-disks" program       >>> can show whether partitions are present. If the storage       >>> devices are both blank, that's the answer, they're both blank.       >>>       >>> Paul       >>       >> Update:       >> No matter which ssd with either linux or win10 I tried, none of them booted       up in the Intel NUC. When I looked in the BIOS, it reported 'No Boot Drive'       with every disc I tried       >       > Boot from your DVD with Linux Mint on it,       > or your USB boot stick with Linux Mint on it.       >       > Then examine the storage devices in question,       > from the Live session acquired by using       > the DVD or the USB stick OS. You should       > be able to boot from *something* in your collection,       > to do your forensics and examine the storage       > for any sign of partitions whatsoever.       >       > The fact you are conversing with us, implies you       > can make installer media at any time, by downloading       > the LM ISO. Then make something that the I/O on the       > NUC can use (like a USB boot stick). If you are on       > Windows right now, you can use the USB prep software       > from rufus.ie (dev in Ireland). Either ecosystem can       > be used to make a boot media stick, to examine the       > storage on the NUC and determine how best to salvage       > the situation.       >       > Paul       >              Thanks for that.       I installed a ssd in my old laptop and then installed LM22.2 on it. I       then moved the ssd to the Intel NUC, and powered it up, but it would       boot up as the BIOS said there was no boot device.       So I then tried a usb stick with LM22.2 on the NUC to boot from, which       it did, but no install icon or anything else was loaded onto the       desktop, just a blank grey screen with the LM logo in the middle.       I then tried my Ventoy bootable usb stick which has LM22.2 on, but when       I selected to boot from that, the NUC just went a screen which said:              Intel Boot agent GE v1.53       CLIENT MAC ADDR: whatever it was or is       PXE-E53: NO Boot filename recieved              PXE-M0F: Exiting Intel Boot Agent              Reboot and select proper Boot device              Out of interest, I had a go at installing windows on the same ssd in the       NUC and it did ok.              Weird or what.              Thanks              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca