Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Problem to upgrade to test release

Featured Replies

We own two 15-drive LimeTech systems. One is a recent MD-1510/LL. The other one is an older MD-1500/LL (?).

 

An upgrade of the newer MD-1510/LL to 4.5.3-TEST didn't show any problems.

 

The older one is not upgradeable. It always stops during load of the two bz* files at the end of the last shown dot.

 

I tried this 4 times:

 

- Format stick

- syslinux -ma e:

- copy files with older bz* files or newer bz* files

- reboot

 

Whenever I use the 4.5.3-TEST files the boot hangs.

 

The bz* files are the same I used on the new LimeTech machine. There they work.

 

Any ideas? I know, there should not be no difference but for one of the systems they seem to be different.

 

Regards

Harald

 

We own two 15-drive LimeTech systems. One is a recent MD-1510/LL. The other one is an older MD-1500/LL (?).

 

An upgrade of the newer MD-1510/LL to 4.5.3-TEST didn't show any problems.

 

The older one is not upgradeable. It always stops during load of the two bz* files at the end of the last shown dot.

 

I tried this 4 times:

 

- Format stick

- syslinux -ma e:

- copy files with older bz* files or newer bz* files

- reboot

 

Whenever I use the 4.5.3-TEST files the boot hangs.

 

The bz* files are the same I used on the new LimeTech machine. There they work.

 

Any ideas? I know, there should not be no difference but for one of the systems they seem to be different.

 

Regards

Harald

 

To upgrade you only needed to copy the two files (bzroot and bzimage) to the drive and reboot.  You did far more than needed.

 

Usually, in other cases like this, a newer version of syslinx was needed.

 

Also, don't forget to set the volume label of the drive to UNRAID

  • Author

Thanks Joe,

 

I did everything - it's not my first upgrade ;-)

 

Label UNRAID is set. The previous release is 4.5.3 and the latest syslinux tool is used. Copied just the two files. Whenever the two TEST bz* image files are involved the system refuses to boot. It took me two complete resync (because I do not have keyboard/monitor attached to the systems) until I found out that it's only the new bz* image that makes the difference.

 

I even tried the working stick from the running system. If the TEST files are in use the new system boots but the old system hangs. It's a m%stery.

 

Thanks

Harald

 

Thanks Joe,

 

I did everything - it's not my first upgrade ;-)

 

Label UNRAID is set. The previous release is 4.5.3 and the latest syslinux tool is used. Copied just the two files. Whenever the two TEST bz* image files are involved the system refuses to boot. It took me two complete resync (because I do not have keyboard/monitor attached to the systems) until I found out that it's only the new bz* image that makes the difference.

 

I even tried the working stick from the running system. If the TEST files are in use the new system boots but the old system hangs. It's a m%stery.

 

Thanks

Harald

 

Sounds like a mystery to me as well...

On some BIOS it makes a difference if you use FAT vs. FAT32 when you format.  On others, the geometry of the drive matters.

 

Joe L.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.