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.

[solved] problem starting up array after changing cases

Featured Replies

edit 11/05/12

I forgot to mention that I'm using the unRAID Server Plus ver 4.7

end edit

 

I recently transferred my array into a new case and discovered that I was unable to start up my array. I was fortunate enough to come up with a solution so I thought I would share my finding in case others experience this same problem.

 

When I transferred my array, I was negligent in marking which drive was which so when I tried to start up the array after the transfer, I had to rearrange the drives into their proper arrangement. After I had everything set, the main menu asked me to press start to bring the array online. After doing so, I waited 10 minutes before refreshing the page and the page came back with the same menu. (i.e. Press start to bring the array back online.)

 

I figured I hadn't waited long enough so I pressed the start button and waited 1 hour. After doing so, the menu came back asking me to press start to bring the array back online. I figured my 5 drive array would take longer so I pressed start and waited. This time I waited longer than 24 hours.  When I returned, the page asked me to press start to bring the array back online.

 

That was when I decided to do something else. I un-assigned the last drive in my array and pressed the start button. It warned me that pressing start would bring the array online BUT without protection. I pressed start anyway. After waiting around 5 minutes, I refreshed the page. The array was online but unprotected. But the array was started.

 

So I stopped the array, re-assigned the last drive in the array, and re-started the array. After waiting 10 minutes, I refreshed the menu page. (Hit F5 on the keyboard.) This time the message read that the array was rebuilding and I had to wait 90 minutes for the array to be rebuilt. THIS was different from the previous times as the previous attempts just asked for me to press start to bring the array online.

 

After waiting the 90 minutes, the array was online. So the moral to my story is if re-starting the array takes too long, un-assign the last drive in the array, bring the array online. Once the array is online but unprotected, stop the array. Re-assign the last drive in the array. Then re-start the array. If you've done it correctly, refresh the page and it will tell you to wait xx minutes. After waiting those xx minutes, your array should be started.

 

I hope this doesn't happen to anyone else but if it does, I hope this helps.

 

Day

 

edit 11/05/12

I forgot to add that in the move I busted connection point of the last disk in the array and had to reconnect it to another port on my raid card. This was probably the origin of the problem in starting up the array.

end edit

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.