- Posts: 20
- Thank you received: 0
myServer RPi won't boot
- LimeyFK
- Topic Author
- Offline
- User
-
Less
More
5 months 3 weeks ago - 5 months 3 weeks ago #4774
by LimeyFK
myServer RPi won't boot was created by LimeyFK
Hello,
I have had my server hardware shut down for the last 4-5 months while I was doing construction in the theater. In the process of putting everything back together, I've discovered that the RPi with myServer6 won't boot.
On startup, I get the following message:
Gave up waiting for root file system device. Common Problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay = (did the system wait long enough)?
-Missing modules (cat/proc/modules; ls /dev)
ALERT! PARTUUID = (b82a2d5-02 does not exist. Dropping to a shell!
From there, I get a series of messages including:
- Timeout while waiting for setup device command"
- usb 2-2: device not accepting address 2, error -62 (or -71)
Ultimately, it lands in a "usb2-port2: unable to enumerate USB devices" message. I tried booting across all 4 usb ports with all peripherals removed with no luck. Is the usb flash drive corrupted? Any advice on how to troubleshoot / proceed from here? If there's any additional information I can provide that would be helpful, please let me know.
Thanks,
Neil
I have had my server hardware shut down for the last 4-5 months while I was doing construction in the theater. In the process of putting everything back together, I've discovered that the RPi with myServer6 won't boot.
On startup, I get the following message:
Gave up waiting for root file system device. Common Problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay = (did the system wait long enough)?
-Missing modules (cat/proc/modules; ls /dev)
ALERT! PARTUUID = (b82a2d5-02 does not exist. Dropping to a shell!
From there, I get a series of messages including:
- Timeout while waiting for setup device command"
- usb 2-2: device not accepting address 2, error -62 (or -71)
Ultimately, it lands in a "usb2-port2: unable to enumerate USB devices" message. I tried booting across all 4 usb ports with all peripherals removed with no luck. Is the usb flash drive corrupted? Any advice on how to troubleshoot / proceed from here? If there's any additional information I can provide that would be helpful, please let me know.
Thanks,
Neil
Last edit: 5 months 3 weeks ago by LimeyFK.
Please Log in to join the conversation.
- David Li
- Offline
- Admin
-
Less
More
- Posts: 1019
- Thank you received: 99
5 months 3 weeks ago #4775
by David Li
Replied by David Li on topic myServer RPi won't boot
Please Log in to join the conversation.
- LimeyFK
- Topic Author
- Offline
- User
-
Less
More
- Posts: 20
- Thank you received: 0
5 months 3 weeks ago - 5 months 3 weeks ago #4778
by LimeyFK
Replied by LimeyFK on topic myServer RPi won't boot
Thanks - I was worried that was the case. The instructions you linked were helpful - looks like I'll be able to get everything off of the old flash drive to avoid having to start from scratch. Do I need to do anything to ensure the license is activated on the new flash drive (other than copy the license file over from the old to the new)? I did use the "restore license" and "restore database" server commands as well.
Edit: I'm mostly back up and running but on the Dashboard I see two issues:
- Teamviewer ID: Unknown
- License Type: Trial
For the latter, do I send an email to info@allonis.com to ask for my license to be transferred to the new flash installation? For the Teamviewer ID, any guidance? The RustDesk ID does populate.
Thanks again!
Neil
Edit: I'm mostly back up and running but on the Dashboard I see two issues:
- Teamviewer ID: Unknown
- License Type: Trial
For the latter, do I send an email to info@allonis.com to ask for my license to be transferred to the new flash installation? For the Teamviewer ID, any guidance? The RustDesk ID does populate.
Thanks again!
Neil
Last edit: 5 months 3 weeks ago by LimeyFK. Reason: Update...
Please Log in to join the conversation.
- LimeyFK
- Topic Author
- Offline
- User
-
Less
More
- Posts: 20
- Thank you received: 0
5 months 2 weeks ago #4798
by LimeyFK
Replied by LimeyFK on topic myServer RPi won't boot
Sharing an update here in case it's helpful for others. Also, if anyone has any ideas on what went wrong / how to avoid something similar in the future, that insight would be incredibly helpful!
As a quick recap, I had a working install / license from mid 2024 until late 2025. I shut down and removed all equipment from my home theater for several months while I finished up the multi-year build. When starting up myServer, the Pi wouldn't successfully boot and it seemed that the USB stick had become corrupted. I had several backups saved on my NAS and followed the instructions in the myServer 6 - Master Image Installation documentation to mount the corrupted USB stick to still access the data. This shortened the recovery time needed once I had a new USB stick installed with the myServer master image to boot from. Everything looked to be going well except for the Dashboard still showing the License Type as "Trial."
Using the backup / restore documentation , I followed the instructions to move over a .bak file for the license from 2024 and then used the server command to restore the license - no luck, still showed as "trial." It was suggested that the license .bak file may have been made before the license was registered / licensed, so I went to the myServer\data folder from the corrupted USB (that was fully working several months ago) and copied the license.json file into the myServer\data folder on the new USB stick (replacing the existing license.json file) thinking that this would then restore the appropriate license to the installation. Unfortunately, that still didn't work and the License Type still shows as "Trial."
I took a look at the .json file and in there it does include "isTrial": false but also includes "isNeedsActivation": true. Regardless, I'm out of ideas on how to troubleshoot further and was informed that I need to pay for the services to migrate licensing from one controller to another (despite this being the same controller / hardware). I paid the fee in order to get this resolved and move on but it still bugs me not knowing why the restore process didn't work for the existing license. I plan on moving to a M.2SSD for greater long-term stability but am a bit hesitant to do so until I know I can successfully restore the license on a new boot drive.
Has anyone successfully used the restore license functionality when migrating to a new boot drive? Any insights into how your process may have been different to mine? If anyone has any other ideas on why it didn't work that they'd be willing to share, I'd love to hear them as well.
As a quick recap, I had a working install / license from mid 2024 until late 2025. I shut down and removed all equipment from my home theater for several months while I finished up the multi-year build. When starting up myServer, the Pi wouldn't successfully boot and it seemed that the USB stick had become corrupted. I had several backups saved on my NAS and followed the instructions in the myServer 6 - Master Image Installation documentation to mount the corrupted USB stick to still access the data. This shortened the recovery time needed once I had a new USB stick installed with the myServer master image to boot from. Everything looked to be going well except for the Dashboard still showing the License Type as "Trial."
Using the backup / restore documentation , I followed the instructions to move over a .bak file for the license from 2024 and then used the server command to restore the license - no luck, still showed as "trial." It was suggested that the license .bak file may have been made before the license was registered / licensed, so I went to the myServer\data folder from the corrupted USB (that was fully working several months ago) and copied the license.json file into the myServer\data folder on the new USB stick (replacing the existing license.json file) thinking that this would then restore the appropriate license to the installation. Unfortunately, that still didn't work and the License Type still shows as "Trial."
I took a look at the .json file and in there it does include "isTrial": false but also includes "isNeedsActivation": true. Regardless, I'm out of ideas on how to troubleshoot further and was informed that I need to pay for the services to migrate licensing from one controller to another (despite this being the same controller / hardware). I paid the fee in order to get this resolved and move on but it still bugs me not knowing why the restore process didn't work for the existing license. I plan on moving to a M.2SSD for greater long-term stability but am a bit hesitant to do so until I know I can successfully restore the license on a new boot drive.
Has anyone successfully used the restore license functionality when migrating to a new boot drive? Any insights into how your process may have been different to mine? If anyone has any other ideas on why it didn't work that they'd be willing to share, I'd love to hear them as well.
Please Log in to join the conversation.
Time to create page: 0.175 seconds