Copying an OS to a SSD - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111) +--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114) +--- Thread: Copying an OS to a SSD (/showthread.php?tid=11889) |
Copying an OS to a SSD - ab1jx - 10-20-2020 This is probably not the normal way to do it, but I installed the mrfixit image to an SD, updated it to Buster, seems to work fine. Now I'm trying to copy it to my 1 TB Intel SSD. I made a 1 GB (generous) FAT32 partition and a 200 GB ext4 with gparted on the SSD. Then following piclone's example I used cp -ar to copy the files in the partitions on the SD to the SSD. Then edited the root= specification in extlinux.conf on it to the nvme path. But it doesn't boot, it boots the eMMC instead. My notes: Code: ssd: I copied a Raspberry Pi SD to a USB hard drive and got it booting this way once. Maybe I forgot something here. Duh, forgot up update the /etc/fstab on the SSD, working on that but it's time to eat. RE: Copying an OS to a SSD - wdt - 10-20-2020 On a non-booted image,,, dev, proc, sys, run are empty directories RE: Copying an OS to a SSD - ab1jx - 10-20-2020 Right, traditionally there there are fstab entries for mount points. I just tried Code: /dev/nvme0n1p1 /boot vfat defaults 0 2 I don't know anything about uboot but I was hoping to fake it by copying a working sd. RE: Copying an OS to a SSD - ab1jx - 10-21-2020 OK, this seems odd. I created the partitions in gparted but remembered that I hadn't specified mountpoints in it. There's no place to do that. There is for the eMMC, I don't see why one has them and the other doesn't. Notice this doesn't show mount point options The exclamation point has to do with not finding superblocks. Gparted isn't quite right in places, I knew that. There are superblocks: Code: mke2fs -n /dev/nvme0n1p2 There's nothing I have to do to set the boot order as I recall. Actually I'm not sure what mke2fs is really doing here. I think it isn't actually finding superblocks, it's calculating the locations based on drive size, block size, etc. It's more theoretical than an observation. Probably the right thing to do is study man pages, blow away this partition, write a little script that feeds all the right arguments to mke2fs (and fdisk), then copy the contents in from the sd again. It usually takes me a few tries before I get a drive set up the way I want it. Seeing that eMMCs are starting to fail ups the priority, I can't use one of those forever. RE: Copying an OS to a SSD - ab1jx - 10-21-2020 Well, that didn't help,it still boots the eMMC. I have a serial console adapter somewhere. Seems like there should be some log files. The official answer of course is at the wiki, I just hadn't looked at it in a while. https://wiki.pine64.org/index.php?title=Pinebook_Pro#Using_as_OS_root_drive I was so impressed with the 180 year MTBF that I bought another of these Intel SSDs, the 2 TB version, and put it in a USB housing I got from NewEgg. That's probably as close to permanent storage as you can get since even CDs and DVDs develop bad spots after years. It's plugged into a Raspberry Pi downstairs. I have 3 or 4 1-2 TB hard drives I've put in USB adapters, they can float around. And when they aren't mounted they aren't spinning or wearing out. I can stick any of my old hard drives into a USB adapter temporarily to retrieve a file so I've let my dinosaur computers die off. RE: Copying an OS to a SSD - ab1jx - 10-21-2020 Tinkering, I see there's an nvme-cli deb out there, so I installed it. And duh, it has a man page. It looks quite well evolved: Code: nvme-1.0 nvme list shows me: Code: nvme list From what I'd read I was thinking I'd have to download and build something. It even has SMART. Don't know if there's any support for USB-connected nvme. There's also nothing in there for booting from an nvme device so I'll probably still have to build something. Oh, OK, in /dev I see: Code: nvme0 My SMART log: Code: Smart Log for NVME device:nvme0 namespace-id:ffffffff RE: Copying an OS to a SSD - ab1jx - 10-31-2020 But I didn't get much farther. I have my nvme in my fstab as noauto (mount) and I boot from my eMMC, which I made a backup of. I guess that's good enough for now. I'm on the arm debian mailing list and I think I could install official Debian on here if I rummage around and find my serial console cable. Supposedly once it's installed it can drive the video, the standard Debian installer works. Not sure about the nvme though. https://www.debian.org/releases/buster/arm64/ch05s01.en.html RE: Copying an OS to a SSD - ab1jx - 11-29-2020 Just tinkering with something else, if I boot from a mrfixit image, I can see the nvme and mount and use the partitions on it. I was quite surprised by this. I don't know if it contains a driver or if I managed to install the driver somewhere else. The same thing also happens with Daniel Thompson's Bullseye installed on an SD. What I'd really like is Bullseye booting from the nvme. But I don't want GPT and I don't want umpteen partitions. And I'd like to not have any Manjaro in there. But for now I mount my 700 gb partition on the nvme as /data and it's fairly workable. Maybe I should manually do a debootstrap onto it. I left a 1 GB partition for /boot, I have a 10 GB swap and a 4 GB hibernate. 196 GB to install the rest of Linux into, but leave my 700 GB alone. |