-
Posts
35 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by tone
-
-
-
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
-
-
+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.
-
Get a windows 10 PC and run chkdsk on the flash drive
-
3 hours ago, trurl said:
This thread is over 3 years old and marked solved, but keep it here now that you have posted in it.
Are you booting from a USB2 port? You should.
Yes, I am using a USB2 port. It is the existing motherboard, flash drive, and same exact port as before (last 18 months).
-
I am experiencing this now and I am unsure how to progress past the suggestions in this post (reformat usb flash).
Details:
- Sever was running fine for the last 18 months
- Did a hardware upgrade (new cpus, case w/backplane) this last weekend and ran into this issue once but a reboot fixed it
- Since then every time I reboot it has this issue. I have left it for 1 hour + with no change
Steps I tried:
- First I backed up my flash drive to my macOS desktop (verified it looked good, size was correct, etc)
- I used the `Unraid USB Creator` on macOS.
- Selected Stable, Unraid 6.8.1 (212 mb)
- Clicked Customize
- Checked Allow UEFI Boot
- Selected my flash drive and Clicked Write
- Replaced the /config folder from my desktop backup
- Tried to boot into unRaid, boot screen shows, tried normal (headless), with GUI, and Safe mode. All had the same result.
I have attached a 2 second video of the hanging.
I have attached a screenshot of the hanging (same as video, just not live).
Also, when I hit Ctrl + Alt + Del on the keyboard it tried to Reboot (SIGTERM), it never actually reboots, it hangs also. I uploaded a pic of that.
Thank you in advance, this is a super bummer for me as I have always had a really clean experience with unraid.
Unraid won't boot - stuck at rsyslogd -i /var/run/rsyslogd.pid
in General Support
Posted
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