Error mounting after successful burn rpi5 NVMe #168
Comments
|
"Is the device name maybe incorrect somehow? device /dev/nvme0n12" This should actually be /dev/nvme0n1p2, referring to the 2nd partition. This should be fixed in V11.2, What version of sdm are you running ( If your sdm is earlier than 11.2, please update to 11.2 (the latest) and try again. If you're already running 11.2, then let's hope the nvme adapter and device that will soon be on my workbench (coincidentally arriving this afternoon Seattle time) actually work so this can be sorted. The dmesg errors (AER and PCIe bus errors) are interesting, but I suspect that they're related to sdm not using the correct partition name. We should only worry about those once sdm can correctly and consistently burn and mount the nvme drive. |
|
I will check the version asap, but I installed it yesterday following the quick start |
|
If you installed yesterday you've got the latest. Hopefully my nvme adapter and disk arrive...and work...so I can nail whatever this is. Will update this later today. |
|
I was reviewing some code and found the problem. Will be fixed in the next release. If you want to fix it now, you can sudoedit /usr/local/sdm/sdm-cparse. Line 1401 is: Change it to be that is, change Since test done in several locations it will be centralized, but this is the only code that's broken. Pshew! |
|
Great, that did the trick! This now seems to work as expected using the flag One other thing I tried did not go as expected, but that might be me using it wrong. I tried again using parted as a burn-plugin to add a partition and resizing the root and the added one: But this ends in: Root is not expanded because parted is called and new partition not created, as expected from the specification. But am I using it wrong or could this be related? |
|
I just found and fixed a few bugs in the emerging 11.3 version, but I've never seen these errors: Only the first error is interesting, since the first error results in the 2nd error. A couple of questions so I can repro it here:
And a note for the future: The first several lines of /etc/sdm/history in the customized IMG or burned SSD/SD Card are super-helpful, especially the first lines to "Plugins selected:" for these types of issues. For plugin problems, helpful to include up to the first report of free disk space. |
|
A bit of delay because of our timezones. The host hardware is a Raspberry Pi 5 Model B Rev 1.0 (revision d04170) 8Gb with a pimoroni bottom nvme hat. The Nvme drive is a Patriot P310 240gb. It's running I am redoing a test from scratch: a customized latest version of rapberry os lite. Two tests: 1) set burn plugin at burn command and 2) set it at customization command: Test 1 And then burn with parted parameters: Which does not set partitions as I expect and the following output: Test 2: set burn plugin at customization: Gives output: The burn without any parameters linked to parted: Gives the output: |
|
I have also rerun the test to set burnplugin at customization with a fresh copy of clean raspberry os image (uncustomized, just in case). I set the burnplugin Then line 18-19-20 is: Trying that referenced file So they are present in the image. But somehow code doesn't find it? I don't know how to debug this so not sure how for example Hope this and previous helps? |
|
Thanks for the detailed details 😂 I've got enough info to nail it now. |
|
Haha yeah I figured you know better than me what to filter out |
|
Just did a test with 11.2 (which you're using). Wasn't able to replicate the problem with "/etc/sdm/sdm-readparams: No such file or directory", but did run into another issue I fixed yesterday. Reran the same test with 11.3 and all good. Now I just need to finish up 11.3 for you 🥴Still chasing a couple of other features/bugs, but should have it done in the next day or two, worst case. |
|
Too bad that it doesn't reproduce, but fortunately I can work around it. I burned the image without the Could it be due to us using different brand NVMe hats? Also tried setting/unsetting Nonetheless, I am grateful for such a great tool being here in the first place. |
|
I believe these are all fixed in 11.3, per testing on my NVME drive. Please test with your configuration. Thx! |
|
I just tested on a new Rpi5 4Gb, now with a kingston NV2 1TB drive and another pimoroni base hat using SDM 11.3 and still have the issue: But it is another issue than the one I started with, so I could close this one because now that does work. As I'm still with the pimoroni, maybe that has something to do with it? |
|
I'm not worried about whether it's this issue or another issue. This one is open, so let's just continue here. I need to see the /etc/sdm/history file from in the IMG that you're burning. You can either post it here or email it to me (email on https://github.com/gitbls/sdm/README.md). My suspicion is that there's something in the way your IMG has been customized, but in addition to the history file, please also shoot me the commands you're using to customize and burn. Please feel free to redact passwords as necessary, but leave everything else intact. Thx! |
|
Ah! Never mind...I was in my best thinking place (shower 😂) and realized exactly what the problem is. 🥴 |
|
On host systems running sdm where sdm was NOT used to burn the host system disk, there is an error in the installer. This will be corrected shortly in the default download. The issue is that the installer doesn't do these steps, which burn-plugins rely on. You can correct your system so that the parted plugin works with the following. It assumes that you put sdm in the default location (/usr/local/sdm). If you've changed that, modify these commands appropriately: Please LMK if this fixes it. Apologies for the delay in nailing this for you 😳 |
|
The first two lines ok. But then I'm unfamiliar with the syntax. I execute it line by line and there is an error |
Sorry, was apparently in too much of a hurry. Try this. After you type the cat command, you should be prompted with |
|
Still get permission denied: So I outputted the file first to home dir and then copied it to And success! 😎 Nice Not sure why cat has no permissions while using sudo? But anyway now it is all working as expected. Any suggestion how I can set another partition on that disk using the burn plugin that expands to fill the whole free space? It's not fully clear from the docs to me, only how to expand root. I have about 630GB left that I want to configure to the last byte, but would like to be able to do it without calculating all clusters or guessing etc. --edit: (re-reading the docs) --edit2: So I haven't figured it out yet. |
Glad that you got the cparams file created. Not sure what's going on there. Re creating a "last partition" that fills the disk: There's no way to do that at the moment, but there should be. I've got the parted plugin open to add GPT disk support, so will look into adding this "makes perfect sense" feature. |
|
Confirmed. Adding a last partition with a size of 0 will fill the whole free space in the next release. Of course, if there's another partition specified after a 0-length partition, it will fail miserably, since there will be no room for it. |
|
Hi, me again. xD It was good I read this because I was thinking of forking and sending 1 or 2 requests. I also saw you are doing some unnecessary operations that I could help out with if you'd like. (partition resizing and stuff) But you should def make the changes you have in mind first because I might need to move a few things around to do what I have in mind. |
Please don't hijack other threads...please start a new Issue (or Discussion if you'd prefer) where we can chat about this. I'm interested in your code to understand the code complexity, tradeoffs, possible issues, etc. as well as proven performance data. I'd much prefer a script that I can download/use on the side than something you've integrated into sdm. Thx. |
This is fixed in the just-released V11.4. Please test. Thx! |
|
Ok interesting, I tried installing latest version using Resulted in this: Note the line --edit: using |
Pretty sure I understand what's happening, but what is the host OS and version that you're installing on? |
|
Hardware is Raspberry Pi 5 Model B Rev 1.0 (4GB) |
|
OK, thx. Please download the latest EZsdmInstaller and rerun it. It will properly create cparse, and I'm off to read about "here documents" and sudo 😕 |
|
ok that went well now, great! Will now try the image burning again |
|
ok that's looking good, great work! |
|
Excellent! And...apologies for the duffs/hassles along the way, and thank you for sticking with me on getting this working for you. |
Disclaimer: I am not an expert at linux, but I think this might be interesting to let you know.
I am using an RPi 5 with a Pimoroni NVMe bottom HAT and a Patriot P310 240Gb NVMe SSD. The burn seems to be almost successful. After burning there is an error mounting the image, if I understand correctly. The (headless) pi CAN now boot from the NVMe drive and the requested user is created with the set password and I can login via the enabled SSH. However, the hostname is not set to what I specified and still at raspberrypi.
Here's what I did:
I customised an image with some basic settings (appears successful to me, have output if needed):
$ sudo sdm --customize --plugin user:"adduser=me|prompt" --plugin L10n:host --plugin disables:piwiz --regen-ssh-host-keys --restart 2023-12-11-bookworm-arm64-lite-my-custom-image.imgThen burned the image:
$ sudo sdm --burn /dev/nvme0n1 --hostname pi --expand-root --regen-ssh-host-keys 2023-12-11-bookworm-arm64-lite-my-custom-image.imgThe following output showed:
I check the devices:
dmesg output shown below due to length.
Is the device name maybe incorrect somehow?
device /dev/nvme0n12dmesg output (last parts only):
The text was updated successfully, but these errors were encountered: