comet424

check mark its unclickable when its white.. unable to check the file system if i cant mount it, as your steps was to check the file system before you mount it.. but white check mark does nothing oh ok.. ya i think it was just a spare drive from another unraid i had and shoved it in my sisters box to use.. but that was last year so i didnt remember... ya if its part of data disk then ya i dont need it.. i dont use unraid all the time its a set it and forget it.. so i appreciate you guys that know it 100% as i know it 5% lol i wish i stuck with linux 20 yrs ago i just hated linux in 2000 and later Redhat gui and command line cisco in 2000. should have stuck with it all instead of just windows lol ill format it then 🙂

ill probably just try to format the drive dont think i have anything important on it

so i tried.. there is no Tool Tip for the White Check mark as u cant mount the drive the drive log i didnt copy it all.. so hovering over the check mark doesnt tell me how to check the file system of the drive.. and how to repair it Mar 25 18:36:58 mitchsserver kernel: BTRFS error (device sdd1): devid 1 uuid 5be4c804-26b8-4b18-9454-aec4c376ea38 is missing Mar 25 18:36:58 mitchsserver kernel: BTRFS error (device sdd1): failed to read the system array: -2 Mar 25 18:36:58 mitchsserver kernel: BTRFS error (device sdd1): open_ctree failed Mar 25 18:36:58 mitchsserver unassigned.devices: Mount of 'sdd1' failed: 'mount: /mnt/disks/WD-WCAZA2404054: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error. ' Mar 25 18:51:59 mitchsserver emhttpd: spinning down /dev/sdd Mar 25 20:54:12 mitchsserver unassigned.devices: Adding partition 'sdd1'... Mar 25 20:54:12 mitchsserver unassigned.devices: Mounting partition 'sdd1' at mountpoint '/mnt/disks/WD-WCAZA2404054'... Mar 25 20:54:12 mitchsserver unassigned.devices: Mount drive command: /sbin/mount -t 'btrfs' -o rw,noatime,nodiratime '/dev/sdd1' '/mnt/disks/WD-WCAZA2404054' Mar 25 20:54:18 mitchsserver kernel: BTRFS info (device sdd1): using free space tree Mar 25 20:54:18 mitchsserver kernel: BTRFS info (device sdd1): has skinny extents Mar 25 20:54:18 mitchsserver kernel: BTRFS error (device sdd1): devid 1 uuid 5be4c804-26b8-4b18-9454-aec4c376ea38 is missing Mar 25 20:54:18 mitchsserver kernel: BTRFS error (device sdd1): failed to read the system array: -2 Mar 25 20:54:18 mitchsserver kernel: BTRFS error (device sdd1): open_ctree failed Mar 25 20:54:18 mitchsserver emhttpd: read SMART /dev/sdd Mar 25 20:54:18 mitchsserver unassigned.devices: Mount of 'sdd1' failed: 'mount: /mnt/disks/WD-WCAZA2404054: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error. '

ok the SSD mounted.. i been trying to learn this encrypted stuff. always learning how do i run the file check? i dont do this everyday so i forget what is what

oh maybe i did practice the btrfs encrypted.. let me try... spinner drive wont even mount anymore and its not password protected but ill tryt the password for the ssd

unable to mount my drive anymore running UD 2022.03.24. Mar 25 17:52:03 mitchsserver unassigned.devices: Mount of 'transport_data' failed: 'mount: /mnt/disks/transport_data: special device /dev/mapper/transport_data does not exist. ' Mar 25 17:52:10 mitchsserver root: error: /webGui/include/ProcessStatus.php: wrong csrf_token Mar 25 17:52:18 mitchsserver unassigned.devices: Mount of 'transport_data' failed: 'mount: /mnt/disks/transport_data: special device /dev/mapper/transport_data does not exist. ' spinner drive couldnt be mounted either Mar 25 17:52:03 mitchsserver unassigned.devices: Mount of 'transport_data' failed: 'mount: /mnt/disks/transport_data: special device /dev/mapper/transport_data does not exist. ' Mar 25 17:52:10 mitchsserver root: error: /webGui/include/ProcessStatus.php: wrong csrf_token Mar 25 17:52:18 mitchsserver unassigned.devices: Mount of 'transport_data' failed: 'mount: /mnt/disks/transport_data: special device /dev/mapper/transport_data does not exist. ' Mar 25 17:56:36 mitchsserver ntpd[1748]: frequency error 868 PPM exceeds tolerance 500 PPM Mar 25 18:06:11 mitchsserver kernel: BTRFS error (device sdd1): devid 1 uuid 5be4c804-26b8-4b18-9454-aec4c376ea38 is missing Mar 25 18:06:11 mitchsserver kernel: BTRFS error (device sdd1): failed to read the system array: -2 Mar 25 18:06:11 mitchsserver kernel: BTRFS error (device sdd1): open_ctree failed Mar 25 18:06:11 mitchsserver unassigned.devices: Mount of 'sdd1' failed: 'mount: /mnt/disks/WD-WCAZA2404054: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error. ' Mar 25 18:06:16 mitchsserver kernel: BTRFS error (device sdd1): devid 1 uuid 5be4c804-26b8-4b18-9454-aec4c376ea38 is missing Mar 25 18:06:16 mitchsserver kernel: BTRFS error (device sdd1): failed to read the system array: -2 Mar 25 18:06:16 mitchsserver kernel: BTRFS error (device sdd1): open_ctree failed Mar 25 18:06:16 mitchsserver unassigned.devices: Mount of 'sdd1' failed: 'mount: /mnt/disks/WD-WCAZA2404054: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error. ' Mar 25 18:06:28 mitchsserver unassigned.devices: Mount of 'transport_data' failed: 'mount: /mnt/disks/transport_data: special device /dev/mapper/transport_data does not exist. ' mitchsserver-diagnostics-20220325-1754.zip

ah ok ya the guy in discord wasnt sure... but i figured id ask.. i appreciate the reply .. as it gets frustrating constantly editing thanks 🙂

i noticed with my transmission docker that when you delete or if you do a new install and delete fields.. it comes back next time Docker checks for updates or does updates.. it puts in 5 fields i deleted and breaks the settings file where you manually have to edit it.. i had to go around the block getting help and one person on discord said its an unraid issue that unraid might be working on.. but if its not i figured id ask for the next release to Disable Docker template sync... so it stops downloading template from the repositories my journey starting with transmission support page.. which is github they say not there problem to send you to transmssion website you cant create user account.. to me asking help in community apps forum.. and squid sent me to discord for linux respository... and in the end they tell me its an unraid problem.. so been around the block its a circle so they had me go into the flash drive /plugins/dockermon edit the my-transmission.xml and change <TemplateUrl>webaddress</TemplateUrl> to <TemplateUrl>false</TemplateUrl> so it stop basiclly bricking transmission everyday be nice an option in Template to say disable template sync.. as its a pain in the butt basiclly everday you need to delete 5 fields in transmission template and delete the settings file in the app data just to get it to work

but i guessing it just something to live with... living in country we dont get good internet we dont even get 5megabit.. get about 3 megabit for 100 bucks a month.. probably have to live with the slow docker ... but it is what it is right

what information..... so then when i cut the internet then docker will always be slow then.. cuz it cant gather internet info.. as i found if i bog the internet down.. docker takes more then a minute every time... but as soon as i unbog the internet it goes fast... but when i re bog the internet.. and click docker its back to slowness and you said ? goes away once its downloaded and stored never downloaded again.. that cant be true those above apps were installed 9 months ago or longer.. so if its stored it should never ? show up what i found is internet bog down.. click docker takes more then a minute and ? shows up unbig the internet click docker takes a few seconds and the ? are gone rebog the internet click docker takes more then a minute and the ? are back... they didnt save .. and now the 1 app says 9 months ago and other onese say it was created 19 hours ago.. so i totally confused well i dont think the dns address will work my sister uses netflix it bogs down 5mbps internet so thats what 500k... so internet is maxed full and impossible to use unraide to update.. you gotta stop the internet 5 megabit internet isnt fast.. and boggs down so much that google or unraid forums webpages constantly get page cant found.. as i have the same internet 5 megabit download and 500k upload.. so using a netflix or a youtube causes issues .. but ill try the dns but it probably wont work when 100% of internet goes to a netflix and unraid times out and so does any webpages but its just frustrating with the docker cuz im sitting there waiting and waiting wish i could just disable docker to ever gather any info so its always fast.. when internet is not there or bogged down 100% cuz my own unraid always bogged down and to reply to you here.. i have to always constantly stop video or netflix just to reply to unraid forums but wish docker would just not gather info when you have terrible speed internet i need docker to work fast with 100% internet ussage used so 0% to unraid.. or when 0 internet is offered is it possible?

or is it all on internet based? or what tweaks tips can tweak unraid to run smoothly so i dont get docker issues as unraid isnt always connected to internet either as if i turn off my all internet like netflix and her tv stuff.. on her 5mb/s unraid docker is faster and the icons are are normal so my question is.. is docker and the icons only internet based... and if you dont have internet then it cause's issue for loading the docker page and icon issues and just seems super slow

i know i asked before for my 1 server... but i noticing it again on another server my sister has 5 docker apps only one running is plex... docker takes 1 min or so or so to load.. and it gets ? is plex the cause of this as i have same issues on my own server i personaly think something wrong maybe plex does something? i also asked but no one ever answered... should Plex Appdata go on its own SSD away from the appdata for other apps and i having troubles "stopping the plex container too" just spins but doenst actually shut down.. does the diagnostics say why its slow? mitchflix-diagnostics-20220316-1758.zip

hi i have trouble understanding all this stuff.. and i try to run nano in the console terminal for the mosquitto but doesnt work i want to do is send home assistant a command to turn on a switch.. but want to run from a user script i have "test" as the topic "turn_on" as a message to turn on "turn_off" as a message to turn off i hjave no idea what i doing... i tried to read the documenations.. is there any docs for a noob so i can run like "mosquitto test/turn_on" something like that .

i dont know what i need.. i really dont understand mqtt broker or mosquito which is the server.. i guess broker and mosquito is the client? what i trying to do is i got home assistant running and set up 2 automations.. 1 to turn on a switch and other to turn off the switch for now i use "test" as the topic "turn_on" as the message to turn on switch "turn_off" as the message to turn off the switch works in mqtt part in home assistant to test but i dont know how to do it in unraid.... as i want to run in a script like "mqtt test/turn_on" to turn on the switch "mqtt test/turn_off" to turn off the switch but i tried installing the mqtt and went to the gui page and that didnt help me and i installed the mosquito and well the logs tell me options i domt know i just wanted a command line so what do i need to get what i need to do.. as i dont really know what i need.. and i tried google and it didnt help me

i figured it out i had to re load it.. this Thumbs up didnt show up.. guess i need to really reboot windows been up for 3 weeks no reboot

i think i did something wrong i connected it gave me welcome and rules but i cant post in welcome... i read the rules but no option to join the chat to ask did i do something wrong says i dont have permission to send messages in this channel but i only have #welcome and rules

thank you 🙂 that got me connected i appreciate it 🙂

i have discord.. how do i add linuxserver to the discord.. as i have it for unraid

can you guys verify if the community app "transmission" is compatible or basiclly defunct i doing an unraid install for a friend and installed transmission but it no longer works. i did have issues before and there is no "unraid" support page only a github and on there they do no want your questions they tell ya to goto transmission website we.. you cant create an account on the transmission website i get these log erros from a clean install ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 01-migrations: executing... [migrations] started [migrations] no migrations found [cont-init.d] 01-migrations: exited 0. [cont-init.d] 02-tamper-check: executing... [cont-init.d] 02-tamper-check: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [2022-03-12 10:54:29.113] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:29.113] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:30.104] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:30.105] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:31.105] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:31.105] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:32.106] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:32.106] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:33.109] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:33.109] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:34.110] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:34.110] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:35.111] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:35.111] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:36.113] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:36.113] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:37.115] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:37.115] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:38.118] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:38.118] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:39.118] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:39.118] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:40.119] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:40.119] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:41.121] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:41.121] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:42.122] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:42.123] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:43.123] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:43.123] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:44.126] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:44.126] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:45.126] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:45.126] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:46.128] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:46.128] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:47.130] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:47.130] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:48.132] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:48.132] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:49.134] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:49.134] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:50.135] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:50.135] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:51.136] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:51.136] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:52.138] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:52.139] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:53.140] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:53.140] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:54.141] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:54.141] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:55.144] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:55.144] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:56.146] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:56.146] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:56.146] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:56.146] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:57.147] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:57.147] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:58.148] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:58.148] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:58.148] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:58.148] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:54:59.151] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:54:59.151] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:00.152] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:00.152] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:01.153] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:01.154] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:02.153] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:02.154] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:03.155] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:03.155] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:03.155] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:03.155] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:04.157] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:04.157] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:05.159] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:05.159] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:05.159] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:05.159] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:06.161] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:06.161] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:07.161] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:07.161] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:07.161] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:07.161] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:08.163] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:08.163] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:09.166] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2022-03-12 10:55:09.166] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) [2022-03-12 10:55:10.168] JSON parse failed in /config/settings.json at pos 902: SPECIAL_EXPECTED -- remaining text "peerport, "p" [2 so i wanted to know if its gone defunct for unraid what is working is "transmission-nzbtomedia" but not "transmission" so i figured id ask and report it incase its no longer a compatible program with unraid anymore

so what does that rooshare mean and actually do..? does that the automount? it places the Share folder of the ud drive.. to the /mnt/user/ directory? is that what that means as i dont understand.. since i never used rootshare? i just use the automount and autoshare option to have the folder pop up in the sambre share

ya its a backup its just my sister lives a few hours away so once or twice a week we meet half way and we swap ssds and i store her files.. and i dont think she got static shock but you never know it doesnt tell ya oh just got shocked... damn things i tell ya the Sata Ports are set for Hot Swap in the Bios.. and its a 4 bay slide in.. and i use a Sabrent 3.5 to 2.5 holder that sits inside the tray so i can hot swap the ssd from a 3.5 bay so i wanted to least try to get the files.. windows cant even see the disk guess its cooked and ya i should have enable UD plugin cuz they all work and i helped ya figured the bugs you were having in the UD Plugin a month ago.. and it auto updates everyday... so i not sure what you all mean about the rootshare part and the conf file in your other comment.. i just make sure ud and all plugins up to date and the UD just works.. all i know lol so i guess i best RMA SSD and get another one

so it didnt happen in latest version also the change uuid grayed out and unclickable is there any way to fix this or is the drive totally gone Mar 11 02:13:21 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:13:36 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:13:52 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:14:20 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:14:35 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:14:50 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:15:18 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:15:33 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:15:48 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:16:16 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:16:31 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:16:47 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:17:15 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:17:30 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:17:45 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:18:13 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:18:28 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:18:44 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:19:11 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:19:27 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 11 02:19:42 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) i use ssd for easier hot swapping transport but maybe hot swapping isnt good? the BIOS is set for hot swap i unmount the SSD and slide it out but maybe they still get corrupt? i know in the 90s when i used dos... we used the program PARK to park the heads of the drives before transporting to lan parties etc.. now i dont know when you power down drives if parks heads on spinners and i dont know if its safe to hot swap ssds buti figured ssds were better this sdd not even a year old it had 1 relocate error but that happened i guess bad sata cable least 5 yr warrenty but like to try to get files off if i can and can you see what the errors mean the mitchserver is where the ssd came out of. it was working before 1pm before my sister had pulled it out.. but i had it unmounted.. does the diagnostic i just took say anything with the errors i see backupserver-diagnostics-20220311-0641.zip mitchsserver-diagnostics-20220311-0655.zip

maybe spinner drives are better for hot swapping on regular basis since something happened to SSD ugh.. as i swap with my sisters server.. it was working i unmount and she slides the ssd out of the tray and adapter tray.. and then i get it.. now i cant mount it..

i cant get my ssd to mount.. i getting some ata errors.. i tried my other server and same errors.. is the ssd cooked. or can i force a mount etc any info? i took 2 diagnostics 1 and the 2nd one i tried a different sata i tried reboot and a shut down and turn back on but cant access it as i need to get the files off it 3rd one is from my other server.. how can i scan disk like force a mount etc i also getting the other errors now too thats from version 2022.02.27b... gonna update to your latest Mar 10 22:14:04 backupserver kernel: BTRFS warning (device <unknown>): duplicate device /dev/sdb1 devid 1 generation 741242 scanned by udevd (3489) Mar 10 22:14:13 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 10 22:14:29 backupserver kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40) Mar 10 22:14:41 backupserver kernel: BTRFS warning (device <unknown>): duplicate device /dev/sdb1 devid 1 generation 741242 scanned by udevd (3609) Mar 10 22:14:42 backupserver kernel: BTRFS warning (device <unknown>): duplicate device /dev/sdb1 devid 1 generation 741242 scanned by udevd (3609) tower-diagnostics-20220310-2034.zip tower-diagnostics-20220310-2024.zip backupserver-diagnostics-20220310-2135.zip backupserver-diagnostics-20220310-2233.zip

@GMAsterAU no i never i ended up just using the board to play with unraid and Truenas.. which truenas is frustrating me.... i think sometimes if it worked.. it only work if i sleeped unraid... but i havent tried in a while.. and i havent updated to the latest bios but i should retry.. as with this pandemic i couldnt afford another compujter so i just use this one to play with things but i should retest it.. i havent bothered to test it.. or update if it has a 2022 bios update if there is one