Koperfild

I already have one in my array, works quite good http://img76.imageshack.us/my.php?image=67055722zk1rf9.jpg Here's the whole topic about my new server case: http://forum.pclab.pl/index.php?showtopic=399202

Here it is: http://pastebin.com/m2c901bdb My answer to the question asked in the topic name is NUT (Network UPS Tools) - a program which controls UPS condition and turns the system of in cases of emergency. It's something similar to that "APC Tools" which are already in bubbaraid, but better configurable and works with uncomparably more ups brands. P.S. Does the bubbaraid automatically apply the "20% read performance hit" trick? If not maybe it would be a good feature...

Ok, what i did was: when the parity-building process was about 10% (under bubbaraid) i decided to break it and roll back to normal unraid. Then i restored the configuration and built the parity another time. What is intressting is that the newest super.dat file is different to the oldest (before playing with bubba). But all disks and data seem to be ok. Today, i tried to install bubbaraid once again and all disks were shown as missing again, so i again rolled back to unraid and everything was ok there. BubbaQ, there must be something wrong in your distro with disks identification. You must fix it to make it safe to use. I attach a syslog from running bubbaraid today: http://rapidshare.com/files/156041764/syslog.rar.html

Yes i was using unraid 4.3.3 i pressed "restore" button without thinking too long about that. I hope i didn't mess the things up When i list directories all the files look to be ok now. Should i stop parity building and uninstall bubbaraid and then boot regular unraid and build the parity once again? would it be safer? P.S. I calculated checksums of both super.dat files. They are different. Very strange...

I've installed the latest bubbaraid (beta 7) and booted the machine up. Then i opened the emhttp (tower:88) and all the disks are red. Emhttp says too many disks bad/missing, but they all are proper for shure. I decided to make a backup of my super.dat file and then pressed "restore" button. Emhttp started to record new parity on my parity disk. What was wrong? Did i do well pressing restore?

Any movements here? I've found a nice tutorial how to set up web interface for rtorrent. It's here: http://code.google.com/p/rtgui/ WeeboTech can you do something about that?

Today the kernel numbered 2.6.27 got relased. Will you update it in the beta3 relase and implement full NFS support, as you mentioned Tom?

What driver updates are you referring to? Actually i only refer to Intel PRO1000 driver update (v0.2.0 in 4.3.3, and v0.3.3 in 4.4b1) but i believe there are much more driver updates. By the way did samba get updated to the latest version - 3.2.4?

Works cool for me. However there are few little errors such as: Sep 29 22:31:18 Tower kernel: system 00:08: iomem range 0xffe80000-0xffefffff could not be reserved Sep 29 22:31:18 Tower kernel: system 00:08: iomem range 0xffc00000-0xffffffff could not be reserved Sep 29 22:31:18 Tower kernel: Couldn't register serial port 0000:00:03.3: -28 My system: Asus P5E-VM Do bios v.0803 Celeron 420 2 x 512mb kingston BQ! SP 450W 3 x HD501LJ, 1 X 7200.11 750GB, 1 X 7200.10 160GB Now, when SMP is supported, and some drivers got updated i'm waiting for security & reliablity improvements and revamping the web panel. P.S. Is it possible to export Fuse shares via NFS on that kernel? Full syslog here:

That's amazing i tried to write a post here: "Yes i'm also very dissappointed because of the lack of the response from limetech. The last unRaid build is very old now and there have been discussed many usefull easy-to-apply tweaks. I would be glad just to be informed that everything goes fine and tommo is working on new relase. Right now it looks for me as if he gave the project up " But i couldn't send it because the internet got disconnected in my school for 15 minutes so i copied the content and decided to post it later and now i've just entered the page and i see a response from tomo Just amazing...

Hey I performed those steps two times trying to install some packages and now I have bzroot and bzroot2 folders on my disk1 that are impossible to be deleted How to delete them?