It was also actually pretty fun!

116 points

Give me more of this and less of the politics. This is what I come to Lemmy for.

permalink
report
reply
9 points

subscribe to the linux comms and not to the politics comms

permalink
report
parent
reply
-17 points

Weird

permalink
report
parent
reply
20 points

No, you

permalink
report
parent
reply
51 points
*

Impressive, sounds like magic, tbh! You know any tutorials?

permalink
report
reply
88 points

Not really, I pulled it together from a bunch of random posts lol

Maybe I should write one, but in essence you:

  • Stop all non-OS essential services

  • Create a filesystem in a chunk of RAM

  • Pull essential OS files from the installed OS into it recreating needed directories (Though you could probably just use a tiny pre-built distro but meh)

  • Pivot root into it

  • Reload services (when they restart they’ll be restarted in the context of where you pivot rooted, prior they’re still running under the context of the installed OS)

  • Unmount the boot drive

  • Then do what ever you need to do

  • ???

  • Profit

permalink
report
parent
reply
25 points

How exactly so you pivot root? Simply chroot or something more involved?

permalink
report
parent
reply
73 points

chroot isn’t enough, you need “real” pivot_root

chroot just changes the shells root point, pivot_root actually changes the root mount point and enables this trick to work

permalink
report
parent
reply
1 point
15 points

I work in this field and I think this is 🔥 af

permalink
report
parent
reply
6 points

FYI you can use kexec and a prepared initrd to do something similar with only one command.

permalink
report
parent
reply
3 points

Imagining this process, despite having never done 50% of the steps on the list, makes my brain imagine this:

permalink
report
parent
reply
27 points

Yeah, I’d love to see a write up on this to follow.Sounds like useful practice in the lab if nothing else.

permalink
report
parent
reply
3 points

i experimented with this some time ago, see my post here: https://lemmy.ml/post/18706002/12772832

permalink
report
parent
reply
28 points

What happens if the SSH session closes before dd finishes? Sounds pretty badass but I don’t think I would trust this approach in prod lol

permalink
report
reply
32 points

Well the 1 SSH session bit was for dramatic meme-effect lol, you can actually connect back without issue (at least it did for me) so worst case if you weren’t working in tmux you’d just have to start dd again

Worst worst case, you’d just end up back where you were probably heading before anyways, KVM/IPMI

permalink
report
parent
reply
6 points

Sure, I suppose as long as sshd is up and running in the ramdisk environment (which you mentioned in another comment, along with all other services) you could always reconnect. Very neat and clever!

permalink
report
parent
reply
10 points

You could use screen or tmux for a persistent terminal session.

permalink
report
parent
reply
11 points

True, but I was more thinking about the issue of reconnecting in general when you just nuked sshd.

permalink
report
parent
reply
2 points

As long as you only copy off the disk, you can just reboot and the whole system in RAM vanishes and the normal system boots again for the second try.

permalink
report
parent
reply
1 point

Maybe run ssh on 2 different ports?

permalink
report
parent
reply
24 points

I also vote for a writeup. This sounds awesome!

permalink
report
reply
21 points

Can someone ELI5? Are you freefloating an operating system on your RAM?

permalink
report
reply
36 points

I had a server I rented from a provider in a data center and I wanted to image (dd) the drive for archival before I decommissioned it from my infrastructure.

Normally, you can’t really do that with the OS running and you would have to shut down and insert a live USB or something and temporarily boot from that. The server being a faraway rental the only option was to open a ticket so that they could enable an out-of-band management option like KVM or IPMI. Which would allow you to control a machine as if you had a physical monitor, keyboard and mouse in front of you. With that you can attach flash drives, shutdown, restart, see the POST/BIOS/UEFI screens etc remotely .

But, I didn’t want to wait 6-8 hours for them to enable that so instead I put together a process that would “boot” me into another distro “installed” into a RAM disk (kinda like how live CD/USB works) from the currently installed and running OS without rebooting

From there I could unmount the boot disk and do what ever I wanted from there, I could have even wiped the disk entirely and installed a entirely different distro if I wanted

permalink
report
parent
reply

How do you do that? What minimal distro did you use? Did you make it yourself? How reliable is pivot-root? How many tries did it take you to do that successfully?

permalink
report
parent
reply
17 points

RAM is still memory, so you can put anything in there, like an OS.

With pivot_root, you can change where the root is. So you pivot into your OS in RAM, which becomes the root of the system.

At that point, you can do pretty much anything you would normally do with your OS, like unmount a HDD.

I’ve never personally done it, but that’s a simplified explanation of what OP did.

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

I use Arch btw


Sister communities:
Community rules
  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

Community stats

  • 7K

    Monthly active users

  • 885

    Posts

  • 14K

    Comments