-
Notifications
You must be signed in to change notification settings - Fork 34
failed to update - No space left on device #255
Description
5 min old fresh install of Clear Linux 37860...trying to update now
/etc/kernel/cmdline.d/mitigations.conf >>
mitigations=off
sudo clr-boot-manager update
[ERROR] cbm (../src/lib/bootvar.c:L372): efi_set_variable() failed: No space left on device
[ERROR] cbm (../src/bootloaders/shim-systemd.c:L284): Cannot create EFI variable (boot entry)
[ERROR] cbm (../src/bootloaders/shim-systemd.c:L285): Please manually update your bios to add a boot entry for Clear Linux
Expected behavior
no errors as before
Environment (please complete the following information):
- Clear Linux OS Version: 37930
- clr-boot-manager Version: 3.2.12
- Platform: Ryzen 9 5950X, ASUS ProArt B550-Creator, Ripjaw 128GB, nVidia Quadro 600 (non EFI, might be problem), Samsung 256GB NVMe
** Block Devices:**
- List of Block Devices:
{
"blockdevices": [
{
"name": "loop0",
"maj:min": "7:0",
"rm": false,
"size": "0B",
"ro": false,
"type": "loop",
"mountpoints": [
null
]
},{
"name": "loop1",
"maj:min": "7:1",
"rm": false,
"size": "0B",
"ro": false,
"type": "loop",
"mountpoints": [
null
]
},{
"name": "loop2",
"maj:min": "7:2",
"rm": false,
"size": "0B",
"ro": false,
"type": "loop",
"mountpoints": [
null
]
},{
"name": "loop3",
"maj:min": "7:3",
"rm": false,
"size": "0B",
"ro": false,
"type": "loop",
"mountpoints": [
null
]
},{
"name": "loop4",
"maj:min": "7:4",
"rm": false,
"size": "0B",
"ro": false,
"type": "loop",
"mountpoints": [
null
]
},{
"name": "loop5",
"maj:min": "7:5",
"rm": false,
"size": "0B",
"ro": false,
"type": "loop",
"mountpoints": [
null
]
},{
"name": "loop6",
"maj:min": "7:6",
"rm": false,
"size": "0B",
"ro": false,
"type": "loop",
"mountpoints": [
null
]
},{
"name": "loop7",
"maj:min": "7:7",
"rm": false,
"size": "0B",
"ro": false,
"type": "loop",
"mountpoints": [
null
]
},{
"name": "nvme0n1",
"maj:min": "259:0",
"rm": false,
"size": "1.8T",
"ro": false,
"type": "disk",
"mountpoints": [
null
],
"children": [
{
"name": "nvme0n1p1",
"maj:min": "259:1",
"rm": false,
"size": "1.8T",
"ro": false,
"type": "part",
"mountpoints": [
"/c-tmp"
]
}
]
},{
"name": "nvme1n1",
"maj:min": "259:2",
"rm": false,
"size": "238.5G",
"ro": false,
"type": "disk",
"mountpoints": [
null
],
"children": [
{
"name": "nvme1n1p1",
"maj:min": "259:3",
"rm": false,
"size": "512M",
"ro": false,
"type": "part",
"mountpoints": [
null
]
},{
"name": "nvme1n1p2",
"maj:min": "259:4",
"rm": false,
"size": "7.3G",
"ro": false,
"type": "part",
"mountpoints": [
"[SWAP]"
]
},{
"name": "nvme1n1p3",
"maj:min": "259:5",
"rm": false,
"size": "230.6G",
"ro": false,
"type": "part",
"mountpoints": [
"/"
]
}
]
}
]
}
Additional context
After update & reboot...still same error, but additional kernel parameters are loaded...I guess it works, just with error.