-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Impulse1337
-
-
Hi all,
I saw this morning that there was a new update (Yay!).
But when i wanted to connect to a docker just now, i saw i couldn't connect..
So i logged in to Unraid and saw this..:
I cannot select anything..
here also the Diag package.be001srvfs01-diagnostics-20230622-2050.zip
not sure what to do, 37TB on the line here..
Im running:
HP DL380 G8 with 12 disks (1 parity disk)Had a lot of dockers running, arround 12 i think, and 2 VM's.
Everything was working, was running 6.11.5 (i think) and updated to 6.12.0 this morning.
-
On 3/13/2017 at 4:27 PM, 1812 said:
If it doesn't work, then post your server diagnostics and xml for the vm.
Well, it doesn't work, and have tried every step here..
I get this error when starting the VM..
I attached the diagnostics and the VM XML.
Could you help? -
2 minutes ago, ich777 said:
Don't think there will be any data lost since i've only add the necessary kernel modules and also the necessary software.
Only built a 6.9.0beta25
Have to build the 6.8.3 version tomorrow, it's getting late...
Here as well, same timezone for us. Give me PM when you got something
-
8 minutes ago, ich777 said:
Could also build it for 6.8.3...
if it's free of data-loss, i can test it.
- 1
-
52 minutes ago, Ioannis said:
This is how everyone does it: allocate an image file and present it to the iscsi initiator (the client).
I would suggest though to allocate it on the cache, if available, because its usage will be exactly the same as VM's vdisks so performance will suffer if allocated on the array.
Configuration on the iscsi target side (unraid in this case) is pretty straightforward. Each iscsi volume (image file) needs the volume path, authentication details (optional, e.g. CHAP2 username/password) and a couple of other (optional) options.
The only thing i am unsure of, is if it is possible to let it expend automatically. If not, is it going to be a hassle to expand it after the file is being used.. But maybe that is too early to think about. I think the first step would be to implement it first
-
58 minutes ago, bonienl said:Any information about how to configure (set up) this on FreeNAS and Windows?
https://thesolving.com/storage/how-to-create-an-iscsi-target-with-freenas/
If you want, i can dedicate some time help testing etc.
EDIT: If i can read correctly, is seems to be based on a dedicated disk, of a "file" that is the target. So, if that is correct, we could do the same on unraid, use a "file" as the target, which is on the array.
Or do i see this too easy? -
Maybe we need to switch all over to freenas then.. they have iSCSI built in iSCSI is, as you can read yourself, needed in every NAS.. a lot of small to medium businesses can/could use this..Not bonienl, but I'm pretty sure there are much bigger fish to fry at the moment. The complications of trying to mix iSCSI with fuse and user shares means this is likely not going to happen any time soon, maybe never.
And mix it with user shares, if iSCSI would be an option, i wouldn't have any problems with the shares..
Verstuurd vanaf mijn SNE-LX1 met Tapatalk
-
@bonienl is there any progression here?
-
This is my setup. Not sure why it isn't working thoI've tried Bridge as well same behavior...
Verstuurd vanaf mijn SNE-LX1 met Tapatalk
-
I'm using the 'bridge' settings in Unraid. Working for 8 dockets or something
Verstuurd vanaf mijn SNE-LX1 met Tapatalk -
I would use it to back-up Windows VM's using Windows Back-up.. Got like 15 Servers waiting for LT to implement this.. or even a trial testign version, so i could test this at home, before implementing in a live business network with over 150 users.. Iscsi is like the last thing needed in my eyes..
-
On 6/5/2017 at 8:54 AM, bonienl said:
unRAID v6.4.0-rc2 is available with the new agent included.
when will it be available as an update?
Currently running 6.3.5 and no updates
Update to 6.12 - all drives missing
in General Support
Posted
The only thing that was the issue, was rebooting the server for the update..
The raid controller went haywire.. i just took it out, put it back in and booted again.
everything back to normal..
Case closed.