Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Whenever trying to run the read-nafile command I'm getting the error message below:
Connect-NaController FilerA
Read-NaFile -path /vol/vol0/etc/syslog.conf
Read-NaFile : Unable to open /vol/vol0/etc/syslog.conf: No such file or directory
At line:1 char:1
+ Read-NaFile -path /vol/vol0/etc/syslog.conf
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (FilerA:NaController) [Read-NaFile], EONTAPI_ENOENT
+ FullyQualifiedErrorId : ApiException,DataONTAP.PowerShell.SDK.Cmdlets.File.ReadNaFile
Has anyone seen this issue before?
Thanks!
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you sure your root volume is called vol0 and that the path is correct? Can you successfully perform a Read-NaDirectory on that path?
5 REPLIES 5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see no issue
PS C:\powershell> read-nafile /vol/vol0/etc/syslog.conf
#*.info /dev/console
*.info /etc/messages
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are correct the command should work.
The issue can be recreated while trying to access any other files i.e. hosts,rc,etc. I am testing the command against different controllers and it is failing as well.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What I would suggest is use cifs and i usually browse etc$ via native powershell..
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you sure your root volume is called vol0 and that the path is correct? Can you successfully perform a Read-NaDirectory on that path?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cole thanks for pointing me in the right direction, vol0 has been renamed and that is what was causing the issue. After updating the name the command ran fine.
