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

...

 

Chris what kind of unraid_notify script is that? Not "bubbaRAID's stock"?

 

Because my unraid_notify script is just 86 lines and doesn't need anything in the go script since bubbaRAID initializes it itself.

 

 

  • Replies 929
  • Views 234.1k
  • Created
  • Last Reply
  • Author
bubbaraid go script

 

And just what file do you think that is?

  • Author

bubbaraid-0.01.15-Beta is posted

 

Link is in OP

 

New in this version:

- fixed the issue with some mobos with ICH chips

- /boot/config/go2 script support (see below)

 

Some people were editing BubbaRaid’s startup scripts – this is not a good idea since new versions of BubbaRaid will overwrite them and wipe out your changes.  So I added a feature for a second “go” script (/boot/config/go2) that will be run AFTER all of the BubbaRaid applications start up.  This is so you can put your own startup commands in a script that BubbaRaid will not overwrite in future versions.

 

So the boot process is now:

 

- boot Linux

- /etc/rc/d/rc.startup (core system startup, and calls the following scripts)

- /boot/config/go (loads emhttp)

- /boot/bubba/rc.bubba (starts BubbaRaid apps – users should not edit this file)

- /boot/config/go2

 

Once this new build get's tested, I'll start adding new apps again (i.e. llink).

 

I am going to make a slight architecture change in the next major version of BubbaRaid.  The lighttpd config directory will be split out from the /boot/bubba/ directory structure to a stand-alone location on the flash in /boot/config/lighttpd.

 

BubbaRaid will still continue to have lighttpd built into it, but I will also have a stand-alone add-in package for Lighttpd that anyone can use to add lighttpd to an unRAID server with a static config file.

.15 is no go for me man.

Same known error.

Only difference I see is that AFTER the ata4.00 errors and the "not found" errors, I get some info on ata4.01 being configured for UDMA/100 and that EH is complete for ata4... but still no prompt yet as usual. In older releases I didn't get the "not found" errors over ata4.01 messages, but below... if this means anything.

 

Reverting to .11.

 

...ah and it goes on! (this is definitely different than .11)

 

Even after I issued "shutdown now" I get messages from the system that ata4.00 is already in PIO0 mode (YIKES!!!) and ata4.01 (that I don't remember having a problem with older versions) is also going down... until this also reached PIO0 mode!

 

I can say this is the worse 0.01 release for my mobo up to now. :D

 

 

  • Author

Well that narrows it down to the I2C modules.  Build 01.16 will be posted soon.  Strange, that they were not enabled in stock unRAID .config file... they must have been built separately.

 

 

  • Author

OK... 0.01.16 is now posted.  I2C modules are now built into the initramfs.

 

Link is in OP.

OK... 0.01.16 is now posted.  I2C modules are now built into the initramfs.

 

Link is in OP.

 

I tried the upgrade and it did not do anything.  The download says it started, but does not progress at all.

 

I'm now downloading the full release, can I just install the full build over the top?

 

thanks,

dave

 

EDIT:  OK I see the -Upgrade file is not there. I"m just doing a full install.

 

I completed the upgrade and still see the same issue.

 

No IDE from the motherboard.  It is loading the ata_piix driver and setting them as sd* drives.

 

dave

No go for me too.

Same thing as always.

 

(btw, irrelevant, but you should consider some messaging solution for more live and thus quicker, interaction bubba)

 

  • Author

OK.  Back to drawing board.

Sure you don't need extra data from us?

I hope syslog contains all the info needed.

 

BTW I just replaced bu_root from .11 and I am fine (and in fact if your current beta updates are just bu-root, let us know so we don't re-replace everything else for no reason).

 

 

 

  • Author
Sure you don't need extra data from us?

 

Yes, I am sure.

thanks for working on this.

 

I can test whenever you need.

 

Is there any way I can use the perl installed with bubbaraid on my stock unraid?

 

thanks,

dave

Even after I issued "shutdown now" I get messages from the system that ata4.00 is already in PIO0 mode (YIKES!!!) and ata4.01 (that I don't remember having a problem with older versions) is also going down... until this also reached PIO0 mode!

 

No, this is exactly the same behavior you had in the syslog I looked at, and probably in each version since the one that worked for you.  ata4 is being handled similar to an IDE channel of 2 drives (ata4.00 and ata4.01), so problems on one drive result in resets to the channel which affect both drives.  In this case, the disabled IRQ causes communication failures to each of the drives, so it keeps slowing them down, hoping to resume good communications, until it bottoms out at PIO0.

 

A suggestion, do you have AHCI available in the BIOS?  If so, that will cause different drivers to be associated with those drives, AND avoid the common channel problem for pairs of drives.  Another suggestion, try the irqpoll boot option, at least to see what difference it makes.

Well I know irqpoll *WAS* needed with older unRAID versions but was not needed in later ones (maybe last couple or three).

 

Remember with my current setup (current BIOS setup etc.) my plain unRAID works fine.

 

Thank you for your suggestions but since bubba is in the middle of debuging the thing I will follow what he needs me to do next. After all I am back to .11 and working. If a new beta comes along (so I do the whole "shutdown-remove-insert on other machine-remove-boot and watch" drill again), I'll probably try your two suggestions too.

 

  • Author

OK.  One more time..... Version 0.01.17 is now posted.

 

Link is in OP.

YES!!

 

I'm up and running BubbaRaid!!

 

Whatever you changed on this one fixed it for me.

 

thanks,

dave

 

OK.  One more time..... Version 0.01.17 is now posted.

 

Link is in OP.

  • Author

Good.  I don't want to jinx it, so I'll wait on some other successes.... but you won't believe what was causing this.

Quick question.  When I go to the UnRaid tower:88 page, I no longer see the spin down, reboot or shutdown buttons.

 

Ideas?

 

thanks,

dave

Now that is work for me  ;D

 

I'd like to ask for some additional perl packages:

 

IO::Socket

Net::Pcap

NetPacket::Ethernet

NetPacket::IP

NetPacket::TCP

NetPacket::UDP

Unicode::String

Proc::Daemon

Proc::Simple

Unix::Syslog

 

 

I think Unix::Syslog may be there already along with IO::Socket, but not the others.

 

I tried to install them via CPAN, but you have to have a compiler/make yada yada to do that.  Is there a place that I can download the .pm files already compiled for Slackware?

 

thanks,

dave

I think Bubba was waiting for me.

And *I think* we can go forward now. :)

 

 

Quick question.  When I go to the UnRaid tower:88 page, I no longer see the spin down, reboot or shutdown buttons.

 

Ideas?

 

thanks,

dave

 

Nevermind on this. I got up this AM, hit refresh and the buttons appeared.  Not sure what was up, but it all looks good now.

 

dave

  • Author

It was a bad ram stick in my development machine.

 

...downloading the latest Memtest+.....

 

;D

 

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.