[[Plugin] Nvidia-Driver]

15 hours ago, ich777 said:

The first line tells the system that it's a 1050Ti but actually the second line tells you that this is a Fermi based card (Geforce 400 and 500 series), Pascal based card should have something like a GP106 Audio Controller on it and not a GF116 (Fermi based).

 

Unfortunately I think you're right. I should have known better; It has a VGA port and Nvidia hasn't done analog video since Maxwell.

That's what I get for not paying close attention to the listing.

Thanks for the help!

[[Plugin] Nvidia-Driver]

Here is the diagnostics .zip.

What do you mean "a picture from the card itself?"

Like boot unraid to UI mode and a take a picture? 

nas-diagnostics-20210707-1630.zip

 

EDIT: Booting to GUI mode gives the same error I see in the syslog. I just get left on a black screen. If I change console sessions (Ctrl+Alt+F1) I get the usual console login prompt. startx does nothing.

It seems like the system recognizes the card, but the driver doesn't. The device ID(?): '0000:01:00.0' doesn't seem right to me.

[[Plugin] Nvidia-Driver]

I just picked up a GTX 1050ti to use for Plex transcoding and I'm getting the error message: 

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

 

It shows up in lspci -v and I've made sure it's not checked under Tools>System Devices (VMs are disabled.)

 

I see this in the syslog:

kernel: nvidia: probe of 0000:01:00.0 failed with error -1

kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).

 

Google doesn't give me any results except that it may be a bug in the nvidia drivers.

Is there anything I can do?

 

[Hangup on Samba Transfer Between Shares]

If the source and destination both are on the same disk, and you're copying from share to share, then your results are probably right.  Going share to share (and doing it from the network is going to wind up reading a block, writing the block (and the thrashing of the drive head), along with transferring everything over the network to do this. 

 

If the destination is on the same disk as the source, then the absolute fastest way to do this is to enable disk shares and transfer from diskX/shareA to diskY/shareB -> it'll be instantaneous  (but you can't mix disk shares and user shares with the copy otherwise you'll corrupt the files.)

 

Next fastest way is to avoid the overhead imposed by the network transfers, and either use the command line, midnight commander, or Dolphin / Krusader docker applications

 

I think you're right, I had it set up differently before, where each share was essentially on a different disk.

I guess the best way to deal with that is just to separate them again.

 

New (Intel) network card and having share live on separate disks seems to be the answer.

 

Thanks again

[Hangup on Samba Transfer Between Shares]

Sorry I didn't have a chance to post back earlier.

 

I'm currently using 6.2.0 beta 23.

 

I think the issue was with my network card, my integrated one is realtek and I hear they have issues.

So, I got an new Intel nic (EXPI9402PTBLK) and that seems to have stopped the issue with it freezing the whole system.

 

It seems to be working now, but it's a lot slower that I'd like. Only ~13-15 MB/s.

I'm waiting for the last hard drive to come in, so I don't have parity setup yet.

 

I'm not sure which tweaks I should be looking for.

 

Thank you guys for your help!

[Hangup on Samba Transfer Between Shares]

I'm pretty new to unRAID and I'm still in the trial, but I absolutely love it.

 

But I'm having this issue whenever I try to transfer files from one share to another through samba. It starts like one would expect, but after ~5% the transfer comes to a screeching halt and refuses to continue. Sometimes this even crashes explorer on my Windows machine. It won't let me even connect until I reboot the server, and most of the time the web interface gets taken down with it making it difficult to reboot it safely.

 

My previous iteration of my home server was using Debian and simply running samba, and I'd never had this problem before.

 

The old message I get is 'waiting for lo to become free' on the monitor connected to the server. It makes it sound like that interface it getting overloaded somehow, but I'm not sure what is causing it, let alone how to fix it.

 

For now I can manually transfer files from share to share using mc, but I don't want to have to do that because it's a bit cumbersome.

 

Let me know if there's any more info I can get you that would be beneficial.