comet424

i got some help to boot into "maintance mode" but they asked me to scrub drive but since it wont mount it wont let me scrub. but there was a btrfs check i ran it and the log it gave is parent transid verify failed on 1543279591424 wanted 136563 found 130890 parent transid verify failed on 1543279591424 wanted 136563 found 130890 parent transid verify failed on 1543279591424 wanted 136563 found 130890 Ignoring transid failure ERROR: root [1 0] level 1 does not match 0 Couldn't read tree root ERROR: cannot open file system Opening filesystem to check...

hi i had btrfs file system not work again.. its been 2 yrs since i last posted but my download drive i use a spinner as a cache pool to download and uses btrfs... i was trying to move files off it.. and it was failing.. i rebooted and its unmounted... here is the logs Jul 2 12:18:42 mitchsserver kernel: ACPI: Early table checksum verification disabled Jul 2 12:18:42 mitchsserver kernel: floppy0: no floppy controllers found Jul 2 12:18:42 mitchsserver kernel: ata5.00: exception Emask 0x50 SAct 0x1000000 SErr 0x30802 action 0xe frozen Jul 2 12:18:42 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED Jul 2 12:18:42 mitchsserver kernel: ata5: hard resetting link Jul 2 12:18:42 mitchsserver kernel: ata5: hard resetting link Jul 2 12:18:42 mitchsserver kernel: blk_update_request: I/O error, dev sdd, sector 4160 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Jul 2 12:18:43 mitchsserver mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Jul 2 12:19:15 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:19:15 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:19:15 mitchsserver kernel: BTRFS warning (device sde1): couldn't read tree root Jul 2 12:19:15 mitchsserver kernel: BTRFS error (device sde1): open_ctree failed Jul 2 12:19:15 mitchsserver root: mount: /mnt/download_drive: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error. Jul 2 12:19:15 mitchsserver emhttpd: /mnt/download_drive mount error: No file system Jul 2 12:19:26 mitchsserver rc.docker: transmission: Error response from daemon: error while creating mount source path '/mnt/user/Transmission/completed': mkdir /mnt/user/Transmission: no medium found Jul 2 12:19:26 mitchsserver rc.docker: Error: failed to start containers: transmission Jul 2 12:29:03 mitchsserver root: Fix Common Problems: Warning: unRaids built in FTP server is currently disabled, but users are defined Jul 2 12:36:19 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:36:19 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:36:19 mitchsserver kernel: BTRFS warning (device sde1): couldn't read tree root Jul 2 12:36:19 mitchsserver kernel: BTRFS error (device sde1): open_ctree failed Jul 2 12:36:43 mitchsserver kernel: BTRFS warning (device sde1): 'usebackuproot' is deprecated, use 'rescue=usebackuproot' instead Jul 2 12:36:43 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:36:43 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:36:43 mitchsserver kernel: BTRFS warning (device sde1): couldn't read tree root Jul 2 12:36:43 mitchsserver kernel: BTRFS error (device sde1): chunk 1664330235904 has missing dev extent, have 0 expect 1 Jul 2 12:36:43 mitchsserver kernel: BTRFS error (device sde1): failed to verify dev extents against chunks: -117 Jul 2 12:36:43 mitchsserver kernel: BTRFS error (device sde1): open_ctree failed Jul 2 12:37:09 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:37:09 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:37:09 mitchsserver kernel: BTRFS warning (device sde1): couldn't read tree root Jul 2 12:37:09 mitchsserver kernel: BTRFS error (device sde1): open_ctree failed Jul 2 12:39:09 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:39:09 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:39:09 mitchsserver kernel: BTRFS warning (device sde1): couldn't read tree root Jul 2 12:39:09 mitchsserver kernel: BTRFS error (device sde1): open_ctree failed Jul 2 12:42:38 mitchsserver kernel: sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Jul 2 12:42:38 mitchsserver kernel: sd 1:0:0:0: [sdb] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Jul 2 12:46:37 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:46:37 mitchsserver kernel: BTRFS error (device sde1): parent transid verify failed on 1543279591424 wanted 136563 found 130890 Jul 2 12:46:37 mitchsserver kernel: BTRFS warning (device sde1): couldn't read tree root Jul 2 12:46:37 mitchsserver kernel: BTRFS error (device sde1): open_ctree failed i tried these commands as the link i got provided in here was upadated for 6.10 but i get these other errors it wont work now root@mitchsserver:~# btrfs fi show /dev/sde1 Label: none uuid: 547e712d-e478-48a9-a84a-30ed71534b0d Total devices 1 FS bytes used 530.19GiB devid 1 size 931.51GiB used 572.02GiB path /dev/sde1 root@mitchsserver:~# mkdir /temp root@mitchsserver:~# mount -o rescue=all,ro /dev/sde1 /temp mount: /temp: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error. root@mitchsserver:~# mount -o usebackuproot,ro /dev/sde1 /temp mount: /temp: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error. root@mitchsserver:~# mount -o degraded,rescue=all,ro /dev/sde1 /temp mount: /temp: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error. root@mitchsserver:~# ls /dev/sde1 /dev/sde1 so not sure how do i get it back... not sure whats going on or why this stuff happens/ better to have ntfs cache pool maybe? should i be using like an ssd instead of a spinner to download? as i use it to keep array offline or should i use 2 disks for cache pool for downloads? or error happen on both? i do the same setup on a few unraids 1 drive to dump any downloads from server windows etc.. but i use a spinner and 1 drive so not sure what the best is to do it mitchsserver-diagnostics-20220702-1255.zip

how do i write an if statement to check if a drive is existant or not.. i use a scrip to copy music to a hard drive.. but if the hard drive isnt plugged in i get the error.. but i guess it makes a directory in the unnassigned drives.. as Krusader sees the Drives even though they dont exists.. i guess makes a temp folder or so so unraid thinks the drive is there and it isnt.. so id like a IF statement if Drive is there copy files if not exit if

@itimpi so would mover be consider something you wouldnt bother using then if ur moving the files of appdata system docker vms from the cache to the array and then back again if it does alot of checks when would you use it? i never really had money for a cache drive to copy files from network to a cache drive and then over night copies to the array.. does mover work faster for regular files.. and really slow for appdata like plex being huge... or is it equally slow? ill take a look about the dynamic file manager.. but dont you need the "checks" for appdata docker system... or when do you need "checks" and when dont you need "checks" and id even like to see so SSD to SSD say your SSD is named "unraid_files" and everything is linked to that pool name when you add a new ssd.. it be nice to have the option of 1. install New SSD 2. App that Will Transfer the "unraid_files" pool to the new SSD (either move or copy, give the option) 3. App would re label the old broken(or upgrade) SSD if can to "old_unraid_files" 3. App would re label the "new SSD" to "unraid_files" 4. boom your done and your back in business and you dont need to worry about linking to a different pool if you happen to have scripts or what not that points to the old pool name.. or having to delete old pool name then label the new pool the same pool you had. this way you could do it in 1 app and it be all automated.. like mover u press the move button and u wait till its done. its a thought... but ill take a look at that dynamic file manager.. but maybe the developers could look at the option of transfer from old ssd to a new ssd and keep the same pool name.. but skip the "check" or whatever its really doing that makes it godly slow.. and nothing against the program.. as i probbably dont utlize unraid to its full potenial .. but love the program so just a thought

hi i like to see a request... that when you wanna move from a bad SSD or Upgrade etc.. instead of "JUST" going to the array.. have the option to move files the appdata system docker folders from 1 cache drive to a 2nd one.. this way you wouldnt need to move it twice from ssd to array and then from array back to new ssd have it from old ssd to new ssd... in 1 Step not 2 steps.. as it takes hours and hours for mover to Move files... so if you can Move from 1 cache to a 2nd cache skipping the "Array" youd save soo much time.. and maybe just maybe mover would move faster since your going SSD to SSD instead of SSD to SPINNERS then SPINNERs to NEW SSD as it looks like it takes a 1 Day to move from SSD to Array.. and then it will be 1 day to go from ARRAY to SSD... so thats 2 days to move like 300gb .. to move 300gb from SSD to SSD can be just 1 day then and or be able to improve Mover it seems its going to take 2 Days to move 300 gig to the array .. if its possible to improve the speed of mover

so i contacted unraid developers.. and they say the "hwmonX" is a Kernel issue and they dont write the kernel maybe the developer of the AutoFan could make it 1.. use Hard Drive Serial Numbers not SDx DevX numbering 2.. since the HwmonX constantly changes so makes plugin useless if you change hard drives and seems to be Hwmon0 Hwmon1 Hwmon2 maybe a 3 for each fan.. Save Fan 1 hwmon0 hwmon1 hwmon2 with the exact same settings.. this way when Hwmon0 changes to Hwmon2 it wont bugger up... this way it be a work around instead of constantly re scanning the for the hwmon change

and when i remove the UD drive how does the monitoring work? cuz then it goes from hwmon0 and goes to hwmon2 does the reverse above. after a reboot cuz the smart monitoring doesnt apply when the drive isnt pluged in anymore? or does it?

oh your talking about the "Device name" dev1 dev2 not look for the word "device designation" way you wrote it.. i been looking for the word "device designation" and then i check off a box so id enable device designation over what its doing now dev1 2 23 or sda sdb sdc either way didnt work still changes before i add the hard drive /sys/devices/platform/nct6775.656/hwmon/hwmon2/fan1_input its set to hwmon2 when i add the hard drive and do a reboot /sys/devices/platform/nct6775.656/hwmon/hwmon0/fan1_input its now hwmon0 what i want is everytime unraid reboots you force "hwmon" to say be hwmon0 no matter what you do as many ud or array or cache drives you add

ok you lost me under smart there is no "device designation" cuz you said "a change to the SMART settings and then click 'Apply'. This will set up disk monitoring by serial number and not devX." i dont see "device designation" to click under smart to hit apply .. and disk monitoring will change dev2 to like serial number reason i asked if i just change "disk name" from "dev2 " to the "wdc-xxxxxx"(serial number) that you have cuz under the smart settings you see there is nothing that says "device designation" for me to change to serial number and not DevX and none of the 3 "defaults" have an option of "device desgination" under drop downs so i cant selection this device designation option so i kinda lost

@dlandon i dont seem to have device designation... could you send some pics? i was wondering there is for "disk name" from dev1 2 3 4 it has for my un assigned drives if i change the disk name from dev1 to the serial number of the drive? i click also the DEV1 for the 1 usb drive and looked at all the sub headings but nothing to change smart settings for device designation.. maybe you could send a few screen shots, would help

@spl147 ill have to try that set to 100% i cant remember what i have i know i think its in manual mode.. except cpu fan i leave that on automatic.. ya the autofan issue i have had issue for couple years.. where i mentioned if you add or remove a hard drive or cache drive as i guess the sdX keeps changing and bumps things so if it were to use UID then each drive would still have UID and the sdX can change as much as it wants it would still stick to the UID or even if you had to swap a drive that say Disk 1 needed replacing that auto fan plugin would also update to that new hard drive like when you do a pull drive and put a new one in and rebuild.. cuz it messes up .. and the HwmonX keeps changing i asked in general chat.. if there is a "Force" so you could force hwmon be either 0 1 or 2.. since it changes after a reboot if you change a drive either by adding it to array or to the un assigned devices.. i was hoping there was likea boot.ini and youd say force hwmon#=hwmon0 or force hwmon%=0 then at bootup the sensor hwmon be the same everytime no matter howd drive changes but i do appreciate to the programmer that wrote it.. as it keeps it quiet.. so some ideas and issues maybe he can work on would help but always appreciate it.. saves wear and tear on the fans 🙂

ah ok i dont have the drives plugged in at moment so say hwmon0 is set in the sensors or whatever and i have the 2 UD hard drives plugged in.. and when i unmount and remove the drives and then happen to reboot hwmon0 now changes to hwmon1 or hwmon2 and thats when fans all run at 100% but usually then when you plug the 2 UD drives back in and then do another reboot hwmon1 or hwmon2 will change back to hwmon0 and the fans ramp back down to silent..

is there a file in the boot folder i can set so say hwmon0 is always set to 0 and not change to hwmon1 or hwmon2 if you pull out or add a new hard drive and happen to reboot.. and then the hwmon keeps randomly changing betweeen 0 and 2 is there like a boot.ini and you do the "force hwmon#=hwmon0" something like that?

@mmwilson0 try in your bios and if it has like settings for manual and automatic fan controls try the opposite is set for.. i know i had to do that for my asus x570 boards i think i have manual i know the HWMON keeps changing if i pull or add an un assigned drive it start of as hwmon1 but after a reboot it could be hwmon0 or 2 so far no one has an answer to my question how to force it to be 1 not toggle itself so i always have to click the DETECT and then apply... cuz of the hwmon change each time you reboot if you add remove a unassigned drive

and about the UD and identifliers.. what i mean is if i have what you see in above pic... if i have 2 USB drives plugged in.. and reboot.. it will then uncheck those check boxes.. same if i add a drive to the array but also mostly the Hardware monitor keeps changing when you remove a UD from the system.. so if you have 2 UD drives pluged in and HWMON2 is set.. when you pull the 2 drives out and reboot.. HWMON2 changes to HWMON0 and buggers up the fans... and or sometimes the disk1 etc wil sometimes uncheck and re check others.. and say if i add another Disk to the array.. so Disk8 it buggers up the fans checked off cuz its not doing UID but the SD and the orders change,, so each time you add an Disk either a cache or a Disk will missup what you have already set

under fan exclude you see its sdk sdj sdl well they always change if i were to add a drive to the array... and if you add a UD drive and reboot well exclude the check marks are off by 1 or 2 or 3 depending how many UD drives you add and do a reboot for whatever reason.. so if i have array 1 to 7 checked off and you add 2 UD drives and you reboot things.. then array 1 is checked 2 3 is unchecked 4 5 6 7 could be checked off.. it picks and chooses what i mean about uid beside Disk 1 instead of it looking for SDJ it be nice if it was UID cuz so Disk 1 (sdj) would be Disk 1 (UID #) this way fans wouldnt bugger up every time a any hard drive you plug into the server and then you happen to do a reboot causes the fan list bugger up... so like excude Disk 1 UID# Disk 2 UID# Disk 3 UID# this way it be always linked to the UID number not a SDx number as i guess the Fan Speed Exclude only looks at "SDx" not "UID" and is there a way to fix that HwmonX issue i notice too?

a feature request id like to see is.. not to use "SDx" to define hard drives.. but use there UID numbers.. if you pull a UD drive.. and reboot unraid. then the SDx get all jumbled at times in the exclude drives so a drive you wanted excluded is now moved a hard drive or 2... be nice to have (array 1 drive) uid # not (array 1 drive) sda as tomorrow sda could be array 2 drive but if it could go to each unique id of a hard drive... then it wouldnt bugger up... same with the "hwmonX" it changes if you pull a UD drive out and you reboot.. now a hwmon1 is either hwmon0 or hwmon2 be nice if there was a way to fix it.. that it never changes

@mmwilson0 probably the HwmonX has changed.. re detect.. and see if its changed from hwmon0 to like 1 or 2 for each of the 6 pwms that normally fixes it for mel

ah well maybe there is a way like retropie you edit the one text file so its the same at each reboot... maybe unraid can have a way to set it so it doesnt change cuz its frustrating... but nothing is perfect

hi i was wondering if there is a way to hardcode Hardware monitor.. like you do for a Retropie at bootup you set in a textfile your usb drive to like sda1 if i start with hwmon0 and if i pull out a unassigned drive... and reboot the hardwre monitor will change from hwmon0 to like hwmon1 or hwmon2 and it will also bugger up the exclude drives in the dynamix fans plugin.. is there a way to force at bootup that hwmon0 is for Fans and it never changes no matter how many drives you add to array or UD or when you pull a drive and reboot as i know for the plugin it screws up when you add a drive to the array... the check boxes are all over the place its like it doesnt know what each drive is.. same with the sdaX it changes i guess thats why sometimes the fan speed exclude drives keeps changing... cuz they point to "sdax" and not to the actual Hard drive UID but the main issue is if you can force it... to stay at Hwmon0 cuz if i pull the drive and reboot... then the fans are running full speed.. and now on the fan plugin i gotta do a "Detect" to find which HwmonX its on now 0 1 2 and then re save each one... is there anything i can change in the "GO" file ?

the hwmon is the hardware monitor from the unraid sensors i guess like sda1 sda2 etc but the sensors for your temperatures and fan speeds i guess i can ask in general.. cuz it always changes when i change the ud drives in all versions its like each boot up the like sda1 or what not change its never the same

is there a setting in unassigned devices.. that keeps changing hwmonX i start off with hwmon0 for fans... if i add drives... and reboot unraid then hwmon changes to 1 or 2 and buggers upexclude drives check marks i thought in 6.10 unraid was able to do better at hard drive labeling or is it just the plugin.. or is there something else cuz if i put the ud drives back and reboot and the hwmon goes back to 0 and the fans are fine... is there anything i can do? or just ask in general chat?

ah ok ill try a different cable.. as i unmount and then usually spin the drive down.. as i havent been unplugging the drive.. and i thought the unraid 6.10 was supposed to solve that issue u could add remove the drive without mounting and didnt need a reboot.. ill try a new cable then.... start from there it gets frustrating cuz i make sure to unmount then least spin down... and its hard to tell cuz cable looks fine and the enclosure doesnt say nothing and smart shows nothing.. guess best to try a new cable....

what does the reboot mean? before it was cant mount.. now its reboot.. it seems to be this 1 hard drive i always have issues with whats going on i unmount and hit the spin down the drive before i remove it.. does it say anything is something wrong with the hard drive or is the using the star tech enclosures? tardis-diagnostics-20220610-1739.zip

ah ok wasnt sure about that parity.. but thats good .. good you dont need to start over 🙂