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.

unRAID Server Release 5.0-beta6a Available

Featured Replies

I have just upgraded too 5b6a from 4.7 final and one of my disks is showing as MBR: unknown. It is a WD 500GB disk that I have been using in Unraid for some time. In fact it is the last 500gb disk I have as I am currently phasing them out.

 

What I assume has happened is that the disk has been using in windows, as an operating system disk or something. Causing irregular entries to the MBR section. As I did not preclear the drive when I added it (8 months ago) as assume that MBR data is still there causing me problems now.

 

What would be my next step? Looking forward to getting this running and enabling my addons and what-not again.

 

Thanks a lot in advance!

  • Replies 349
  • Views 134k
  • Created
  • Last Reply
Oh yes  ;D. Here is my information. I hope it helps.

 

All I can see there is the mbr dump for drive sdb.  That appears to be a 1.5TB drive and the mbr looks perfectly clean - just as unRAID would expect it.

Sorry, didn't change the drive letter.

 

I think this is the one...

root@tower:~# cat /sys/block/sdd/size

2930277168

root@tower:~#

root@tower:~# dd status=noxfer count=1 if=/dev/sdd | od -Ad -t x1

0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

1+0 records in

1+0 records out

*

0000448 00 00 83 00 00 00 3f 00 00 00 f1 7a a8 ae 00 00

0000464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

*

0000496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa

0000512

 

sdd appears to be another 1.5TB, healthy drive.

 

Right this SHOULD be it. Got the drive id from unMenu.

 

 

root@tower:~# cat /sys/block/sdf/size

976773168

root@tower:~# dd status=noxfer count=1 if=/dev/sdf | od -Ad -t x1

0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

1+0 records in

1+0 records out

*

0000432 00 00 00 00 00 00 00 00 89 af 0b 61 00 00 00 00

0000448 00 00 83 00 00 00 3f 00 00 00 f1 5f 38 3a 00 00

0000464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

*

0000496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa

0000512

 

sdd appears to be another 1.5TB, healthy drive.

 

How do I find the right folder for the drive?

type

ls -l /dev/disk/by-id

The disks will be listed by model/serial number with the "device" at the end of each line.

sdd appears to be another 1.5TB, healthy drive.

 

How do I find the right folder for the drive?

type

ls -l /dev/disk/by-id

The disks will be listed by model/serial number with the "device" at the end of each line.

 

Thanks a lot.

 

root@tower:~# cat /sys/block/sdf/size
976773168
root@tower:~# dd status=noxfer count=1 if=/dev/sdf | od -Ad -t x1
0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1+0 records in
1+0 records out
*
0000432 00 00 00 00 00 00 00 00 89 af 0b 61 00 00 00 00
0000448 00 00 83 00 00 00 3f 00 00 00 f1 5f 38 3a 00 00
0000464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
0000496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
0000512

What I assume has happened is that the disk has been using in windows, as an operating system disk or something. Causing irregular entries to the MBR section. As I did not preclear the drive when I added it (8 months ago) as assume that MBR data is still there causing me problems now.

 

and

 

0000432 00 00 00 00 00 00 00 00 89 af 0b 61 00 00 00 00

 

Just so.  Your drive has an ID written in the mbr which was probably put there by windows.

 

If you wish to proceed with unRAID 5.0b6, you can use the mkmbr utility (instructions in the first post of this thread) to 'clean' the mbr.

 

The command you need to issue is:

  mkmbr /dev/sdf 63 0x83

 

which will create a normal unRAID MBR, with partition 1 starting in sector 63

 

I decided to try 5.0-beta6a this week, this is what I experienced.

 

1. All drives detected OK, I had to run the permissions script so that I could access my shares.

2. GUI alignment issues when using Google Chrome Browser.

3. unMenu failed to install packages, I had to install manually

4. Unable to get AirVideo working, I kept getting communications errors.

5. Unable to get my sleep script working, tried changing the sleep command from sleep to state but server would not go to sleep. Not sure if I need to modify any other settings.

 

 

 

 

Is the drive spin down function working in this beta? I can manually hit the button to spin down all drives and the drives spin down as expected and come back up as needed, but are the drives spun down automatically? I have set the default spin down delay to 45 minutes and saved the settings in the web interface, but is there something I am missing?

 

Thanks...

Is the drive spin down function working in this beta? I can manually hit the button to spin down all drives and the drives spin down as expected and come back up as needed, but are the drives spun down automatically? I have set the default spin down delay to 45 minutes and saved the settings in the web interface, but is there something I am missing?

 

Thanks...

 

After an initial problem, before I spun the drives down manually once, all my drives have been spinning up and down automatically for almost 2 months.

also if I use the "fillup" method, what happens if i have a TV show stored on one drvie and upon flowing over to the second drive will in move the entire show folder? or just create another folder and start adding the files to that?

 

unRAID will create a new folder on the second drive.  The original folder will not be affected.  Through disk shares you'll see both folders, through user shares you'll see one big folder or share that contains the contents of both.

 

So now that my UNRAID Norco is now populated with nice clean 1.5TB EARS + 2TB WD Black for Parity. Thanks to the nice Preclear script and using the -D option to get the SMART status info when preclearing drives attached to the BR10i's. I now need to choose an allocation method. If I use High-Water, so for instance, im copying TV shows (a bunch at a time) as the first drive starts to fill to 50% (750GB) and if the next thing is an Episode for a TV Show on Drive 1 will it even if the drive is at 50%, store it on drvie 1 since thats where the original TV Show folder is eg; "Lost" or will it create a new folder on Drive 2 called "Lost" and put the other data there etc? I cannot seem to find anyone else taking about this and I hope that this version 5 may have emprovments on High-Water.

You'll need to play with the split level to achieve what you want.  I can't give you an exact number to use without knowing your file structure (and even then I get it mixed up all the time).  Lionelhutz is the resident split level expert, consult his posts if you have questions about it.

You'll need to play with the split level to achieve what you want.  I can't give you an exact number to use without knowing your file structure (and even then I get it mixed up all the time).  Lionelhutz is the resident split level expert, consult his posts if you have questions about it.

I will be using Split level "0" as i want more control :)

 

I will manually create the structure on  the disks. so I have this.

 

for now il keep this simple. I really just want to know what will happen to data.

 

here is the self created folders that the allocation of high-water will obey

 

Disk01\Media\TV Shows\

Disk02\Media\TV Shows\

 

so lets say I copy "Lost Season 1-5" to

\\Tower\Media\TV Shows\

 

this will create it on Disk01 as Disk01\Media\TV Shows\Lost\

 

now lets say that doing so brought the drive up to 49.9% used of the 1.5TB Disk1. what happens when I go to copy "Lost Season 6" to \\Tower\Media\TV Shows\Lost ??

 

will it see that the show folder already exists on Disk01 (Disk01\Media\TV Shows\Lost) and put it there even if the high-water level has been reached on Disk1 or will it create it on Disk02 like so?

 

"Disk02\Media\TV Shows\Lost\Season 06"

 

with the end result looking like this.

 

"Disk01\Media\TV Shows\Lost\Season 01"

"Disk01\Media\TV Shows\Lost\Season 02"

"Disk01\Media\TV Shows\Lost\Season 03"

"Disk01\Media\TV Shows\Lost\Season 04"

"Disk01\Media\TV Shows\Lost\Season 05"

"Disk02\Media\TV Shows\Lost\Season 06"

 

or will it all live on Disk01 since there is still freespace ?

 

 

I will be using Split level "0" as i want more control :)

 

 

 

Be careful with split level 0. From the manual:

 

If you set the Split level to 0 for a share, then all directories/files created under that share will be on the same disk where the share was originally created.

 

So, I would think it would just keep sending everything for "TV Shows" to disk01 until it fills up and then the copy would fail. If you used Split level 2 in your instance, then TV Shows could live across disks, but not "Lost". All that would be on the same disk. But if you then copied ..\TV Shows\Fringe to the share, and your high level mark was met, it could copy that to Disk02. And all of Fringe would live on Disk02. This is also why I set minimum free space, so as to not fill a drive. If copying to the Lost folder would fill the drive, you could copy it to \\disk02\tv shows\lost\... as an alternative.

 

 

I think I got that right. :)

 

Shawn

Well I thought I would be adventurous tonight and test an upgrade from 4.7 to the 5B6a on my main system. Of my seven assigned drives, 4 show MBR: unknown. <sigh>  Attached is a bunch of info. The first disk, sda, is my parity drive. The other three are data drives. All 4 are attached via Sata ports on the motherboard. Three other data drives, connected via my RocketRaid 2300's are showing the 4k Alligned...

Hopefully someone can help. If you need any other info, let me know!

 

Shawn

 

 

 

Well to update this. I recently swapped over to a new motherboard, so new onboard disk controller. Also, disks got connected to different controllers and disk1 was replaced with a new disk as it failed. I figured I would try the upgrade again and see what happens. Same issue, Parity, disk2 and disk3 (same ones as before) all show MBR: Unknown. I am pretty certain though they are 4k aligned, but what do I know. :) The disk1 though, being a new disk, was ok now. All the other disks in the system show as 4k aligned. Maybe I should just swap those three out over time and re-do the preclear on them...

 

Shawn

 

 

After an initial problem, before I spun the drives down manually once, all my drives have been spinning up and down automatically for almost 2 months.

 

interesting... what problem were you having initially? I can manually spin down the drives and they all stay spun down... but once they spin up due to accessing files, they don't spin down automatically as far as I can tell. Is there some setting that is needed to make it happen? I am using a supermicro atom board with a mix of Samsung 2TB and WD20EARS drives.

 

Thanks...

 

After an initial problem, before I spun the drives down manually once, all my drives have been spinning up and down automatically for almost 2 months.

 

interesting... what problem were you having initially?

 

The initial problem was that spindown wasn't happening at all until I invoked it manually, just once.  Since then it has worked perfectly

 

After an initial problem, before I spun the drives down manually once, all my drives have been spinning up and down automatically for almost 2 months.

 

interesting... what problem were you having initially?

 

The initial problem was that spindown wasn't happening at all until I invoked it manually, just once.  Since then it has worked perfectly

The cache mover for me had the same problem if I remember correctly.  Once I "updated" the setting shit apply, and then kicked it off manually it has been fine since.  I have probably written 50+ GB to the server since then and the mover has been working fine.

I will be using Split level "0" as i want more control :)

 

here is the self created folders that the allocation of high-water will obey

 

Disk01\Media\TV Shows\

Disk02\Media\TV Shows\

 

so lets say I copy "Lost Season 1-5" to

\\Tower\Media\TV Shows\

 

this will create it on Disk01 as Disk01\Media\TV Shows\Lost\

 

Yes, it will use disk1 if the allocation method means that disk1 is the disk which should be used. Then, you now have a "parent" directory "Media\TV Shows\Lost\" on disk1 and any futher writes to Lost will go to disk1, since it already exists and only exists on disk1. The split level will over-ride the allocation method.

 

If you went to disk2 and created a Lost directory then future writes for Lost could go to either disk1 or disk2 and the decision would be based on the allocation method.

 

You could also achieve about the same thing by using a split level of 2 and the include/exclude disks but you would not have to create the parent directory. You seem to have a decent grasp on what split level 0 will do so I think you'd be fine sticking to that. One cool thing about level 0 is that you can have one big media share and not be stuck with a single split level. Creating your own parent structure means that TV could be allowed to split 4 levels deep yet movies only allowed to split 2 levels deep.

 

As you can imagine, forcing whole TV series to stay on a single disk can easily lead to full disks. I would not recommend you use the fill-up allocation method if you want to keep complete TV series on a single disk. The high-water method is OK, but in some cases the most-free might be best since it would start a new series on the most free disk, which should then allow the most room for future seasons.

 

Pulling this out of the 5.0B6 thread into it's own topic would be a really good idea. This split level stuff is not a bug or issue in the release. Keep the topic/section and starting a new thread in mind for your next question.

 

Peter

 

Anyone heard from Tom regarding the MBR: unknown problem? I posted that I had this issue on 5 beta 5a with results of MBR contents. Tried again just then on Beta 6a, all drives still come up with MBR: unknown.

 

 

Anyone heard from Tom regarding the MBR: unknown problem? I posted that I had this issue on 5 beta 5a with results of MBR contents. Tried again just then on Beta 6a, all drives still come up with MBR: unknown.

 

Have you posted diagnostic information, as requested in the first page of this thread?

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.