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.

What do you want in a custom unRAID package (BubbaRaid)

Featured Replies

  • Author

@NLS:  You are not on any list, but I have no idea what is up with your system. I've tested the new install on multiple systems and flashes, and it works fine.

 

Make a new test flash.... Take a new flash, put unRAID 4.4.2 on it, and then BubbaRaid 0.01.01.  No need to add or configure any unRAID drives.... just see if it boots.

  • Replies 929
  • Views 234.1k
  • Created
  • Last Reply

Not very easy to do this now.

After all unRAID and the stick was ok before the upgrade.

I'll do an offline install of bubbaraid 0.01.01 and we'll see what happens.

 

 

...offline install does the same.

 

I've noticed that as the system (not BIOS) scans disks to mount, takes too much time and produces several errors.

In fact I haven't got the login prompt YET (after the three errors reported in a post I made above)... and the disk LED is fully lit (probably something is trying to happen).

 

So I cannot check if plain unRAID boots ok (I suspect it DOES).

This has happened before in an bubba upgrade (I don't remember which or how I recovered)...

 

Is there any way to grab that whole output to send it for evaluation?

 

I am very sad right now and want the previous version back. :( HELP!

 

I don't have a working system at all. :(

 

 

...indeed loading plain unRAID (from boot menu from same stick etc.), boots the system normally.

 

Something smells bad in bubbaRAID upgrade front.

 

I'll clean all folders related to bubbaRAID in stick and drop it over again... do I need 0.0.18 first?

 

(btw nobody bothered to answer which files to keep from my old setup, either...)

 

 

...offline install does the same.

 

I've noticed that as the system (not BIOS) scans disks to mount, takes too much time and produces several errors.

In fact I haven't got the login prompt YET (after the three errors reported in a post I made above)... and the disk LED is fully lit (probably something is trying to happen).

 

So I cannot check if plain unRAID boots ok (I suspect it DOES).

This has happened before in an bubba upgrade (I don't remember which or how I recovered)...

 

Is there any way to grab that whole output to send it for evaluation?

 

I am very sad right now and want the previous version back. :( HELP!

 

I don't have a working system at all. :(

 

Why can you not boot regular unraid?  Even if you do not have a monitor hooked up to the system you can take the flash out, plug it into a PC and run the disable BubbaRaid.  From there just plug the thumb drive back in and you should be booting to regular UnRaid.

 

 

This should also be a lesson in backup up the flash drive.  I ALWAYS make a .zip of the contents of the flash before i do something like this.  That way if something happens I can unzip the contents back onto the flash.

 

EDIT: never mind i see you have got regular unRaid working.

I said I CAN boot regular unRAID. I didn't say I cannot.

 

Yet the additional functionality of bubbaRAID is now "needed" functionality.

 

I don't have a full zip, but I have a copy of all the files I have modified.

 

The problem is what is wrong with bubbaRAID that web-upgrade didn't work (stopped all services except web server before that) and even offline upgrade doesn't work either.

 

Isn't it something worth checking out?

 

 

  • Author

@NLS.  I can't help you if you don't follow instructions.

 

I said:

 

Make a new test flash.... Take a new flash, put unRAID 4.4.2 on it, and then BubbaRaid 0.01.01.  No need to add or configure any unRAID drives.... just see if it Bubba boots and you get the apps.

 

Do not copy ANYTHING from the old flash.  You are making a CLEAN new flash for test purposes.

ok will get back to you later - thanks

 

 

OK did what you asked.

 

Clean unRAID, 0.01.01 on top, start_bubba (or how you call it).

Even used latest syslinux.

 

From the old setup I only kept basic cfg files in config folder (where my disk assignments are, my IP, DNS and such - NOTHING that should affect bubbaRAID).

 

First selected to boot unRAID (to see if everything was ok). It didn't start the array automaticaly of course because it was asking me if I trust it. So I started it invalidating the parity (which I stopped and will let it build later).

 

Rebooted using unRAID web interface and let it boot in bubbaRAID mode.

 

EXACTLY same situation. VERY long boot (after loading the images), taking much time in most of my disks (and with timeout and various other errors), and in the end the three errors I posted way above... and again login string, nowhere to be seen (judging from previously, it will come up, but probably in 10+ minutes) and my HD light all light up.

 

/mnt is empty and /boot is empty.

 

Now I don't know how you call this, but I call this bubba issue. :) Sorry but to my (limited? I am only 25 years in computing) debugging radar, this looks like something new in 0.01.01 that doesn't like something in my system.

 

I hope you are interested in debugging this, because I am interested in helping you do it (i.e. help you help me).

 

Else let me know so I get back to .18 -> .21.2.

 

  • Author

Send me a syslog, and go back to .18 or .21 while I work on it.

  • Author

Also, send me the output from "lsmod" and "lspci" with a working boot of unRAID on that mobo.

ok will send to your email

 

hope (offline) overwriting .18 and then .21.2 over 0.01.01 is good enough to get me going for now

 

"a working boot of unRAID" you mean let it boot in unRAID mode and send you those outputs?

 

want the same from "bubbaRAID" mode for comparison?

 

hopefully those are commands INCLUDED in unRAID

...btw /boot is EMPTY so I don't think it is my stick (so I don't think I can save it somewhere where we can use it)

 

any other idea? (some way to mount the stick?)

 

NEWS:

 

Indeed boot is NOT my stick (I dropped the files there and saw they were in /boot - empty from any other entry - and then shutdown and in my windows I don't see the files among my other stick files...).

 

I even tried to mount a few of my disks (sda1, sdj1 etc.) and says for all that "special device sdwhatever does not exist"...

 

finally lsmod is there but lspci is not... (note I don't have any PCI card except if anything on the mobo enumerates as PCI)

 

---

 

So... you think there is any way to actually see my stick from the failed bubbaRAID and get the files you need on it?

 

 

  • Author
"a working boot of unRAID" you mean let it boot in unRAID mode and send you those outputs?

 

Yes.

 

want the same from "bubbaRAID" mode for comparison?

 

No.

 

lsmod is in stock unRAID, lspci is not. and lspci has nothing to do with PCI cards installed.

 

Stop trying to boot BubbaRaid 0.01.01... obviously there is a disk controller module issue with your mobo, since several others are running 0.01.01 just fine.  Just send me the lsmod and syslog from a normal stock unRAID boot on that mobo, so I can see what drivers are loading.

ah ok though you wanted syslog from bubbaraid

(in fact you did: "Send me a syslog, and go back to .18 or .21 while I work on it.")

 

sending in 5

 

EDIT: sent

 

thank you

 

I'll stay in plain unRAID for the day in case you find the issue (and for my parity to build).

 

  • Author

BubbaRaid version 0.01.02 is now posted.  You can use the upgrade link in BubbaRaid, or the link in the OP to install manually.

 

Apparently, 0.01.01 had some modules that didn’t link properly, so it did not work on some controllers.  This should fix it.

 

This one also shaves about 10MB off the file size of the initramfs.

 

It also improves the sound support.  To enable sound, run:

 

  /boot/bubba/sound/start

 

I'm still looking for feedback on the sound support working or not.

BubbaRaid version 0.01.02 is now posted.  You can use the upgrade link in BubbaRaid, or the link in the OP to install manually.

 

Apparently, 0.01.01 had some modules that didn’t link properly, so it did not work on some controllers.  This should fix it.

 

This one also shaves about 10MB off the file size of the initramfs.

 

It also improves the sound support.  To enable sound, run:

 

   /boot/bubba/sound/start

 

I'm still looking for feedback on the sound support working or not.

 

I don't have my speaker install but i will work on it so that i can give you some feedback.  Just out of curiosity, what exactly does the sound support do/add?

  • Author

mpg321 is included as a mp3 player, and it will play over the soundcard output in the server.

 

When you run the start script, it will play a mp3 file at the end to test it.

 

There are several media server packages that can make use of this ability.

mpg321 is included as a mp3 player, and it will play over the soundcard output in the server.

 

When you run the start script, it will play a mp3 file at the end to test it.

 

There are several media server packages that can make use of this ability.

 

OK, thanks for the info.  I will hopefully get to mess with the server sometime this week (after my college midterms are over) and I will report back on results.

 

- Added socat for secure login support for e-mail notify scripts

- Fixed bug in the autostart checkboxes on individual edit pages

 

Wow that was fast!  Thanks!  Will try it out and report back!

OK .02 is the same for me (i.e. not working).

 

Seems that problem start when it reaches ATA4 (sdf) and starts slowing it down (trying UDMA/66, /33, PIO4 etc.).

Then it reaches the same three errors (can't even see UNRAID stick!) and gets 10-15 minutes to get to login prompt after that!

 

No "merge" with UNRAID system takes place, so no web, no shares, not even an IP.

 

We really need to find a way to send you THAT syslog.

 

Tell me how to make it mount the flash drive back, so we can send log files there. Else I don't think we'll find it.

I *do* remember this happening in some past beta and then you fixed something. I'll look our email history.

 

PS. If it all happens for a disk (which disk works fine and is green and usable in unRAID btw), still system shouldn't deteriorate like this.

 

 

HA HAVE SOME LOG SUCCESS!!!

 

I've noticed that sdf never got in the dev list and then did visit /dev/disk/by-label and although during bubba boot it reports that UNRAID doesn't exist, IT DOES!

 

SO I MOUNTED it and sure enough it IS my stick!

 

So in the mail I have the syslog/lsmod/lspci outputs!

 

Maybe now we can really progress.

 

 

I hope I can step to 0.01 too.

Anybody having problems with this beta?

 

 

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.