pinion

Just read that there's a New Config option on the Utils page. I assume I should use that?

Cool. So I can just delete the disk.cfg file and when it comes back up ill reassign all the frives like they were and start the array? Or will all my drives be blue dotted then?

So I just upgraded to a pro key and figured while I had the server off and was copying the key over I would upgrade to 5.05. But I accidentally copied over and deleted the config directory. I had an old copy of the usb key from a few months ago so I decided I would just copy the old config directory over. This must have been before I added my most recent drive because everything showed up in the right spot except for the newest 2TB drive and the cache drive. I assigned them but that drive (disk 4) is blue dotted and saying it's a new drive. Now I'm scared to turn on the array. What should I do? EDIT: Actually I can't turn on the array anyway. It wants me to clear that drive. It should have data on it. Everything should be good. Maybe I just need to rebuild parity?

Thanks!

Thanks mrow. I think I'm too late for that because in my haste I did a cp -R of the apps dir in the /user share to the cache drive and then deleted it but when I deleted it it removed everything from the cache drive as well. But that makes sense now how I can still use the cache drive for user shares and set the apps folder to cache drive only. Thanks!

Where does everyone keep their plugin data? I used to keep mine on /mnt/cache/apps. I tried /mnt/cache/.apps but it seems like something wouldn't work right when I did that. Before 5.0rc13 it seemed like that was fine but now all of a sudden all my settings for my apps had reset. And now I have a /mnt/user/apps directory too. Perhaps I screwed up when I enabled use of the cache drive in user shares. I'm not sure. But I was curious how everyone else stores ther plugins data.

I'm getting the same thing with the SOAP error. I'll update this when I figure it out. To be clear I fought thru the stupid simple features bullshit to get that installed. So if you're at that point... well let's continue. At line 980 of /boot/config/simpleFeatures/php.ini Uncomment that line.

I just got the quad core for $319 and it is super super loud. You can count on doing modifications. I have mine in a room in the basement with the door closed and the basement door closed and I can hear it whining through the floor. I took out some of the fans and that helped but even in standby the power supplies are super loud. Another thing is I had to set my bios to safe defaults and then go back and set usb as the first boot device (But this may be optional I was trying to get the network to work). I couldn't get the network to connect. There are two NIC ports on the back and I couldn't get one to work plugged into the wall. Actually there's a nother addon card with a ethernet port but that's for monitoring or whatever and doesn't get you connected. I had to get a powered 8 port switch and plug them into that and then the wall before they came on. While I was trying to figure that out I didn't cleanly shut down and then I think my usb got corrupt. After that it wouldn't poweroff via shutdown and the array wouldn't stop, or at least emhttp wasn't being told it was ready to go. Now I'm kind of screwed because my usb became completely corrupt and my disk1 is corrupt and I don't have a parity for that drive now because I had to rerun parity when I reinstalled to the flash drive (I ran chkdsk but it moved all the contents to lost and found as random filenames). So I'm currently back in my old hardware trying to get it back to working and get my data back. Hopefully my experience with those few things can help out other people getting these And if anyone has any advice about corrupted reiserfs systems feel free to answer them in the thread I've been talking to myself in http://lime-technology.com/forum/index.php?topic=27648.0

Now my entire daggone flash drive was corrupt and chkdsk repair moved every file to lost and found except the 2 smart reports I grabbed before shutting down last time. Holy cow. Now I have no idea what is going to happen. Based on this here thread I should be able to just reinstall onto my flash drive, drop my key in, and go. http://lime-technology.com/forum/index.php?topic=20505.15 So now I'm resyncing parity. Again, attached are the 2 smart reports. SDB was red balled and SDC is currently showing unformatted. On a positive note sdb no longer has a red ball next to it and I'm pretty sure I don't see any issues with it in the smartlog. smart_sdb.txt smart_sdc.txt

I came home to find out that disk 1 is showing unformatted now while disk 3 is still red balled. Which I'm sure is because I ran reiserfsck --rebuild-tree and also probably because when I did that I wasn't in maintenance mode. Had I been in maintenance mode parity would have picked up the changes. So I'm an idiot. Then I realized my flash drive was corrupt which is why I couldn't write the syslog to it. I've taken care of that thanks to a tip from the amazing Joe L in another thread to run chkdsk on it from windows. That looks good so here is my most recent syslog attached. I still don't know where to go from here. I think I will first try to run some smart commands on my disks to make sure they're good. If they are I'll probably start the reiserfsck on md1 again. syslog-20130530.txt

So I just found this and now I'm hoping I didn't hose my system somehow. http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems I still don't really know how to proceed but if I don't here anything on what to do by tonight I"ll report back the steps I'm taking for posterity.

I should also note I'm on 5.0-rc12a. Also when I tried to shut down my array so I could put it into maintenance mode last night it hung but I think since md1 was read only already because of errors it let me go ahead with the reiserfsck. This morning I didn't have any problems getting into maintenance mode after I rebooted.

This is working now. I got a powered switch and plugged both ports in although it seems to work with just one or the other. What didn't work is plugging one of them straight into the wall. Which is weird. But ok... Of course now I'm having a whole host of other problems http://lime-technology.com/forum/index.php?topic=27648.0

I recently picked up one of those super micro 4u servers from Tams and swapped everything over but couldn't get the network to work. I finally got that fixed but then I started having kernel panics. Currently I"m stuck at "Kernel panic - not syncing" <4>REISERFS panic (device md2): journal-003 check journal_end: j_start (2835) is too high This is after I was having problems with md1 so I ran a reiserfsck that told me to rebuild tree so I did. When the system was coming up disk 3 was showing as a red ball although fdisk -l confirmed all my disks were there. I took the array offline to go into maintenance mode and then it showed Parity drive was not there even though when the array was up it had a green ball. After running reiserfsck rebuild tree on md1 it appears that parity is ok in unraid now but when I reran the check on it all sorts of stuff was coming up although I didn't get a chance to finish the check because I need to shut down for this morning for a bit and it was taking too long. Anyway, When I went to take it out of maintenance mode so I could capture syslog because /boot wasn't writeable that is when I had the above kernel panic on md2. So I'm not really sure where to go. Should I just put all these drives back in the old case since everything was working fine then and then try to get back to a working system... or what? I don't really know where to go from here. Attached is the telnet output for the reiserfsck on md1 from last night reiserfsckmd1_rebuild_tree.txt

I wonder if I need to plug them both in although if it were for redundancy you'd think it would still work. I'll look into it more tomorrow night and probably have more questions. Thanks for your help you guys!

And one more thing. The MAC address that's on the sticker spanning the two network ports on the motherboard has the MAC address that eth0 is reporting. Maybe unraid has a problem with H8DME-2 mobo? I doubt that though. I'm probably just not doing something right.

Ok, I have MAC0 LAN0 and MAC1 LAN1 both set to Auto in the bios. The only other option is disabled. I also have IMPI third Lan OPROM which was set to Yes but I've set it to no. And Load Onboard LAN Option Rom which was enabled but I've tried disabling it as well with no luck.

Ok, I'm powering down now. What does it mean if I can see eth0 though on ifconfig with a hardware address?

I'm not sure what you mean by reset the IP setup through BIOS. Mine is currently on for IPMI network etc etc. So should I turn it off?

I don't have anything for en in /dev

I got one of those Supermicro 4U servers from TamSolutions today and it appears everything is working except I can't get it on the network to save my life. There's 2 network ports on the MoBo and there is also an addon card with a network port. The 2 on the motherboard give me no link light and appear to probably be off. The addon gives me link lights but I have no connectivity. I don't see it's mac address showing up on the router ad I can get out from it or get in to it. Anyone else have one of these that can clue me in to what I'm doing wrong? Let me edit this and say that before I was running the server without dhcp. I tried to go into network.cfg and turn dhcp on but then I didn't get an ip at all. Of course I have a static ip now but my router doesn't seem to care.

Mine should be on the doorstep today. Does anyone run esxi on this setup? I was trying to figure it out but it looks like once you install esxi you have to give it harddrives and then it formats them for the data store. So I assume I'd have to have extra hard drives on hand to copy all my current data to the esxi/unraid server. Sounds like a pita so I'll probably just use vmware under my current unraid setup and just put the hdd's in the supermicro server so I can be back up in a short amount of time. I'm also super confused about how unraid can protect the data of the esxi datastore... Say my setup is Parity, disk1, and disk2. So if disk1 fails can I just replace it in esxi and then unraid will do a rebuild? Do I need a separate disk outside my unraid array to hold data for any other VM's I'd want to run? So I guess none of them would be backed up then? But I could probably back them up from esxi to my unraid server right? Basically what I was hoping to do was to install esxi to a spare usb drive, plug in my unraid usb flash drive and get that set up so it's running, then add all my data disks so unraid will see them, and then I'd be back up and running. Is that possible? I know this probably isn't the place to get esxi specific help but I was just hoping one of you was already doing it on this current batch of hardware that jdc posted

It looks like I was probably just running out of memory. Thanks! EDIT: Furthermore it looks like something in my go script was using a crap ton of ram. I went to stock GO and instead of 97 MB free I have 1692 MB free. So I really need to troubleshoot that.

Guess I should have added all the smart reports to one log, I'm sorry. Here are the other 2 logs. smartf.txt

Lately it seems like my server has slowed way down so I was thinking maybe my cache drive went bad because I just threw in an old laptop hdd which I didn't know if it even worked still. I ran hdparm -tT /dev/sdX and noticed that the cache drive jumped all over the place for speed between 500 MBs and 1100 while the others stayed 1000-1100. So I went ahead and copied everything to a brand new 2TB seagate drive that hasn't been added to the array yet and passed preclear. I ran top and noticed I have about 60%wa to upwards of 99%wa which upon googling says it's the system waiting on some io operation to happen before it can continue. I've seen this doing some different tasks but currently I'm scanning my music folder with Subsonic /mnt/user/Media/Music/ which usually takes about a minute and currently it's been running for about 15 minutes and is only a small percentage of the way into it. Maybe I have a drive going bad or maybe the cache drive has something corrupted. I really have no idea how to proceed. So here is my syslog and some smart reports. smarta.txt is my cache drive and smartd.txt is the cache drive. The other 3 are the data drives. Any help is greatly appreciated! smarta.txt smartc.txt smartd.txt smarte.txt