mrpainnogain

instead writing the whole thing, i just add pcie_aspm=off on the config. it's been going fine for the past 2hrs ++ . i will report if there is another error. in the mean time , can you please check on my new diagnostic, i got one NVME with series 2N462LQ5CSYH that always go offline after several minutes/hours connected to the system. do you happen to know why? asas-diagnostics-20240216-1638.zip

may i know which power management option? because i think i am experiencing similar issues.

okay , after running for approximately 1 hr. it happens again . exactly the same thing also the NVME can not be accessed any more as well. also i posteed asas-diagnostics-20240216-1334.zip

i have been experiencing I/O device error with different NVME and also different nvme slot on the motherboard. suddenly after running for more than 5 days, one of my NVME got that warning and can not be accessed anymore. and i had to restart the unraid, luckily the problem did not occur back until now. i initially thought the issue only happened on BTRFS file system, but 2 my NVME got the same warning even on the XFS filesystem. what might be the issue here? is it bad motherboard? i have 3 NVME on the mobo, only one that seems to never have any problem. asas-diagnostics-20240216-1159.zip

i did that but i did not solve it, the detected space only 20 GB. i have already restarted the docker as well

my previous scrypted docker somehow got corrupted and so i created the new one. i made a path to the footage folder which located on /mnt/user/SCRYPTED/footage, that share is specifically only on disk 4 which is a 1 TB HDD. but it is only detecting 20 GB on my scrypted docker and also i could not find the previous footage. am i making the wrong path for the footage ? i actually just copy on exactly the same what the previous docker had. asas-diagnostics-20240212-0319.zip

hi guys just this morning i got log which tells that one of my NVME that contains the appdata is somehow corrupted. i managed to move the shares to the nvme where the data was originally stored, but instead the docker started fresh. i did not change anything on the docker container or host path. am i missing something here? or somehow the files got overwritten ? To be more specific, couple days ago the appdata share was on "cache" pool then i changed the share path to " app_data" pool. but then the app_data pool got corrupted. then i change the share of the appdata back to the cache. asas-diagnostics-20240211-1131.zip

thanks a lot your solution worked!

yes the device is OK by itself, as i am currently using it. 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?

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

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

okay , finally it worked again now. all i had to do was updated the BIOS my mobo is z590 vision g and the version was F2 and now it became F8. i can boot again to unraid. it is weird though, i didn't do any softwares update. all i did was just added another NVME

it just stuck like this IMG_8091.MOV IMG_8091.MOV IMG_8092.HEIC

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.

ok cool, will try tomorrow. thanks