rmp5s

Time for some MemTest fun! Thanks.

Machine rebooted again right around 10:20p last night, Feb 14th. Looking through the syslog file, I'm seeing what looks like memory errors around that time. Seem about right, @Squid? syslog

Alright. That's a start. Will do. Thanks.

I'm trying to figure out why one of my unRAID servers is rebooting. It'll be up for 6-8 days at a time, then reboot. I've gone through the logs (attached) and the only thing I see is that it says "unclean shutdown detected". Nothing about why it's actually doing it. Anyone see anything in the log as to WHY it's rebooting? I've been troubleshooting this for a couple months now and I still have no idea why it's doing this. I moved the RAM sticks into the correct slots on the motherboard, disabled a few plugins, disabled Docker, now I'm going to disable the VM service and see if it still reboots. I'm thinking about starting up the syslog server on the thing to see if I can find out what's going on...anyone have any other ideas? Machine is an HP Proliant DL360e G8 Server with 2x E5-2430 CPUs, 64GB RAM and 2 8TB drives, a 3TB drive, an 8TB parity drive and a 240GB NVMe SSD running version 6.8.0. I have another unRAID install, same version, running on an HP ProLiant DL380p G8 Server with 2x E5-2667v2, 64GB RAM, etc that is rock solid. tower-syslog-20200209-1647.zip

I REALLY need to figure out a way to shove a GPU in the thing...THAT is what I need to quit dragging my feet on.

Got ya. That's what I was thinking about doing...just having them all assigned to a VM. I would too but I don't have enough PCI slots for that...I don't think, anyway... So...thanks for participating in this little thought exercise, everyone. lol The server and/or unRAID has limitations...maybe it's time to build a new machine...hmmmmm...

Hey, they always say "RAID is not a backup", right? lol That machine wouldn't be used for anything important. It would mostly just be to play around. Maybe I'll buy 9 of these things and assign them to a Windows Server VM. With RAID10, I'd end up with a bit under 2TB of usable space which isn't too bad. I dunno. Would adding a bunch of drives like that speed up the unRAID array itself any?...or is it kind of a "weakest link" kind of thing where the slowest drive is the fastest it'll go...

Very interesting. I'll look into the ZFS stuff. Maybe I'll give the plugin a shot beings as I am already set up in unRAID. Switching isn't really an option on this server at this point. After getting my first unRAID server up and running, someone asked me why I chose it over FreeNAS. Apparently FreeNAS has changed a LOT in the near decade since I used it last. I had no idea it did most of the same stuff unRAID does.

I'm watching this Linus video and it got me thinking...I have a 12 bay HP Proliant DL380pG8 that only has a parity and two 8TB drives in it right now...what would you put in the other 9 bays to make it really fast? Of course it's going to be limited by SATA, but I was thinking maybe put a bunch of drives in there and assign them all to a Windoze Server VM and create a RAID10 array out of them?...slap a 10G NIC in the thing and assign that to the server too? I dunno. Kinda just toying with ideas. What would you do if you had 9 drive bays and a bunch of RAM to play with? Server specs: HP ProLiant DL380p LFF G8 2x E5-2667v2, 16 Cores/32 Threads 64GB RAM 2x 8TB SATA drives 1x 8TB Parity 1x 480GB NVMe PCIe SSD (which I can not for the LIFE of me get to show up in BIOS...but that's another discussion...)

Well, either way, we're good to go now. Thanks!

You nailed it, my friend! I scrolled down to the routes and it was aaaaaaaaaaaall screwed up. Route delete, route add, boom. Good to go. Thank you!!

Not sure what exactly "bonding" does in unRAID, let alone "active backup"...

I am still getting the error so I decided to uninstall and reinstall Community Applications. Uninstalled and it won't install. I noticed that, when I go to the terminal and try to ping out, I get no responses. How can unRAID not have any network access but the VMs do? Am I missing something?

...oh...well hell, that's simple enough. Thanks.

Hi! Not sure why, but Community Applications can't connect and it's telling me I need to "set static DNS addresses (Settings - Network Settings) of 208.67.222.222 and 208.67.220.220" and try again. I know what DNS servers are and all that, but that's pretty vague. Can anyone shed a little more light on what that means? Thank you!

That -l makes all the difference. That's how to correlate everything. Beautiful. I'll update my post. Thanks.

Yes. I know. But, after spending HOURS trying to get the drive ID method working, I'm STOKED to just have it working. If you'd like to look at my previous posts and see if you could figure out the correct drive ID, have at it.

So, to go from a vdisk to a physical disk (v to p, as it were), first you must dd (copy) your vdisk to the physical disk: dd if="location/of/vdisk" of=/dev/sdX Details can be found in this video. My command was... dd if='/mnt/user/domains/Adobe/vdisk1.img' of=/dev/sde **EDIT: Thank you, John_M!!** When that's done, open up the terminal (top right corner under your server stats) and run... ls -l /dev/disk/by-id ...to get all your disk associations. This is what I was trying to do earlier but, without the "-l" flag, it just comes out as a bunch of random nonsense. With the flag, it shows which ID is tied to which device. So, you run that command and you get something like this: We know that the drive that we want is SDE from the "Main" tab: That means we can use either scsi-35002538e40d01f52 or wwn-0x5002538e40d01f52 to tell the VM which disk to use. So, go edit the VM and hand jam either \dev\disk\by-id\scsi-35002538e40d01f52 or \dev\disk\by-id\wwn-0x5002538e40d01f52 into the disk location: ...and boom...Bob's your auntie. It's that easy. Seriously. Thank you again, everyone. YOU ROCK!!

WE HAVE BOOTAGE, EVERYONE!!! Thank you ALL for the TREMENDOUS amount of assistance everyone provided. Next post will be the last post of the thread with a final recap of what worked. Thank you all...you're the best. 😄

HA!! I spoke too soon!!!

Not looking promising...lol

HA!! I said, "f this xml nonsense", switched back to the normal view, punched in "manual, /dev/sde" and... Boom. lol Now, let's see if it actually boots...

I tried this method from the one post... <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/sda'/> <target dev='hdd' bus='sata'/> </disk> ...and it took it, but when it boots, it's not seeing the drive...windoze isn't booting. I'm still messing with it.

EXACTLY what I'm thinking, too. Looking at "system devices" doesn't scream anything to me...I don't see anything in common between the "/by-id" list and the "system devices" list. You all see anything?

That's what I thought. That's what I've been using and it's giving me an error. Then, when I do the "dev/disk/by-id/" thing, I don't see that disk ID anywhere...at all... Very confusing...