MorgothCreator

Members
  • Posts

    24
  • Joined

  • Last visited

MorgothCreator's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Wats happening, after the last update, UnRaid 1.9.1: Mar 26 18:00:00 ecaace443c98 zmdc[1516]: INF ['zma -m 6' started at 21/03/26 18:00:00] Mar 26 18:00:00 ecaace443c98 zmdc[850]: INF ['zma -m 6' crashed, signal 6] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF [Starting pending process, zmc -m 2] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF ['zmc -m 2' starting at 21/03/26 18:00:01, pid = 1517] Mar 26 18:00:01 ecaace443c98 zmdc[1517]: INF ['zmc -m 2' started at 21/03/26 18:00:01] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 2] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF ['zma -m 2' starting at 21/03/26 18:00:01, pid = 1518] Mar 26 18:00:01 ecaace443c98 zmdc[1518]: INF ['zma -m 2' started at 21/03/26 18:00:01] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 11] Mar 26 18:00:01 ecaace443c98 zmc_m2[1517]: INF [zmc_m2] [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor is not part of your debug targets] Mar 26 18:00:01 ecaace443c98 zmdc[1519]: INF ['zma -m 11' started at 21/03/26 18:00:01] Mar 26 18:00:01 ecaace443c98 zmdc[850]: INF ['zma -m 11' starting at 21/03/26 18:00:01, pid = 1519] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 9] Mar 26 18:00:02 ecaace443c98 zma_m2[1518]: ERR [zma_m2] [Shared data not initialised by capture daemon for monitor CAM6] Mar 26 18:00:02 ecaace443c98 zmdc[1520]: INF ['zma -m 9' started at 21/03/26 18:00:02] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF ['zma -m 9' starting at 21/03/26 18:00:02, pid = 1520] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 8] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF ['zma -m 8' starting at 21/03/26 18:00:02, pid = 1521] Mar 26 18:00:02 ecaace443c98 zmdc[1521]: INF ['zma -m 8' started at 21/03/26 18:00:02] Mar 26 18:00:02 ecaace443c98 zmdc[850]: ERR ['zma -m 2' exited abnormally, exit status 255] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF ['zmc -m 2' crashed, signal 6] Mar 26 18:00:02 ecaace443c98 zmdc[850]: INF ['zma -m 11' crashed, signal 6] Mar 26 18:00:03 ecaace443c98 zmdc[850]: INF ['zma -m 8' crashed, signal 6] Mar 26 18:00:03 ecaace443c98 zmdc[850]: INF ['zma -m 9' crashed, signal 6] Mar 26 18:00:21 ecaace443c98 web_php[594]: ERR [Potentially invalid value for ZM_LOG_DATABASE_LIMIT: 30 day] Mar 26 18:01:22 ecaace443c98 web_php[1072]: ERR [Potentially invalid value for ZM_LOG_DATABASE_LIMIT: 30 day] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF [Starting pending process, zmc -m 2] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF ['zmc -m 2' starting at 21/03/26 18:01:23, pid = 1535] Mar 26 18:01:23 ecaace443c98 zmdc[1535]: INF ['zmc -m 2' started at 21/03/26 18:01:23] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF [Starting pending process, zma -m 2] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF ['zma -m 2' starting at 21/03/26 18:01:23, pid = 1536] Mar 26 18:01:23 ecaace443c98 zmdc[1536]: INF ['zma -m 2' started at 21/03/26 18:01:23] Mar 26 18:01:23 ecaace443c98 zmc_m2[1535]: INF [zmc_m2] [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor is not part of your debug targets] Mar 26 18:01:23 ecaace443c98 zmdc[850]: INF ['zmc -m 2' crashed, signal 6] Mar 26 18:01:23 ecaace443c98 zma_m2[1536]: ERR [zma_m2] [Shared data not initialised by capture daemon for monitor CAM6] Mar 26 18:01:23 ecaace443c98 zmdc[850]: ERR ['zma -m 2' exited abnormally, exit status 255]
  2. Ohh, I will give a try when I will have the occasion ๐Ÿ˜€๐Ÿ‘
  3. The more you fix things, the more broken they are ๐Ÿคฆโ€โ™‚๏ธ. Now Gitlab does not even start: Upgrading PostgreSQL to 11.7 cp /opt/gitlab/embedded/service/gitlab-rails/public/deploy.html /opt/gitlab/embedded/service/gitlab-rails/public/index.html ok: down: gitaly: 0s, normally up ok: down: logrotate: 1s, normally up ok: down: registry: 0s, normally up ok: down: sidekiq: 1s, normally up ok: down: sshd: 0s, normally up There was an error fetching locale and encoding information from the database Please ensure the database is running and functional before running pg-upgrade STDOUT: STDERR: psql: FATAL: the database system is starting up == Fatal error == Please check error logs == Reverting == ok: down: postgresql: 0s, normally up ok: run: postgresql: (pid 722) 0s == Reverted == == Reverted to 10.12. Please check output for what went wrong == rm -f /opt/gitlab/embedded/service/gitlab-rails/public/index.html ok: run: gitaly: (pid 744) 1s ok: run: logrotate: (pid 808) 0s ok: run: registry: (pid 821) 0s ok: run: sidekiq: (pid 832) 1s ok: run: sshd: (pid 838) 0s Upgrading the existing database failed and was reverted. Please check the output, and open an issue at: https://gitlab.com/gitlab-org/omnibus-gitlab/issues If you would like to restart the instance without attempting to upgrade, add the following to your docker command: -e GITLAB_SKIP_PG_UPGRADE=true
  4. Hi, is the forth or fifth update and the issue was not fixed The issue is that when I click to a file link will go to "https://git.devboard.tech:9443/tips/linux/-/blob/master/crontab-check-start-app.md" instead of "https://git.devboard.tech/tips/linux/-/blob/master/crontab-check-start-app.md" for example. This behaviour is valid for all files on the gitlab. The git is up and running, you can check it. The rest if pages are OK. This issue has appeared about five updates ago, I do not changed any configuration file, I do not touch anything, after the update I see this behaviour.......
  5. Hi what happened to the last update, After the update all work fine except when I want to access the individual file, the gitlab insert the internal port 9433 to the link and and the browser does not want to load the file, check it here for example: https://git.devboard.tech/boot-loaders/fpga-risc-v If you navigate the directories all OK, when you load file the issue appear.
  6. Same here, What happen if I kill him or restart him from time to time? ๐Ÿ˜€
  7. I see that has only support for mem, not for memmap. Ehh maybe in future the Syslinux guys will add support for memmap, or Unraid will use Grub, maybe both, Maybe Unraid can introduce a way to select between the two bootloaders ๐Ÿ˜€, is a cool feature because like in my case because of one bit you need to throw away an entire stick of RAM (and is part of a kit of four Corsair Dominator Platinum 3000Mhz ( now I see that are not so platinum how they tell ) ๐Ÿ˜ช) . Of course I removed it immediately after I tested it ๐Ÿ˜€ Merry Christmas and best regards.
  8. Ohh, so is no chance for skipping that bit :((, poor 16GB stick. Thank you very much.
  9. Hi I discovered that one of my four 16 GB sticks has only one bit stick to '1' logic, this was from when I bought them, but I have been gone out of my country for two years. Now I am home and make the memtest86 test and see this bit, this bit has bothering me for all that two years, because the Unraid never crash, only see some disk corruption. First I used BTRFS and partitions begin to be corrupted in several days and give me IO errors when try to copy large files, the rest of corruption was silent. After that I used XFS, but because XFS has no check summing, all corruption was silent. After that I put ZFS, and here I begin to see that something was seriously wrong, because each day ZFS reported me around 10 crc errors, at a traffic of around 200GB/day on SSD's. Now that i tested the ram I know where is the problem, one bit out of 64GB stick to '1' :)))))))))) I navigate some DuckDuckGo and find this: https://help.ubuntu.com/community/BadRAM that warm my day, because the ram was bought from another country, and to use warranty will take around two months and for sure I will need to send the entire kit, not only the bad RAM :) The problem is that in Unraid does not exist this file: "/etc/default/grub", the directory exist, but not the file. Someone has an idea how can I setup BADRAM and if is supported by Unraid grub? Thank you
  10. The problem seems to be from tar application. I decompress the ova archive using tar from Synology DSM on the VM, after that, I copied the vmdk image to the Unraid machine and convert it to qcow2 with qemu-img on the Unraid, and the conversion was done successfully. So, something is wrong with tar application working with large files on the Unraid OS.
  11. I see that the problem is on writing to the disk, not on reading, because the error on the file is happening at the same sector when I read the same write file, and the sector change if I rewrite the file and try to read it again. I mentioned that I have a VM with 4 pass-through disks that never had problems, so all components are working properly. The system does not report any other problem, does not freeze, or have strange behavior, being up and running for several weeks in a road. The problem is only when working with big files, like image disks and large videos. On some rare occasions when VM virtual disk is edited by the VM machine the entire disk is corrupted ( happened one time ). When the Windows7 VM has corrupted the disk, when has been shut down by me, the Unraid web page stop responding because has stuck on waiting the disk to respond, but the other VM's and docker run normally ( working on other disks ), when I open the web terminal, has opened normally and I can send commands, the disk was mounted and was navigable, only after Unraid (unclean off course, because after several hours the system refuse to restart ) restart the corruption of the disk was observable. I think that is something with FS arbitration between multiple app's writting on the same disk or something like that.
  12. I know that here are some topics with the same issue, but this issue need to never happen on a server system. So, the story is that some time I want to move data around from a disk to another, to compress some data, to decompress it etc. But on large files some time is getting me Input/Output read error and I am tired of this error on a paid OS. The btrfs check is with no errors, and this Input/Output error is getting me on both , on array and on unassigned devices. Mention is that I virtualized a Synology DSM with pass through and that system is working without any errors, so I know that is not a device fault, but something with FS implementation. Another mention is that the machine is on a semiprofessional UPS, so, can not be a power fault. Last time I try to convert a 70GB image and this is the result: qemu-img convert -f vmdk -O qcow2 SomeFile-disk1.vmdk SomeFile.qcow2 qemu-img: error while reading sector 7978112: Invalid argument And the conversion can not pass this sector. The same error some time give me tar application on large files. The mv and cp never fail or report IO issues but I see sometime artifacts on videos, so the issue is present even in mv and cp, so in one sentence, about all my large files are corrupted to put it like that. I see it on transmission when is reporting disk error and I need to put it to check the file multiple times, and transmission use a virtualized docker disk. When I recreate the source file and try the same above command, will give error on another sector or some time no error. One time an entire disk was corrupted when I powered down a Windows7 VM, and that disk was unrecoverable, needed format. The system is: Thredripper 1950X liquid cooled, with 64GB matched RAM kit on a ASROCK Taichi X399 motherboard, Power source 1200W, UPS APC Smart-UPS C 1000VA LCD the OS is 1.7.2. All rotated disks are from WD, The SSD's are from Samsung and are PRO or Evo, a single SSD is from Intel and is a 120GB and never give me a error because, I suppose that I never transferred large files on it. What is happening???????????
  13. ...... I want to centralize all servers around my house to a single one, a Threadripper 1950X with 64GB RAM ๐Ÿ˜€, and for this I need to mount a IMG usb disk image with the VID:PID instead of using the physical USB device, because the OS can not run if does not detect the expected VID:PID.
  14. Hy, Is there a way to pass to a VM an img virtual usb disk with VID and PID attached to it?
  15. Same error here on a Threadripper 1950x a ASRock X399 Taichi board and Nvidia GTX1080TI and Unraid 6.7.2