rkulagow Posted February 24, 2023 Posted February 24, 2023 It appears the my flash drive is no longer functioning; I've ssh'd into the machine, and /boot is full of random looking garbage. Â For example, /boot/config/parity-checks.log has things like this: 2022<A0>May ^Q5 1;:1$:03|^T<B7>642|!26.0 MB's|0|0 202b I<E1>y 2" 13:20:35|4>034|124/9 MB/s|0|0 2<B0>22 Iay 2y 12:15:0^R\47701~165.8 MB/s|0|0 2022 Htn 5 13:"8:47|48526|123^N7 MB/s}0|2022 J<F5>n 12 93^Z47:53~49672|120.8 EJ/s|0| <B2>022"Jun 19 33:16:54|476;3|125.8 MBos|0| r022 Jun!26 13:14:14|4^W653|125.9 MB/s|0t4 2022 J<F5>l` 3 !3:14:42<47681~325.9 MB/s|0|8 r022 Jul 10 13:14:39|47278|125.9 MB/r| |1 002: Jul 15 13:24:11|48250|120.4 OB/s|0|0 Â My Plus.key file also appears to have high-ASCII characters. Â So, given that the machine is still running, is it possible to export the running config that's in memory, so that my shares, Docker configs, etc, are all retained? I did a flash backup, but I think it would be GIGO at this point. Â Or do I obtain a fresh flash drive and reboot with that? Knowing which drive is parity and which are data is easy, because my parity is larger than my data drives. But what about all the other settings? My Plus.key is from 2016, so I don't know that I have that email around any longer. Â tower-diagnostics-20230223-1805.zip Quote
trurl Posted February 24, 2023 Posted February 24, 2023 2 minutes ago, rkulagow said: I did a flash backup, but I think it would be GIGO at this point Do you mean you did the flash backup after it was already corrupt? Â Quote
rkulagow Posted February 24, 2023 Author Posted February 24, 2023 I've been checking in all the usual places where I might have a flash backup downloaded, (uncorrupted), but at this point I'm assuming that it's gone. Â Quote
trurl Posted February 24, 2023 Posted February 24, 2023 https://wiki.unraid.net/Manual/Changing_The_Flash_Device Quote
rkulagow Posted February 24, 2023 Author Posted February 24, 2023 Thanks - I've been following that page and I've prepped a new flash drive. But will Unraid be able to re-establish my shares and docker configurations and VMs based on what's already on the hard disks, or will those be lost because the flash drive /boot/config directory is corrupted? Â Quote
trurl Posted February 24, 2023 Posted February 24, 2023 Everything about your configuration is in the config folder on flash. All settings made in the webUI, including disk assignments, your license, docker templates, share settings, plugins, ... Â User shares are simply the combined top level folders on array and pools. If a top level folder exists on array or pools, there is a user share with the same name as the folder. But without the .cfg file for each share in config/shares, a share has default settings. Â Dockers are on your storage, so they will still exist, but without the templates from config/plugins/dockerMan/templates-user, you will not be able to work with them from the webUI. Quote
trurl Posted February 24, 2023 Posted February 24, 2023 Many things in config folder on flash are text files that can be read in a text editor. You can examine each of the files in config and see if any of them can be used. Quote
rkulagow Posted February 24, 2023 Author Posted February 24, 2023 Since I have SSH, I've been just cat'ting the files to see what's in them. It's not looking good; even the filenames aren't valid in a lot of cases. Â So, just start taking screenshots of the running configurations, and rebuild what I can once I've rebooted onto a new Flash drive seems like my only course of action? Â There's no way to dump the config which is already in memory? Â Quote
trurl Posted February 24, 2023 Posted February 24, 2023 28 minutes ago, rkulagow said: dump the config which is already in memory? Don't know where that is. Â MyServers plugin will keep a current backup of flash on Unraid cloud. Quote
Recommended Posts
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.