OK my patience with this system is bringing me to a boil. We set up TrueNAS on a PC basically to use it as a mass storage device for movies, music, etc. We have myself and my Partner set up on it with absolute FULL permissions to do whatever we want in this thing. Currently I'm able to access the drive one one PC, and not another despite having the exact same credentials an mapping in place for the drive to be fully accessible on any pc. I'm beginning to feel like this program is the hard way around what should be a dirt simple thing - a common access point for all of our shared movies. What is causing this to deny access from one machine despite being fully accessible to others with the exact same credentials? I'm ready to pull the plug on this and let the windows virus do the work if this continues to be a thorn in my side like this.
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
Riddle me this
- Thread starter Wolfy01
- Start date
- Joined
- Feb 2, 2018
- Messages
- 1,401
No error message, no setting, no info about things you tested and the result, ... There is nothing we can do from that post.
To troubleshoot such situation, I usually proceed from lowest ISO network layers to the highest. Also, because you have 2 clients with different end results, do each test twice, once per host, and compare the results. For each test, bring back the error message / result when failed.
So can you ping the TrueNAS IP address system from both ?
Can you connect to its web interface from both ?
Can you connect the TCP port of your file sharing service (eg: 2049 for NFS) ?
Can you connect your share from first system ? If yes, disconnect it before trying to connect it from the second.
Can you connect the same share twice (one per client) at the same time ?
You have to help yourself a little more before we can help you.
To troubleshoot such situation, I usually proceed from lowest ISO network layers to the highest. Also, because you have 2 clients with different end results, do each test twice, once per host, and compare the results. For each test, bring back the error message / result when failed.
So can you ping the TrueNAS IP address system from both ?
Can you connect to its web interface from both ?
Can you connect the TCP port of your file sharing service (eg: 2049 for NFS) ?
Can you connect your share from first system ? If yes, disconnect it before trying to connect it from the second.
Can you connect the same share twice (one per client) at the same time ?
You have to help yourself a little more before we can help you.
As requested. This is from two different PC's with identical credentials. same login and password for both. Literally this morning the one now giving this issue was running just fine. This is what's making me mad. It make less than zero sense to me why this issue exists.
Attachments
- Joined
- Jul 12, 2022
- Messages
- 3,222
We need your TN system's full hardware specs, as per forum's rules.
danb35
Hall of Famer
- Joined
- Aug 16, 2011
- Messages
- 15,504
Looks like a failed boot device.
Then why are you posting in the legacy FreeNAS section of the forum?
IT IS the free version
11th gen Intel i9 on MSI motherboard, 64GB ram 512gb SSD (windows bootable if I remove the USB stick), 18gb platter NAS rated Toshiba HDD. This is in effect a recycled gaming PC.
danb35
Hall of Famer
- Joined
- Aug 16, 2011
- Messages
- 15,504
It's still TrueNAS. FreeNAS ended with the 11.x release series; everything since then is TrueNAS and has its own section in the forums.
@Patrick M. Hausen, this might be part of your answer.
- Joined
- Feb 2, 2018
- Messages
- 1,401
As @danb35 mentioned, it looks like a failed boot device in your TrueNAS. One possibility is that your first system connected the share before the failure prevented the system to function properly. Because its session is already established, it can access the resources more directly. Because of that failed device, your system was not working normally anymore and the second client was unable to complete the connection,
So first thing will be to re-install on a new boot device and restore your backed up config if you have or learn about the importance of backups if you have not. If you have no backups, you will have to re-configure everything. The data pool is still intact and can be imported. Do not re-create it from scratch or that will effectively destroy everything that is saved in it as of now.
Also, it will be good to know why that boot device failed and protect yourself against that. USB sticks are not recommended anymore as boot devices. If you have only this, at least have 2 of them in mirrors to help mitigate the risk.
So first thing will be to re-install on a new boot device and restore your backed up config if you have or learn about the importance of backups if you have not. If you have no backups, you will have to re-configure everything. The data pool is still intact and can be imported. Do not re-create it from scratch or that will effectively destroy everything that is saved in it as of now.
Also, it will be good to know why that boot device failed and protect yourself against that. USB sticks are not recommended anymore as boot devices. If you have only this, at least have 2 of them in mirrors to help mitigate the risk.
- Joined
- Jul 12, 2022
- Messages
- 3,222
So you have installed TN on the USB stick? You don't want an external USB stick as your boot drive, especially on a laptop.
