master.h

I believe it's a hardware issue, however I'm not sure what's going on. My backup server is usually powered off unless I am rsync'ing a bunch of data over to it. About half the time, the server won't boot up properly unless I remove the flash drive and rebuild it in Windows (I just copy everything to the desktop, format drive, re-copy files/folders, and run make_bootable.bat). Everything works great after that. Sometimes, the server will not allow me to rsync all my files over (it stops rsync with errors on the console about stale file handles). Hardware specs are in my signature for system name "Saidar." The flash drive I have was one purchased from Tom. I've never seen any error messages about flash drive errors when plugging the flash drive into the system, either. Not sure why rebuilding it causes things to work OK for awhile. I've ran memtest for about 6 hours, with no issues reported. Also, I just powered on my server and manually started a parity-check, and emhttp crapped out. I can't access the standard webGUI (I have Tom's new webGUI installed, but it was from a plg that was released awhile ago, webGui-latest.plg). I do have unmenu installed, and I am able to access that. Below are the most recent syslogs I have (the one named -Current is the one pulled from unmenu while the system is running with emhttp down), hopefully someone can give me an idea. https://www.dropbox.com/s/sdtl2fj5t9yzif1/syslog_2014-02-27_21.15.11.txt https://www.dropbox.com/s/oghof11hghaj5rf/syslog_2014-02-27_21.20.35.txt https://www.dropbox.com/s/jxd45m4acjuvap2/syslog_2014-03-01_01.34.58.txt https://www.dropbox.com/s/n45ibg9imd2bxov/syslog-2014-03-01-Current.txt

Ah, I understand now. I didn't have time to mess with anything yesterday, so today I signed in to vSphere and took a look at the nics. Turns out by default unraid/plop vm was using the e1000 nic, but it still wasn't working right. I tried changing to the vmxnet3 type vnic, but still no good. I got the loopback entry only. I'm sure the underlying cause is my hardware, same as the purple screen when passing through a PCI nic. I did order a PCIe NIC though, and it came in today (thank you newegg premiere!). I was able to pass that through successfully. It's the Intel EXPI9301CTBLK from here: http://www.newegg.com/Product/Product.aspx?Item=N82E16833106033. So my current hardware setup is working, just had to finagle it around a bit. Thanks for the input/advice everyone.

I guess I don't understand the question... after the initial ESXi install, everything was already set up. I didn't configure any network settings (aside from assigning a static IP on the ESXi console). I didn't change any network settings in vSphere client. All the VMs I created were assigned to the same vnic (by default called VM Network). It's entirely possible I'm misusing the term vnic. To be honest, since the Windows 7 and Turnkey Linux VMs were working fine, I never looked at the host network configuration in vSphere. I was focused on passing through the PCI nic last night. I'm at work now, so I don't have access to my system at home, but I am going to go home for lunch today. I'll take a look while I'm there.

Before I bought the nic (Intel Pro/1000), the unraid VM did not recognize the vnic. I had two other VMs, Windows 7 and MineOS Turnkey (minecraft server), and both saw the vnic just fine, worked with no issues. Even though unraid/plop was set to use the same vnic, unraid just didn't see it. If I sign in to the console and run ifconfig, it only reports a local loopback IP. If I run ifconfig eth0, it returns "device not found" or something similar, don't remember exact error. Mobo: Asus P7P55D-E Pro, CPU: Intel i7-860. I am passing through a controller, but it's a Perc H310. It's passed through with no issues. Once I pass through the controller and boot up the unraid VM, I can console in and I do see all 8 of my disks and the data is all there. I did notice that, and did turn it on. In fact, I turned it on for kicks whenever I first got the board years ago. I double and triple checked last night as well; it's still on.

I've got unraid up and running as a VM in esxi 5.x (I've tried 5.0, 5.1, and 5.1 with patch ESXi510-201310001 installed). Every single time I try to start a VM (doesn't matter which) with the NIC attached, it PSODS. VM never boots. I have unraid loading using the plop method, if that matters. I tried ESXi 5.5, it doesn't recognize either my onboard or PCI nic. I have not tried any 4.x versions yet. I would greatly appreciate any advice. My hardware setup is in my signature. Let me know if I need to add more info, or if this was posted in the wrong forum. I've been trying to figure this out for the past 4 hours, and I'm at my wits end.

I wasn't able to flash any of the firmware in the toolset you posted the first time through. I ended up cobbling together my own thing and flashing the Dell HBA IT firmware. I only tried the P16 this time. Will try the other two in your toolset and see if I can find the P17 firmware as well.

master.h, can you give more details, where my instructions failed? So it's been quite awhile, but I just got around to trying to flash another H310. Fireball, I ran into the same issue this time as I did last time. Everything goes swimmingly up until Step #14 (which you have labeled as Step 5.3 to flash the P16 IT-firmware). I get an error message Firmware Returned Exception. IOCStatus=0x25, IOCLogInfo=0x0. Due to error remaining commands will not be executed. Unable to Process Commands. Exiting SAS2Flash. Here is a link to a picture of the error: https://www.dropbox.com/s/ucbcoj66ii44p1p/2014-02-14%2013.42.49.jpg Here is a picture of the controller itself. It came brand new from a Dell T3500 or something similar, never been used: https://www.dropbox.com/s/54n8dfqzc8qlk46/2014-02-14%2013.43.15.jpg Also, your instructions indicate that the SAS address will look like 500605bxxxxxxxxx. Mine does not look like that, according to the text file that's output in 1.bat.

I've purchased a Pro and a Plus license. Which one would I get if I signed up for another key?

Sorry for the very delayed response, I've not been browsing the forums very much. I haven't noticed any side effects, my server has been running solid ever since I've installed the h310.

I'm terrible at coding, but if I remember correctly, .h is a C++ helper file right? LOL can't tell if you're making fun of me or not...

OK, I definitely have some things to try/test. My friend picked up the server today (I made sure to tell him that these were issues that we still need to work on). He lives about 45 minutes away, so it'll take some time for us to work everything out. Thanks for your advice; I'll post back here with any updates.

I just put together a rig for my friend, and am seeing the weirdest issue ever. The server will boot up and run fine one time. If I power it down through the webgui (or using the poweroff command from putty/console), the server will freeze while loading bzroot. The dots go across the screen then stop and has a blinking underscore ( _ ) and just sits there. No matter how long it sits there, never finishes loading bzroot. Have to hold the power button to shut it down. Doesn't always have the same amount of dots, either. Sometimes it freezes fairly close to the beginning, other times freezes when it's the middle. The only way to get the server to boot again is to put the flash drive in my computer (Windows 8.1 Pro), copy all the data off the USB, format it, copy all the data back, and run make_bootable. System boots without a hitch. Power it down, it freezes when loading bzroot. All like clockwork. I've got a syslog attached from the keeplogs.sh script, but I didn't see anything weird in there. I have not ran a memtest or anything like that, as the system boots 100% fine as long as I have just formatted the USB. Wouldn't think RAM had anything to do with that. Anyone have any ideas? System specs: 4x1GB RAM ASUS P5B-VM DO Intel Core 2 Duo Unraid 5.0 Pro 2TB Parity, 2TB disk1, 1TB disk2, 250GB disk3, 160GB disk4, 160GB cache No plugins except the keeplogs.sh (not even unmenu or new webgui) syslog_2013-11-08_01.29.09.txt

To anyone else who has this issue, here's what I did: 1. Cloned the problem drive to a spare using DD dd if=/dev/sda1 of=/dev/sdb1 bs=1M conv=notrunc,noerror where /sda1 and /sdb1 are correct for my system 2. reiserfsck --rebuild-sb, with the correct answer as found in bjp99's post: 1. The version of reiserfs is 3.6.x. This is for unRAID 4.2.1. (This is NOT the default, so be careful) 2. Block size is 4096 (default) 3. “No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified)” Is journal default?” (Answer Y) 4. “Do you use resizer?” (Answer N) 5. It tells you that a new uuid has been generated. 6. “rebuild-sb: You either have a corrupted journal or have just changed the start of the partition with some partition table editor. If you are sure that the start of the partition is ok, rebuild the journal header. Do you want to rebuild the journal header?” Answer Y 7. The following info is displayed: Reiserfs super block in block 16 on 0x901 of format 3.6 with standard journal Count of blocks on the device: 73264320 Number of bitmaps: 2236 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0 Root block: 0 Filesystem is NOT clean Tree height: 0 Hash function used to sort names: not set Objectid map size 0, max 972 Journal parameters: Device [0x0] Magic [0x0] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x1: some corruptions exist. sb_version: 2 inode generation number: 0 UUID: <my UUID removed> LABEL: Set flags in SB: Is this ok ? (y/n)[n]: 8. Answer “Y”. 9. With amazing speed the program does its thing and ends 3. reiserfsck --scan-whole-partition --rebuild-tree /dev/sda1 (where /sda1 is the correct drive for my system) 4. Mounted it using the suggestions from steini84 mkdir /mnt/recovery mount /dev/sda1 /mnt/recovery 5. Copied the directories it found off to another drive, then sifted through lost+found later

Thanks steini84, that worked. I did have to use mount /dev/sde1 /mnt/recovery before it would mount. Looks like I recovered a TON of stuff. I'll be sifting through it the rest of the night... thanks everyone involved! Much appreciated.

If you have a monitor and keyboard attached to your server, you can sign in at the console instead of through putty/web, and type this command mcedit /boot/config/network.cfg That will bring up your network configuration. This is what my network settings look like (with the IP addresses removed, just input your own values inside the quotes): USE_DHCP="no" IPADDR="xxx.xxx.xxx.xxx" NETMASK="255.255.255.0" GATEWAY="xxx.xxx.xxx.xxx" DHCP_KEEPRESOLV="no" DNS_SERVER1="xxx.xxx.xxx.xxx" BONDING="no" BONDING_MODE="1" Once that's all typed out, press F2 to save, then F10 to quite. You'll probably need to reboot your server again, but once it's back up, you should be able to connect to it again.

OK, ran the reiserfsck --rebuild-sb which completed succesfully, then ran reiserfsck --scan-whole-directory --rebuild-tree. It just completed. All the while I was doing this, the drive in question was not part of the array. How do I view the recovered files on my drive? I can't cd to /dev/sde1 as this is not a directory. Is it safe to add the rebuilt drive to my array to copy off the files?

After some careful reading on the reiserfsck options, I ran reiserfsck --check /dev/sde1, and it immediately came back with: root@Saidar:/boot/custom# reiserfsck --check /dev/sde1 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/sde1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes reiserfs_open: the reiserfs superblock cannot be found on /dev/sde1. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. I came across this forum post, where user bjp999 had to run reiserfsck --rebuild-sb, but needed to know exact, specific answers to the questions asked. I imagine the answers have changed from 4.2.1 to 5.0. Does anyone know what the current answers are? Do I even need to do this, or should I do as garycase suggested:

OK, dd finishing cloning to another 3TB drive, so I'm ready to try running some commands. Anxiously awaiting expert advice...

After reading through the various links on google, it looks to me like your dd command makes sense. I've got that running now. Unfortunately there's no progress bar so I guess I've gotta let it process and check on it tomorrow or something. I've got a 3TB seagate copying to a 3TB WD, so I imagine it'll take quite some time. I'm hoping that JoeL or Weebotech can chime in with some advice for reiserfsck commands...

I've never heard of DD before, but a link from your previous post gave some commands that referenced dd. The first command that the guy is this: ssh deadserver dd if=/dev/hda1 conv=noerror > hda1.img I assume I would use a similar command to image to another drive locally in the machine. would I just use the last part of the command as such, if my failed disk is disk1, and a spare disk is disk4: dd if=/dev/md1 conv=noerror > /dev/md4/md1.img I'm still getting my feet wet as far as linux is concerned, and this is far outside the scope of anything I've done before.

The worst part is, that is what I'm trying to accomplish now. I've not had a backup of all my data, so I'm currently waiting for additional drives to show up. Unfortunately, I'm waiting on parity drives. I had a bad string of luck over the weekend and had a 3TB parity drive fail in addition to two other 2TB drives. I do not have any parity at all. I was thinking that I needed to do some sort of reiserfsck command, but not 100%. I'll take the drive in question out of the array for now, and wait to hear back from some of the other folks here.

As in the title, I accidentally assigned one of my data disks as parity. The array started and automatically began the initial parity sync. It ran for about two seconds before I noticed what was going on. Stopped array, ran new config utility, and reassigned all my disks. Now disk1 is showing up as unformatted. It's got about 1.2 TB worth of data on it that I would love to recover... syslog is attached. Where can I go from here? I'm on unraid 5.0, no plugins except the new webgui and unmenu. syslog.txt

If you're comfortable with the command line, you could set up rsync on each of your servers and then copy directly from one server to another without using another computer as a middle man: http://lime-technology.com/forum/index.php?PHPSESSID=04f6c9ce799b1a76883ebb7bcdaddd13&topic=13432.msg127670#msg127670

I think this may be my issue... I have an Asus P7P55D-E Pro mobo with a core i3 processor, 10GB ram. I have eight hard drives (2TB and 3TB) connected directly to the mobo, and an additional five 250GB hard drives in a 5-in-3 cage on a Dell PERC H310 raid controller. I kicked off the check before I went to church this morning, and now that I'm back, it seems to be working as I expected (see screenshot). I'll have to do some further testing, but it looks like the rebuild is dog slow for the first 250GB. Thanks for the advice, I'll definitely check out that other thread you posted.

Yes, you can store data on your cache drive, and it is not protected by parity. Lots of people use their cache drive to store the settings/data for the various plugins. I use my cache drive to store the data for Plex and Transmission. Sure, I lose that stuff if my cache drive fails, but it's not really data I'm concerned about keeping. It's no big deal to me to put a new cache in and let those apps repopulate the data.