icopy

Members
  • Posts

    11
  • Joined

  • Last visited

icopy's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Great News. Do you mean: Changing: <<<=========== # Generated settings: startArray="yes" To: ==========>>>> # Generated settings: startArray="no" Thanks.
  2. Here's what I should do. Please see if I get it right. 1. Build a new flash drive. 2. Copy all the config files onto the new flash drive. 3. Start the machine and use webUI to transfer keys. 4. Use Unassigned Devices plugin to verify disk to be data or parity. 5. Reconfig the array. I should get: 1. Data on array intact. 2. VM, Docker and other settings intact? By the way, does the order of disk (disk1, disk2, ....) matter? Thanks.
  3. 1. Can you read anything of the old flash drive? Everything that is specific to your system is stored in the 'config' folder on the flash drive. I've managed to copy some of the config files from the flash drive. Most of the text files seem to be intact. But I can't say the same for other binary files. Is Plus.key the license file? It seems to be encrypted. 2. Do you know which driver were parity drives and/or cache drives? The smart info in diagnose files and my last config log are inconsistant. I don't know which one is correct. sdb-sdi are consistant. The disk numbers are not. The smart info is much more recent. My config log is at least 6 month old. Config log: Smart info: Samsung_SSD_970_EVO_500GB_S466NX0MC14637H-20201216-2224 cache (nvme0).txt ST4000VX007-2DT166_ZGY6NXYW-20201216-2224 disk5 (sdh).txt ST4000VX007-2DT166_ZGY6P1S4-20201216-2224 disk6 (sdi).txt ST4000VX007-2DT166_ZGY6P66Q-20201216-2224 parity2 (sdg).txt TOSHIBA_MD04ABA400V_2869KY7EFMYB-20201216-2224 disk4 (sdf).txt TOSHIBA_MD04ABA400V_58BXKCXIFMYB-20201216-2224 parity (sdb).txt TOSHIBA_MD04ABA400V_58D1KAVXFMYB-20201216-2224 disk3 (sde).txt TOSHIBA_MD04ABA400V_58DFKVTFFMYB-20201216-2224 disk2 (sdd).txt TOSHIBA_MD04ABA400V_58EOKCF9FMYB-20201216-2224 disk1 (sdc).txt VendorCo_ProductCode_920702127A907718462-0-0-20201216-2224 flash (sda).txt The latest parity check is on Dec 7th. The ECC error began as early as Aug. 2020 Sep 7 18:58:50|66529|60.1 MB/s|0|0 2020 Dec 7 18:13:16|63795|62.7 MB/s|0|0
  4. What happenned: * Log filled with ECC Error. Syslog is filled with memory error logs. See attached diagnostics files. Usually solvable by rebooting. * Fail to reboot. I tried to reboot the system, but console showed "SYSLINUX: No DEFAULT or UI configuration directive found!" * USB Flash data corrupted. I found syslinux configuation file is corrupted. Later, I discovered that most of the files on the flash drive has been corrupted. What I am trying to do: * Preserve array data. I have a 8 disk array with 2 parity drive. I am not sure what to do to safely transfer new config on to a new flash drive. * Preserve VM data and config. * Preserve plugin / docker data and config. - Jellyfin. I've installed Jellyfin as media center. Although it does not has significant data value but I've spent quite a lot time on it. Is it possible to preserve its data and configurations. - Other plugin to help run Unraid and UPS, such as CA, Nerd Pack, NUT. How should I proceed? * I bought a new flash drive and read wiki https://wiki.unraid.net/UnRAID_6/Changing_The_Flash_Device. * I'm looking for better way to preserve data and config. Thanks. tower-diagnostics-20201216-2224.zip
  5. It is a bit OCD. Is it possible to change disk device name from "Parity" to "Parity 1"? So it looks aligned?🙃
  6. It seems that I've fixed the problem. Open VM tab Edit VMs in XML mode Change "port" properties in "graphics" section from -1 to a valid number, like 5702 Change "websocket" properties in "graphics" section from -1 to a valid number, like 5902 I don't know how these properties are set to -1. There is not place in the form view to change these values. If unable to make these changes due to nginx workers crashing, restart the unraid server and don't open any vnc view before changing these values.
  7. Same here. This has something to do with VM and webUI. Here's /var/log/nginx/error.log ker process: ./nchan-1.2.6/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2020/03/13 14:14:07 [alert] 3138#3138: worker process 3368 exited on signal 6 ker process: ./nchan-1.2.6/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2020/03/13 14:14:10 [alert] 3138#3138: worker process 3371 exited on signal 6 ker process: ./nchan-1.2.6/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2020/03/13 14:14:13 [alert] 3138#3138: worker process 3377 exited on signal 6 These messsages appear even after I restart nginx.
  8. Thanks for the reply. If I check "parity is already" as you've suggested, will I lose data in the future? Even though I don't have any data at the moment. Is this the recommended way to start a new array?
  9. I'm new to unraid. I've just setup an array with 5 new Toshiba 4T hard drive. 4 data and 1 parity. Also I added a nvme ssd as cache. I transfered about 120+G files for testing. Somehow after a reboot, the parity drive requires a parity-check. I don't think it's necesary and I don't want to do this parity-sync. So I've tried to: a) change the file system for all data drives and format all data drives. b) reset the array. Yet the unraid os still asks to do a parity-sync. How can I avoid this parity-check? Thx.