franohern

You can ignore this. My server wasn't hitting the internet. It was pointing to the address of my old router. Fixed that and everything seems to be working OK. Something really wrong went on during get_categories Post the ENTIRE contents of this message in the Community Applications Support Thread No data was returned. It is probable that another browser session has rebooted your server. Reloading this browser tab will probably fix this error should note that I have indeed reloaded the tab many times and also searched for other instances of browser tabs pointing to the page. This started happening after I moved my server to a new rig.

Was just reading about them in another thread and was looking at how to go about setting them up.

Thanks again. I'll run one more parity check before I go back to taking this server for granted.

The extended smart check on the parity drive returned no errors. So I guess I'm good to go? tower-smart-20201005-0432.zip

I've made the change and have started the extended smart test. I'll report back when I get the results. Thanks for all the help thus far.

So I tried to do this but the only option seemed to be under sata emulation, where my choices were ide or raid. It was set to ide and I left it that way.

My unraid rig (which has been running almost constantly for more years than I can remember,) died recently. It was accidentally unplugged, and the MB would not boot afterwards. I had an old Core2 Duo PC in the attic ( the old box had a celeron in it), and after dealing with a number of issues, was finaly able to boot the server on that box. My old rig consisted of 3 drives, a WD Red 3tb parity drive, a WD Blue data 3tb drive and a WD 750 gig data drive. The 750 was an IDE interface drive (told you it had been running for years) and the new MB didn't have an IDE interface. So I bought a new WD Blue 3tb, placed it in the array, and rebuilt that drive. After the rebuild ended the GUI interface showed 128 errors on the parity drive. My questions are: how big of a problem is this?; do I need to replace the parity drive right away?; and how much does it matter what type of drive I replace it with? I'm thinking I would just get another of the WD Blue drives, but if another drive is more appropriate, I'd like to know that. I mainly use the server for streaming my music collection to my squeezeboxes, but my son wants to set up a VPN on it, and I often contemplate ripping all my blu-ray discs to the server and using it as a media server, although I haven't yet found time to get that project going, and wonder if it is likely that I ever will. Thanks in advance for any advice, Fran tower-diagnostics-20201003-1409.zip

Final Update - and a question. My new nic arrived this afternoon. Popped it in and viola - everything back to normal. Now for the question - while trying to get the box up and running again I tried using a new usb key with a fresh install of 4.7. Being much new, the box booted noticeably faster, plus the new key is a 4gig vs. 512 meg I think on the old one. Are the upgrades in boot speed and memory going to make a big difference for me, especially as unraid moves towards the 5.0 version, and what should I be aware of if I do switch over to the new key? Thanks very much for the help. Makes me less hesitant to attempt upgrades in the future knowing this community has my back.

An update - so I shut down the box, went in to bios, re-enabled the onboard lan, plugged the net cable into the onboard port, rebooted. No lights on the port, not lights on the network switch port I was plugged in to. Shut down, went in to bios and disabled onboard lan, switched the cable back, rebooted, and still no sign of tower anywhere (however I do have lights on the card and the switch.)

Thanks. I will try that.

Actually, I do. The onboard port, which I do have disabled in bios, stopped working a few years back, and that is why I have the second port. I did double check that the onboard was disabled, and re-disabled it just in case. I even tried plugging the network cable into the onboard port, but got no status lights when I did so. Also, I just ordered a new nic, the Intel PWLA8391GT PRO/1000 GT PCI Network Adapter, which should arrive sometime tomorrow. I'm hoping that will solve the problem when I install it, in addition to giving me giga speeds again.

Today I upgraded my basic unraid box from 4.3.x to 4.7. After upgrading I am unable to find my box at all. I type in tower, tower record comes up. I type in the ip address, and I get "the server is taking too long to respond." I hooked up a monitor and keyboard to my box so I could verify that it is booting, which it is, and to capture the syslog, which is attached. I also tried ethtool -i eth0 and was told it could give me no information because eth0 does not exist. Not sure what to do next. Any help would be appreciated. Fran syslog-2011-10-5-1615.txt

Should I upgrade unraid to 4.4 before trying bubbaraid ..0.9 alpha? I've been working with unraid 4.3.3 and buba raid 0.7. thank you for all your help and all the effort you've put into bubbaraid. Fran

Attached find two syslogs, the one calle syslog_unraid boot is from when I boot up by selecting unraid at the boot menu, and the one called syslog_bubbaraidboot is from when I let the machine boot itself into unraid. I hope these provide useful information. Thanks, Fran

the reason I'm swapping back and forth is that I can't get unraid to run properly under bubbaraid. I swap to be sure unraid itself is still working properly. trust me, Once I have the thing up and running properly I don't touch it for months at a time. The problem is I can't get unraid running properly at the same time as bubbaraid. even when I reassign my disks, unraid still tells me that the configuration is not valid. The only option I may have to get unraid up and running properly under bubbaraid would be to do a restore, but I am reluctant to do this with unraid under bubbaraid apparently mis-identifying my drives as scsi drives. the last thing I want is to hose the data on my data drives. Perhaps I'm not understanding what is going one here (perhaps I should drop the modifier perhaps - I don't know what is going on here,) but it seems strange to me that the drives would be identified one way when I boot straight into unraid, and another way when I boot using bubbaraid. Does this make sense to you? Am I over-reacting? Should I just drop this and give up my dream of having one box that runs both unraid and slimserver? Let me know what you think. Thanks, Fran

An update on my travails with BubbaRaid- I finally got to the point where I can get both BubbaRaid and unraid running, but when running unraid under bubbaraid, I get the "too many wrong and/or missing disks!" warning. On the main page for each of the three disks in my array it says Missing in italics, and on the line below lists the serial number of the drive that should be in that position. When I go to the devices page, in the slot for each device it says "ata-ST3706..." listing the rest of the drive's serial number. When I click on the down arrow to show the devices available for that slot, it lists my three drives, but calls them "pci-0000:00:1f.1-scsi-0:0:0:(sda)ata-ST3706..." If I selsect the proper drives into their proper positions and go back to main page it still says "invalid configuration" and won't let me start the array. When I shut down and reboot back to unraid at the boot options menu, when unraid boots I get the "Too many wrong and or missing disks!" warning. But this time when I go to the devices page, the drop down menu lists my disks, but calls them "pci-0000:00:1f.1-ide-0:0:0:0(hda)ata-ST3706..." Here "ide" has replaced "scsi" and "hda" has replaced "sda" in the string. When I select the proper disk into the proper position and go back to the main page it tells me "configuration valid" and allows me to start the array. Everything works properly, as far as I can see. So there you have it. I don't know what this all means, but maybe it will mean something to those of you more versed in the vagaries of operating systems, hardware, and general tinkering around with these things. The mobo for this rig is and ASUS p5pe-vm and the hard drives are seagate 750 gig pata drives (ST3750640A). I f there is any other information that can help diagnose this problem I would be happy to try to supply it. Thanks again, Fran

Yes, I am. I'm in the process of trying again. this time I've wiped my usb stick, reinstalled unraid 4.3.3 and got the system up and running again. Now I'm re-installing bubbaraid to the flash, hoping that starting completely from scratch will clear out whatever gremlins have been giving me these headaches. Will report back later this afternoon. Thanks, Fran

BubbaQ, thanks for your quick reply. I actually figured that out about five minutes after I posted. I'm still not up and running with BubbaRaid. Actually, bubbaraid seems to run fine, its unraid that I can't get going, at least not at the same time as bubbaraid. When I go to network places and look under tower, all I see is the flash, no hard drive, and I can't get to the unraid management page. When I boot unraid at the boot-up screen instead of bubbaraid, unraid loads and runs just fine. I'm still working through the issues. will report back later today with more details when I get a chance to experiment some more. In the mean time, anything that pops up in your mind that might help will be appreciated. Thanks Fran

I'm trying to install bubbaraid on my unraid server. I've extracted the files from the download packeage to the flash, then when I double click on enable_bubba.bat, I get a dos box that says: '\\TOWER\flash' CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory. ***************************************** * FAILURE - BubaRaid not be enabled. * * * * It does not appear that the * * BubbaRaid Zip file was properly * * extracted to the flash because * * there is no \bubba directory on the * * flash. * * * * ReExtract the BubbaRaid ZIP file * * and try again. * * * ***************************************** Press any key to continue . . . I don't know what to do. I've re-extracted the files to the flash a number of times, I've reformatted, re-installed unradi, then extracted the files to the flash again (while unraid is running and the flash drive is in the server) and I still get the same error message. Any help would be appreciated. Thanks, Fran

Just discovered this thread, sounds like just what I've been waiting for. I've upgraded to 4.3.3, and have downloaded the bubbaraid software. But when I went to copy it over to my usb stick, it was too small. So I've ordered a new usb stick, 2 megs, but the question I have is this: when I get the new stick and copy over the unraid software and the bubbaraid software, is there anything I need to do to my unraid array before putting in the new stick? I'm running the unregisterd version with 3 750 gig hard drives. Will it just retsart like nothing happened? Should I copy over the contents of my current usb stick to the new one? Also, do I need to have a monitor hooked up to my server when I boot to choose the bubbaraid option, or is this something that will show up on my unraid home page? Thanks in advance for your help, and for putting together this great package. Fran

Check your local Best Buy. Many of them are clearing out the seagate 750 gig pata drives for less than 60 bucks apiece! I saw a thread on this on Anadtech and checked two of my local BBs yesterday one had a bunch of them for 170, the other had two left, but still at the original price of around 270. Went back to the one with a bunch of them this morning and the sales clerk who did the price check had to call her boss over to verify the 55.99 price. I was afraid I was going to have to argue with them to give me the price, but after he rechecked it I walked out with three. Now I will have a 1.5 tb unraid basic array with the ability to upgrade beyond when the need arises just by purchasing a license key and putting my old 400 gig drives back in.

Tom, Thanks for the help. Everything is running fine now. Fran

I have a 3 disk array using the unlicensed basic version. I'm Currently running version 4.0. The three drives are a seagate 400gig sata (parity), seagate 400 gig pata (disk1), and a WD 160 pata (disk2). I recently took the 160 gig out to use in a new computer build, and tried to replace it with a 120 gig WD pata. Too my surprise, when I went to restart the array, I got the message that the replacement disk is too small and that the replacement disk must be as big or bigger than the original. This hadn't occurred to me before, but now that I think about it it makes sense. Luckily, I had copied all the data from the 160 gig drive over to the 400 gig drive before starting all this, so I'm not completely hosed. I have no intention of putting the 160 gig back in the array, as the new computer is up and running nicely. I guess what I'm looking for here (in the absence of some unlikely secret method of forcing the array to rebuild the data on the 120 gig drive) is what to do next to get the array restarted with the 120 gig drive. The only thing I'm worried about is losing what is on the 400 gig drive. Do I just hit Refresh and the array will format and start using the new 120 gig drive? That seems to me the only logical option, but I want to be sure before I proceed that the data on the 400 gig is not jeopardized. Thanks In advance for your help. Fran

The ethernet port on my P5PE died this week after a number of months but less than a year of service. I bought the board as an open box from newegg and have had no other troubles with it. For now I've just got an old 10/100 card in my rig that I had lying around. It will have to do for a bit. I'm just in the middle of upgrading the rest of the computers in the house, so any new equipment purchases will have to wait until next month. Any suggestions on a reliable, inexpensive, compatible gig-e nic? Thanks, Fran