BTRFS bdev /dev/nvme0n1p1 error


Go to solution Solved by JorgeB,

Recommended Posts

The problem is not the name, it's that the other device still belongs to tat filesystem:

 

Feb  7 14:00:26 ASAS emhttpd:  Total devices 3 FS bytes used 635.53GiB
Feb  7 14:00:26 ASAS emhttpd:  devid    1 size 953.87GiB used 654.06GiB path /dev/nvme1n1p1
Feb  7 14:00:26 ASAS emhttpd:  devid    4 size 953.87GiB used 24.00GiB path /dev/nvme0n1p1
Feb  7 14:00:26 ASAS emhttpd:  *** Some devices missing
Feb  7 14:00:26 ASAS emhttpd: cache: invalid config: total_devices 3 num_misplaced 1 num_missing 1

 

You need to first remove the device for the pool or wipe it, if the pool does not need it, but the pool is still reporting another missing device, so that should be fixed first.

Link to comment
  • Replies 50
  • Created
  • Last Reply

Top Posters In This Topic

3 minutes ago, JorgeB said:

The problem is not the name, it's that the other device still belongs to tat filesystem:

 

Feb  7 14:00:26 ASAS emhttpd:  Total devices 3 FS bytes used 635.53GiB
Feb  7 14:00:26 ASAS emhttpd:  devid    1 size 953.87GiB used 654.06GiB path /dev/nvme1n1p1
Feb  7 14:00:26 ASAS emhttpd:  devid    4 size 953.87GiB used 24.00GiB path /dev/nvme0n1p1
Feb  7 14:00:26 ASAS emhttpd:  *** Some devices missing
Feb  7 14:00:26 ASAS emhttpd: cache: invalid config: total_devices 3 num_misplaced 1 num_missing 1

 

You need to first remove the device for the pool or wipe it, if the pool does not need it, but the pool is still reporting another missing device, so that should be fixed first.

sorry i am a bit inexperienced with unraid, how do i do that? since i can't format the disk without the array started

Link to comment
49 minutes ago, JorgeB said:

First lets try and fix the pool, don't wipe the other device for now in case it's needed, because the pool should not work with two missing devices, disconnect that device and post new diags after array start.

in the mean time , i just got another problem. somehow my unraid wont boot at all, it just blanked screen when i chose the USB that was used for unraid. what happened was that i added another NVME to the motherboard . connected monitor on it , and only shows a "-" dash on the corner left. 

any solution?

Edited by mrpainnogain
Link to comment
5 minutes ago, JorgeB said:

Is the USB still the first boot device? You can also press the boot menu key and choose that.

i always press boot key and chose the usb manually, after that i chose which mode unraid i want to boot to. but this time after i chose the usual USB. it just black screen. i actually just did a back up before i added nvme on it, do i have to remove the nvme first? or can i just switch to other usb to boot straight away? to be more specifics i added one nvme made new pool on it, install VM on it. shutdown the system. then i added another NVME ( so total 3 NVME's) and after that it wont boot at all

Edited by mrpainnogain
Link to comment
2 hours ago, JorgeB said:

It's safe.

ok i did boot to the usb, everything went smooth on my other PC. what might be the issue here? i could see everything on the GUI and it seems like there is no problem. just that the disks are missing as expected. also posted my latest diagnostic on different PC ( just in case needed) 

 

 

asas-diagnostics-20240208-0105.zip

Edited by mrpainnogain
Link to comment
9 hours ago, mrpainnogain said:

ok cool, will try tomorrow. thanks

hi there , i have already done the CMOS reset , it was confirmed by having " bios has been reset" notification when i rebooted . but the same thing happened again , after i chose the usb. the screen stuck at black screen, i haven't even reached the blue background options yet. 

Link to comment
20 hours ago, JorgeB said:

First lets try and fix the pool, don't wipe the other device for now in case it's needed, because the pool should not work with two missing devices, disconnect that device and post new diags after array start.

okay back here. how do i resolve this issue? also attached the diag.  here's the diag with and without the new NVME attached on the system.

basically i want to use the NVME with series 2L082xx stays the same on the system as it has my current VM and others. but i want to create a new pool for the other NVME starting with series 2N462XX. 

 

 

asas-diagnostics-20240208-1333.zip

asas-diagnostics-20240208-1406.zip

Edited by mrpainnogain
Link to comment
7 hours ago, JorgeB said:
btrfs fi show

there we go , 

 

Label: none  uuid: 7f94e2af-8931-47e7-8457-d4946fa8df48
        Total devices 1 FS bytes used 597.08GiB
        devid    1 size 953.87GiB used 654.06GiB path /dev/nvme0n1p1

Label: none  uuid: ebf65eba-8218-475e-94e1-6aa9c3e2dc13
        Total devices 1 FS bytes used 5.41GiB
        devid    1 size 20.00GiB used 8.02GiB path /dev/loop2

Label: none  uuid: 3d8ee1e7-2c37-4667-9518-d41824ba9b65
        Total devices 1 FS bytes used 2.41MiB
        devid    1 size 1.00GiB used 126.38MiB path /dev/loop3

Link to comment

OK, just wanted to make sure the device is OK by itself, and it is, problem is that both NVMe devices were once part of the same pool, and if both are connected btrfs gets confused, you can reconnect the other device and wipe it, since you have UD installed suggest using it, less chance of making a mistake on which device to wipe, once it's wiped you can assign it to a new pool, start the array and format the new pool, but check that only the new pool has an unmountable device before formatting.

Link to comment
3 minutes ago, JorgeB said:

OK, just wanted to make sure the device is OK by itself, and it is, problem is that both NVMe devices were once part of the same pool, and if both are connected btrfs gets confused, you can reconnect the other device and wipe it, since you have UD installed suggest using it, less chance of making a mistake on which device to wipe, once it's wiped you can assign it to a new pool, start the array and format the new pool, but check that only the new pool has an unmountable device before formatting.

yes the device is OK by itself, as i am currently using it. 

image.thumb.png.1e9998a1d27abbc5719801a98aedcecc.png

 

you are right, the device used to be part of the same pool, but due to btrfs corruption , i took it of from the motherboard and since that, every time i connected that device, the cache pool got the " missing disk" notification. 

 

when u say wipe it, do u mean format the NVME before starting the array? 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.