sdfyjert

Members
  • Posts

    28
  • Joined

  • Last visited

About sdfyjert

  • Birthday 04/26/1980

Converted

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sdfyjert's Achievements

Noob

Noob (1/14)

4

Reputation

  1. Finally the new PSU arrived. System now works again as expected. Whatever happened that night the 550W PSU could no longer properly run an 105W on-demand system (that's how much power it draws during rebuild). Thank you all for your help and advice.
  2. After a lot of further investigation today I am getting more and more convinced the issue is with unraid crashing due to some bad data on a disk. Here's how it went I loaded a usb-stick backup from a few days ago (before all hell broke loose) I boot up unraid (array off), the disk that was marked earlier today (but not when the issues started) as dirty and in need of parity fix is now green (this sounds like a bug) I start the array.... all hell breaks loose (reboot) Safe mode... the same... I disable everything (docker, VM manager) I manually disable the drive that needed rebuild (that was marked as dirty days after the reboot issues started). Start the array - no reboot. Reboot in safe mode Keep array offline Start an extended smart test on the dirty drive (now marked as green just by loading an older backup on the usb stick) Let it run for 10 minutes... no reboot. (stopped it there, as with the array running it would have rebooted as all the previous times) I am unfortunately yearning more and more towards software issue... this is extremely discouraging so far.
  3. I have already tried that, since day 0, the machine would reboot the moment disk check was starting. I have also tried switching the power cables for the drives to different PSU outputs with no positive results. I was going through the logs, in one of them only I found 2 entries that would normally look suspicious Apr 10 13:37:53 nas kernel: mpt3sas 0000:01:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM But it only exists in a log from earlier this morning (twice). In all previous days and since that it hasn't appeared again. The latest thing I did before the issues started appearing was an update on the filemanager (dynamix). I would like to believe it is not related in any way.
  4. I have checked the syslog (was already recording it) and there's nothing out of the ordinary there. The messages I see in the display with the pictures posted earlier do not appear in the syslog which means syslog is not started at that point yet. As of today things have taken a turn for the worse. Now it randomly reboots, one of the drives got disabled and marked for errors (it is currently being emulated). Taking the machine offline is not much of an option right now. Running check/fix is impossible as it just reboots the system. Running SMART short tests all drives appear to be fine (extended SMART cannot run as it reboots before they are finished). Currently waiting for the easter days to pass so I can get a new PSU delivered to test it out. If things continue down that path I am considering installing truenas on the same hardware (just different drives) out of curiosity to verify if it is hardware or software related. In the meantime, any ideas are welcome. fingers crossed
  5. I video recorded the display, booting on normal mode and safe mode, I get the following. Sorry for the poor quality but it's moving really fast, it's the best the camera could capture. It has been running parity checks and even a rebuild recently with the exact same configuration for ever a year. Here are the two last ones, not long ago. Any clues?
  6. That was my first idea as well. But in normal mode the machine properly powers on with all Dockers (tried it in both maintenance and normal mode). Is parity check drawing more power than starting the array and initializing all the Dockers? Certainly worth testing. Will report back with update asap.
  7. Hi guys, out of the sudden, every time I try (or the system tries) to initiate parity check the server goes into hard reboot. This happens in both normal and safe mode. I checked logs but couldn't spot anything. I am at a loss here and unraid is an integral part of my infrastructure (lab, home, work) I am open to suggestions and ideas. nas-diagnostics-20230406-1253.zip
  8. Hi, I have noticed every time I move a large number of large files using dynamix the docker containers and the web interface of unraid nearly freeze (they respond very sporadically). I find this very strange given it is running on an i7-8700 with load of below 50% during the move. Is there something I can tweak to fix this or is this a known issue that will be resolved with future updates? Please let me know how I can help you help me. Thank you nas-syslog-20230330-1236.zip
  9. Diagnostics attached to this post. inas-diagnostics-20220616-0227.zip
  10. Short story On the server there are currently 2 USB devices attached. The Unraid stick and an SD-CARD reader with a card inside. Upgrade succeeded but device was no longer bootable. Upgrading with ONLY the usb stick present it worked fine. Artifacts After the upgrade I now have the following device listed and no way of removing it. My cache drive appears to be all in order and properly listed. Is this something I should worry about? How can I remove it? The Odyssey New upgrade out. Checking the change log, I read about fixes with regard to data corruption so must have upgrade ASAP. But first things first... fresh Flash Backup... (seriously, NEVER ever skip that step. IMO it should be part of the upgrade process - please guys seriously consider adding it in the upgrade work flow). I click upgrade... downloads upgrade, installs it and asks to reboot. Flawless... ok, reboot. 10 minutes later... unraid nowhere to be seen in the network... searching for that bloody HDMI or DP cable (how I miss having a KVM)... after a looong search, I found one I could use. Latest messages on the terminal, boot device failed trying again click a button to reboot... Ok, let's recover using the back-up (never ever ever upgrade without a backup). Downloading the creator (mac)..., plugging in the Unraid stick... no USB stick listed. I click refresh, nothing. I must be doing something wrong... onward to the wiki. In the documentation it says USB stick size MAX 32GB (NOT TRUE). Really? I've been using the 128GB stick for years now... damn, might have something changed and it's now an issue? Taking out another stick 32GB max size, formatting FAT32, loading the creator, refresh... nothing. No stick listed... OK, so USB creator broken on mac... onward to Win10... all steps repeated... NO STICK LISTED (you can only get away with such things because most users are experienced, but seriously, even the open source apps copy-files-and-make-stick-bootable can always find the usb stick). Ok, so creator is broken (btw, was also broken years ago when I first purchased the unraid license). I'm thinking, it's UEFI, just copy the bloody files over and run the make_bootable_mac should do it. So I copy the files, open terminal, run the make_bootable_mac... will not run, unknown developer and the such... oook, preferences, allow... again... another binary that it tries to run same issue... same process, again... and another binary, same issue same process... DONE! All messages look ok except for that cannot get current directory (multiple times). ❯ ./make_bootable_mac INFO: make_bootable_mac v1.3 INFO: The following drive appears to be the unRAID USB Flash drive: /dev/disk2 123.7GB Permit UEFI boot mode [Y/N]: Y To continue please enter your admin Password: Sorry, try again. Password: INFO: Unmounting /dev/disk2 Forced unmount of all volumes on disk2 was successful INFO: Writing MBR on /dev/disk2 0+1 records in 0+1 records out 447 bytes transferred in 0.004785 secs (93417 bytes/sec) INFO: Mounting /dev/disk2 Volume(s) mounted successfully syslinux for Mac OS X; created by Geza Kovacs for UNetbootin unetbootin.sf.net shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory "/dev/disk2s1" unmounted successfully. shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory /dev/disk2s1 DOS_FAT_32 /Volumes/UNRAID shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory mountpoint is '/Volumes/UNRAID' checkpoint1 checkpoint2 checkpoint3 Processing: /Volumes/UNRAID/ldlinux.sys checkpoint4 checkpoint5 checkpoint6 checkpoint7 Processing: /Volumes/UNRAID/ldlinux.c32 checkpoint8 checkpoint9 checkpoint10 shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory "/dev/disk2s1" unmounted successfully. checkpoint11 checkpoint12 checkpoint13 checkpoint14 checkpoint15 shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory /dev/disk2s1 DOS_FAT_32 /Volumes/UNRAID syslinux installed successfully! INFO: the Unraid OS USB Flash drive is now bootable and may be ejected. Stick back to the NAS, booting... no luck, same errors 😰 Last try, stick to a windows machine, run the make_bootable.bat.... just a single line saying it's done. Stick back to the NAS, booting... YAY. But I REALLY want the upgrade... there are only 2 USB devices on the machine. Let's remove the SD-CARD reader... maybe something got it confused? 🤔 Upgrade... reboot... success! YAY! btw, It feels embarrassing that windows make_bootable worked when the mac one was failing.
  11. Hi, I am trying to set a device script to run after automounting. I switched on automounting for the device (works fine) then set a filename in the Device Script: /boot/config/plugins/unassigned.devices/scripts/import-script paste the script in the big text-area and click save at the bottom of the page. I can see the file is in place and generated with the script in-place with permissions -rw------- 1 root root 5189 Jun 4 11:25 import-script In the /boot/config/plugins/unassigned.devices/unassigned.devices.cfg I see the following "suspicious" entry command.1 = "/boot/config/plugins/unassigned.devices/packages/" I unmount then automount... script has not run. I open the settings again, Device Script shows packages folder. I switch to the scripts folder, no file is shown for selection. What am I doing wrong?
  12. Hi, I am trying to set a device script to run after automounting. I switched on automounting for the device (works fine) then set a filename in the Device Script: /boot/config/plugins/unassigned.devices/scripts/import-script paste the script in the big text-area and click save at the bottom of the page. I can see the file is in place and generated with the script in-place with permissions -rw------- 1 root root 5189 Jun 4 11:25 import-script In the /boot/config/plugins/unassigned.devices/unassigned.devices.cfg I see the following "suspicious" entry command.1 = "/boot/config/plugins/unassigned.devices/packages/" I unmount then automount... script has not run. I open the settings again, Device Script shows packages folder. I switch to the scripts folder, no file is shown for selection. What am I doing wrong?
  13. I have a cache only share (`/mnt/user/tmp`). Lately fix common problems has found a bit troublesome too often that the cache-only tmp share is appearing on the array disks. This is not new, I have seen it in the past but it was way too rare like once a year. Now all of the sudden it starts becoming once a week issue. Some facts The settings of that share are set for over 2 years now. Actually all my shares have not been modified (settings wise) for over 2 years. The last two times it happened the folders found on the array are cache-only folders mounted to dockers running sonarr and radarr. Sonarr (move files) Radarr (move files) The last two times it happened, I find only empty folders on the array drive (that belong to the cache-only share). How can I help you help me? And how likely is it that I have some underlying bigger issue? Should I worry about my data?
  14. +1 for Progress bar +1 for a list of what remains to be moved +1 for a list of what it already moved during the session
  15. Hi, I just upgraded my rig from an old A10 to a decent i7 with an Asus Prime with Z390 chipset. Now that I have the fire-power I wanted to play a bit with the VMs. I wanted to passthru the ALC but it's nowhere to be found in the audio devices and then also nowhere to be found in the IOMMU groups. My A10 board also had an ALC sound card (really old one) and it was always there listed. The one shipped with the Asus Prime Z390 is ALC S1220A 8-Channel (which normally should be by default included with the Linux Kernel). Any ideas / clues / hints how to make unraid aware of the audio card?