Skip to main content
17 events
when toggle format what by license comment
Oct 16 at 7:21 answer added Derek Sisco timeline score: 0
Sep 12, 2023 at 15:58 answer added Fadeway timeline score: 1
Sep 6, 2023 at 20:30 answer added imz -- Ivan Zakharyaschev timeline score: 0
Jun 22, 2020 at 23:12 answer added aluchko timeline score: 9
Nov 21, 2017 at 8:01 answer added Petr Ketner timeline score: 15
Mar 10, 2017 at 22:57 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Feb 7, 2017 at 8:31 answer added GAD3R timeline score: 6
Feb 7, 2017 at 8:17 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Jan 4, 2017 at 2:01 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Jun 24, 2016 at 18:36 history edited Gilles 'SO- stop being evil' CC BY-SA 3.0
clarified based on comments
Jun 24, 2016 at 11:56 answer added Martin von Wittich timeline score: 2
Jun 24, 2016 at 7:57 comment added MathematicalOrchid @Gilles I'm pretty sure it's actually initramfs. Not sure if it actually makes a difference though; either way, I've got a mini filesystem and I need to mount the real filesystem. (OpenSUSE, in case it matters.)
Jun 23, 2016 at 22:40 comment added Gilles 'SO- stop being evil' Is it actually an initrd, or an initramfs? (Just because the file is called initrd doesn't mean that it's one: most distributions have switched to initramfs but keep calling the file initrd.) What distribution are you using (as what the initrd/initramfs does depends on what the distribution put there)?
Jun 23, 2016 at 15:13 comment added Martin von Wittich @EricRenouf manually booting the full system may very well be the easiest way to fix such an issue. I had problems in the past where the initramfs failed to open my cryptsetup-luks encrypted root partition, and the easiest fix was to manually boot it and then run update-initramfs -u. I absolutely couldn't get it working when I just chrooted into the root filesystem from a rescue system; the resulting initramfs was always broken.
Jun 23, 2016 at 15:06 answer added Archemar timeline score: 1
Jun 23, 2016 at 14:14 comment added Eric Renouf I could be wrong, but I think once you're in a rescue shell you can't continue the current boot, you fix things so the next boot will succeed
Jun 23, 2016 at 14:08 history asked MathematicalOrchid CC BY-SA 3.0