tone

No, just normal. Why?

Thanks for responding @trurl. Tried what you suggest with 6.11.5 and it didn't work. When I tried with 6.9.2 (original OS version) it booted again... Must be something after 6.9.2 with my hardware setup?

I just tried to upgrade again today (albeit to 6.11.5) but same result. I looked and syslinux.cfg had a "-" at the end of it: syslinux.cfg- I tried renaming it as you suggested and booting again. Got a different error this time, no boot still though:

Changed Status to Open Changed Priority to Urgent

I already have it working again from manually reassigning all the devices. After today's fiasco I don't want to take anymore chances experimenting with a working server. Is there a way to check the file contents without fully restoring it?

Thanks for responding. Looking at my previous backup files there is: super.dat (4KB) super.old (4KB) Both look like binary or some human unreadable file. Do you know of a way to view the contents?

After carefully filling in the dropdowns and triple checking I noted a few warning messages: On the two parity drives I saw: "All existing data on this device will be OVERWRITTEN when array is Started" At the bottom near "Start" array I saw: Stopped. Configuration valid. Start will record all disk information, bring the array on-line, and start Parity-Sync. The array will be immediately available, but unprotected until Parity-Sync completes. [] Parity is already valid. Since I luckily did my last parity just a few days ago I am going to check "Parity is already valid.". Might regret this later.. Last checked on Sun 30 Oct 2022 10:34:25 PM PDT (six days ago) --- The array started successfully, all my docker containers were there and auto-started successfully as well! I am going to kick off another parity check just incase. Not sure what to think at the moment but am glad my data is seemingly still intact. A few immediate thoughts: Very glad I had an offsite/cloud USB backup Just checked my config and it happens every 24 hours, this seems OK I am going to donate to Duplicati who was doing my backups I feel that I cannot upgrade to latest and get the updates and security fixes due to these core OS/boot issues While I love the ~7 years I have been using unraid I do feel uncomfortable with unraid as my daily driver for my server given today's issue and previous boot issues I have been having for 3+ years now (see my post history for more, tldr: all rsyslogd.pid hangs during boot) Lastly, I would glad pay for professional help which actually fixed my issues. Not just got me back up and running but identified the root cause and fixed it to prevent it in the future. I mentioned this in the recent survey/poll which went out I don't even know if anyone will read any of this but hopefully this thread helps someone else in the future. Good luck y'all.

Using the CLI on unraid webUI I was able to look through the file contents in /config/ on the USB drive. I found a few interesting files: DISK_ASSIGNMENTS.txt Has all my disks and correctly lined up with where they should be e.g. Disk: disk1 Device: WDC_WD100EMAZ-00WJTA0_XXXXXXXX Status: DISK_OK All disks have "DISK_OK" at the end (for whatever thats worth) The file 1:1 matches my backups (manual and GDrive from 6 days ago) disk.cfg This looks like a config file of 22 disks (1-22) disk.log Nothing much in here, some setting/config (warranty="24") No other files which I went through looked relevant to this issue. Given I want to get my server backup and have no where else to get more experienced help I think I will try to manually (in the UI) assign the drives back to their correct places based on the DISK_ASSIGNMENTS.txt file. Fingers crossed.

Since I was able to boot the unraid web UI I was able to download my Diagnostics.zip and make a manual flash backup (just incase). Attached is the diagnostics if someone who knows what to look for wouldn't mind helping me out (thanks in advance). unraid-diagnostics-20221105-1458.zip

Next I tried restoring from a USB flash drive backup Got the backup files/folders from GDrive Plugged my flash drive into Windows 10 PC Manually selected and deleted all files on the flash drive (did not format) Copied all files over and plugged it in Next I got the below screen and boot was stuck/frozen. I searched google for: "SYSLINUX 6.03 EDD unraid" and there is a mention on these forums of USB2 vs USB3 -- my mobo (GA-7PESH2) only has USB2.0, no problem there. I found a mention of UEFI vs EFI and the folder. I ran the "make_bootable.bat" as admin and replugged in my drive and tried again. It booted successfully. I ran upstairs and logged into the webUI and my heart sank, see screenshot two. Ugh.. Looks like my drive configuration was lost/messed up? This was my absolute nightmare, I don't want my array corrupted. I am going to keep debugging this issue. Need to be extra careful now that my array is in question..

Update: I took out the flash drive and plugged it into a Windows 10 PC, copied the entire contents to the desktop (as an extra backup) Downloaded the Unraid USB Creator and chose Stable/Unraid 6.9.2 Copied the "config" folder over and tried again Same result as before, hanging at the same line. I waited 5 mins before Ctrl+Alt+Del

Following up here. I uninstalled rclone and did a full shutdown (not reboot). One thing to note is that I stopped the array before clicking shutdown to make sure containers had been stopped. That shutdown/restart worked flawlessly, first time in over a year! I will keep playing with it this weekend and try to see if I can reproduce it: - reboot vs shutdown - stopping array before shutdown vs not - having rclone installed vs not

Here are my diagnostics. Thank you! unraid-diagnostics-20211016-1416.zip

Like every morning for the past week. Before I take the dog out I turn on the server and cross my fingers. This morning the server successfully booted up! No changes since last time. Is there something I can enable or do to add extra logging or verbose debug statements during future boot ups? This is still a serious problem. Thanks

Hi all, TLDR: Unraid indefinitely hangs or is stuck during the boot process at this command: I have been plagued with this issue for a while now but finally it boiled over since I cannot successfully boot unraid anymore. It has been days without being able to use my server and I am very frustrated. If you search for this it really does seem like there are many people with the same issue. @limetech is this a larger problem worth investigating? Here is a list of related posts I have found: https://forums.unraid.net/topic/50963-solved-unraid-refuses-to-boot/ https://forums.unraid.net/topic/72755-hang-on-reboot-fine-on-cold-boot/ https://forums.unraid.net/topic/114019-unraid-startup-wont-complete/ https://forums.unraid.net/topic/59506-server-wont-boot-stuck-at-syslogd/ https://forums.unraid.net/topic/88212-boot-stops-in-syslog-on-second-boot-asus-rs720/ Here are a list of things I tried: Put your flash drive in your PC and let it checkdisk (chkdsk [drive] /f /r /x) Plugging flash into PC, make backup of your 'config' folder. Then reformat the usb flash - volume label UNRAID - then copy over release from zip file. Click 'make_bootable' as administrator (don't forget this step), then drag your 'config' file backup to the flash I am pretty desperate at this point and would love any help. Thank you!

So where are you now? Is it fixed?

@DaveDoesStuff Kinda? I have been consistently having this issue for a while now: Not sure if there is something related though

I am getting this exact same thing...

+1 I would love to figure this out. What more can we do?

Nearly everyday my docker image size (20gb total) goes from ~60% usage to 70%+ usage and the alarms start going off (70%). The image size continues to fluctuate (69%, 72%, etc.) so a ton of alarms go off. I believe the "Container" and "Writeable" are growing quickly due to Plex traffic but am not sure that is the only problem and want to understand all my applications a bit more. I am not interested in increasing the docker image size or changing when the alarms go off, I want to understand which applications are consuming the space and why. I have analyzed all my active docker containers and added a max log setting where applicable, when the log became large (>50mb), so I don't believe runaway logs are the problem: --log-opt max-size=50m --log-opt max-file=1 I know I can get a current snapshot of my docker usage by clicking the "Container Size" button on the /Docker page but that is only a current snapshot and it isn't fast enough or historical. I was thinking about collecting this data and placing it into a time series DB (InfluxDB or Prometheus) and graphing it (Grafana). I am most familiar with Prometheus but am not sure how to collect the data from: /mnt/user/system/docker/docker.img Any tips? Is this the best way to get this information/solve this problem? Has this been done before? Thanks!

Following up on my previous post. First thing I did was to plug the flash drive into a Windows 10 PC, I ran chkdsk d: /f /r /x and it resulted in 0 errors. Next, I had an idea, try formatting the flash drive using the Windows 10 machine. I figured there could be an issue isolated with macOS. Downloaded Unraid USB Creator Win32 and reset the drive. I did not add my /config folder back. It booted up quickly to `Tower login:`. I was able to browse to my server IP via another computers web browser and saw it as an unregistered copy of unraid. So far so good! I have eliminated physical problems with the machine and the USB flash drive. Next I wanted to add the /config folder back to the drive but via the Windows 10 PC. Unraid booted up fine, it got past the rsyslogd.pid step. So I am still a bit confused as to the root cause. Potential culprits: - macOS formatting might have an issue - Copying /config from a macOS might have an issue - Other? I never did a memtest but will kick one off later this week.

Tonight I will try: Get a windows 10 PC and run chkdsk on the flash drive This will determine if something is wrong physically or logically with the flash drive Try a brand new flash drive and clean copy of unraid (without my existing /config file) This will determine if something is wrong with the server's hardware (mobo, cpu, ram, usb port, etc.) Install a clean/new copy of unraid on a new flash drive and then move my /config folder over (I will need to move my license if this works, nbd) Also, LMK if I should start a new thread for this, not trying to hijack and existing thread but it is the same issue.

Yes, I am using a USB2 port. It is the existing motherboard, flash drive, and same exact port as before (last 18 months).