NixOS: recover /boot mount info after overwriting hardware-configuration.nix
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
In my NixOS configuration I ended up accidentally overwriting my hardware-configuration.nix. While sudo nixos-generate-config regenerates one, for me the regenerated version appears to be missing the required /boot section.
How can I figure out what this section was / should have been like?
I checked e.g. /nix/var/nix/profiles/, but couldn't find it in there.lsblk shows me some partitions including a sr0 that seems like what should be my /boot:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 923.5G 0 part /tmp/c7ca628b-0645-4af0-95d5-741d47d5923f
└─sda2 8:2 0 8G 0 part [SWAP]
sdb 8:16 0 119.2G 0 disk
└─sdb1 8:17 0 119.2G 0 part
sr0 11:0 1 1024M 0 rom
... however, trying to plug this in did not seem to work.
nixos
asked Mar 8 at 16:20
TychoTycho
1033
add a comment |
In my NixOS configuration I ended up accidentally overwriting my hardware-configuration.nix. While sudo nixos-generate-config regenerates one, for me the regenerated version appears to be missing the required /boot section.
How can I figure out what this section was / should have been like?
I checked e.g. /nix/var/nix/profiles/, but couldn't find it in there.lsblk shows me some partitions including a sr0 that seems like what should be my /boot:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 923.5G 0 part /tmp/c7ca628b-0645-4af0-95d5-741d47d5923f
└─sda2 8:2 0 8G 0 part [SWAP]
sdb 8:16 0 119.2G 0 disk
└─sdb1 8:17 0 119.2G 0 part
sr0 11:0 1 1024M 0 rom
... however, trying to plug this in did not seem to work.
nixos
asked Mar 8 at 16:20
TychoTycho
1033
add a comment |
In my NixOS configuration I ended up accidentally overwriting my hardware-configuration.nix. While sudo nixos-generate-config regenerates one, for me the regenerated version appears to be missing the required /boot section.
How can I figure out what this section was / should have been like?
I checked e.g. /nix/var/nix/profiles/, but couldn't find it in there.lsblk shows me some partitions including a sr0 that seems like what should be my /boot:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 923.5G 0 part /tmp/c7ca628b-0645-4af0-95d5-741d47d5923f
└─sda2 8:2 0 8G 0 part [SWAP]
sdb 8:16 0 119.2G 0 disk
└─sdb1 8:17 0 119.2G 0 part
sr0 11:0 1 1024M 0 rom
... however, trying to plug this in did not seem to work.
nixos
asked Mar 8 at 16:20
TychoTycho
1033
In my NixOS configuration I ended up accidentally overwriting my hardware-configuration.nix. While sudo nixos-generate-config regenerates one, for me the regenerated version appears to be missing the required /boot section.
How can I figure out what this section was / should have been like?
I checked e.g. /nix/var/nix/profiles/, but couldn't find it in there.lsblk shows me some partitions including a sr0 that seems like what should be my /boot:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 923.5G 0 part /tmp/c7ca628b-0645-4af0-95d5-741d47d5923f
└─sda2 8:2 0 8G 0 part [SWAP]
sdb 8:16 0 119.2G 0 disk
└─sdb1 8:17 0 119.2G 0 part
sr0 11:0 1 1024M 0 rom
... however, trying to plug this in did not seem to work.
nixos
nixos
asked Mar 8 at 16:20
TychoTycho
1033
asked Mar 8 at 16:20
TychoTycho
1033
asked Mar 8 at 16:20
TychoTycho
1033
asked Mar 8 at 16:20
TychoTycho
1033
asked Mar 8 at 16:20
TychoTycho
1033
1033
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
IIRC nixos-generate-config generates mounts simply based on what is currently mounted. So... one option is to mount stuff by hand the way you want it and then run the generator. I guess if you have previous system generations that work the way you want, you can boot into one of them via the grub menu and run nixos-generate-config from them.
answered Mar 8 at 20:06
Vladimír ČunátVladimír Čunát
78137
Thanks for your response. I tried this, but the/bootisn't in the generated file, giving me a bit of a chicken-and-egg problem: getting it into a generated config implies having it mounted, while mounting it implies knowing what to mount (and how). e.g. tryingsudo mount /dev/sr0 /tmp/sr0gives memount: /tmp/sr0: no medium found on /dev/sr0.
– Tycho
Mar 9 at 9:26
I assumed that you do have an older system generation in grub that does know how to mount it.
– Vladimír Čunát
Mar 10 at 10:02
I imagine it 'knew' in the sense it managed to boot... but I ended up just formatting instead now. Thanks for your help!
– Tycho
Mar 11 at 10:17
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505161%2fnixos-recover-boot-mount-info-after-overwriting-hardware-configuration-nix%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
IIRC nixos-generate-config generates mounts simply based on what is currently mounted. So... one option is to mount stuff by hand the way you want it and then run the generator. I guess if you have previous system generations that work the way you want, you can boot into one of them via the grub menu and run nixos-generate-config from them.
answered Mar 8 at 20:06
Vladimír ČunátVladimír Čunát
78137
Thanks for your response. I tried this, but the/bootisn't in the generated file, giving me a bit of a chicken-and-egg problem: getting it into a generated config implies having it mounted, while mounting it implies knowing what to mount (and how). e.g. tryingsudo mount /dev/sr0 /tmp/sr0gives memount: /tmp/sr0: no medium found on /dev/sr0.
– Tycho
Mar 9 at 9:26
I assumed that you do have an older system generation in grub that does know how to mount it.
– Vladimír Čunát
Mar 10 at 10:02
I imagine it 'knew' in the sense it managed to boot... but I ended up just formatting instead now. Thanks for your help!
– Tycho
Mar 11 at 10:17
add a comment |
IIRC nixos-generate-config generates mounts simply based on what is currently mounted. So... one option is to mount stuff by hand the way you want it and then run the generator. I guess if you have previous system generations that work the way you want, you can boot into one of them via the grub menu and run nixos-generate-config from them.
answered Mar 8 at 20:06
Vladimír ČunátVladimír Čunát
78137
Thanks for your response. I tried this, but the/bootisn't in the generated file, giving me a bit of a chicken-and-egg problem: getting it into a generated config implies having it mounted, while mounting it implies knowing what to mount (and how). e.g. tryingsudo mount /dev/sr0 /tmp/sr0gives memount: /tmp/sr0: no medium found on /dev/sr0.
– Tycho
Mar 9 at 9:26
I assumed that you do have an older system generation in grub that does know how to mount it.
– Vladimír Čunát
Mar 10 at 10:02
I imagine it 'knew' in the sense it managed to boot... but I ended up just formatting instead now. Thanks for your help!
– Tycho
Mar 11 at 10:17
add a comment |
IIRC nixos-generate-config generates mounts simply based on what is currently mounted. So... one option is to mount stuff by hand the way you want it and then run the generator. I guess if you have previous system generations that work the way you want, you can boot into one of them via the grub menu and run nixos-generate-config from them.
answered Mar 8 at 20:06
Vladimír ČunátVladimír Čunát
78137
IIRC nixos-generate-config generates mounts simply based on what is currently mounted. So... one option is to mount stuff by hand the way you want it and then run the generator. I guess if you have previous system generations that work the way you want, you can boot into one of them via the grub menu and run nixos-generate-config from them.
answered Mar 8 at 20:06
Vladimír ČunátVladimír Čunát
78137
answered Mar 8 at 20:06
Vladimír ČunátVladimír Čunát
78137
answered Mar 8 at 20:06
Vladimír ČunátVladimír Čunát
78137
answered Mar 8 at 20:06
Vladimír ČunátVladimír Čunát
78137
78137
Thanks for your response. I tried this, but the/bootisn't in the generated file, giving me a bit of a chicken-and-egg problem: getting it into a generated config implies having it mounted, while mounting it implies knowing what to mount (and how). e.g. tryingsudo mount /dev/sr0 /tmp/sr0gives memount: /tmp/sr0: no medium found on /dev/sr0.
– Tycho
Mar 9 at 9:26
I assumed that you do have an older system generation in grub that does know how to mount it.
– Vladimír Čunát
Mar 10 at 10:02
I imagine it 'knew' in the sense it managed to boot... but I ended up just formatting instead now. Thanks for your help!
– Tycho
Mar 11 at 10:17
add a comment |
Thanks for your response. I tried this, but the/bootisn't in the generated file, giving me a bit of a chicken-and-egg problem: getting it into a generated config implies having it mounted, while mounting it implies knowing what to mount (and how). e.g. tryingsudo mount /dev/sr0 /tmp/sr0gives memount: /tmp/sr0: no medium found on /dev/sr0.
– Tycho
Mar 9 at 9:26
I assumed that you do have an older system generation in grub that does know how to mount it.
– Vladimír Čunát
Mar 10 at 10:02
I imagine it 'knew' in the sense it managed to boot... but I ended up just formatting instead now. Thanks for your help!
– Tycho
Mar 11 at 10:17
Thanks for your response. I tried this, but the
/boot isn't in the generated file, giving me a bit of a chicken-and-egg problem: getting it into a generated config implies having it mounted, while mounting it implies knowing what to mount (and how). e.g. trying sudo mount /dev/sr0 /tmp/sr0 gives me mount: /tmp/sr0: no medium found on /dev/sr0.– Tycho
Mar 9 at 9:26
Thanks for your response. I tried this, but the
/boot isn't in the generated file, giving me a bit of a chicken-and-egg problem: getting it into a generated config implies having it mounted, while mounting it implies knowing what to mount (and how). e.g. trying sudo mount /dev/sr0 /tmp/sr0 gives me mount: /tmp/sr0: no medium found on /dev/sr0.– Tycho
Mar 9 at 9:26
I assumed that you do have an older system generation in grub that does know how to mount it.
– Vladimír Čunát
Mar 10 at 10:02
I assumed that you do have an older system generation in grub that does know how to mount it.
– Vladimír Čunát
Mar 10 at 10:02
I imagine it 'knew' in the sense it managed to boot... but I ended up just formatting instead now. Thanks for your help!
– Tycho
Mar 11 at 10:17
I imagine it 'knew' in the sense it managed to boot... but I ended up just formatting instead now. Thanks for your help!
– Tycho
Mar 11 at 10:17
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505161%2fnixos-recover-boot-mount-info-after-overwriting-hardware-configuration-nix%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
