Oct 2 10:49:29 HalutNAS vices: Warning: shell_exec(/bin/df '/mnt/remotes/10.246.37.221_Multimedia' -output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Oct 2 10:49:26 HalutNAS vices: Warning: shell_exec(/bin/df '/mnt/remotes/10.246.37.221_Multimedia' -output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Oct 2 10:48:42 HalutNAS vices: Unmounting Remote SMB/NFS Share '10.246.37.221:/srv/halut-pool/Multimedia'. Oct 2 10:48:42 HalutNAS vices: Removing Remote SMB/NFS share '10.246.37.221:/srv/halut-pool/Multimedia'. Oct 2 10:48:27 HalutNAS vices: Share settings updated. but after trying to access the folder this changes to '0' and the system is kind of freezed. After mounting, the nfs share is shown with the correct size etc. The nfs-share can be mounted but - just with smb - cannot be accessed. Not knowing what to do I set up an nfs-server as an alternative.Īnd the shares should be available for unraid: Just to let you know - with Win11 the smb-shares are still available. Once I get access to the data, I plan to just run nextcloud on freeNAS since this seems to be more headache then its worth.Īfter updating to unraid 6.11 I cannot access my smb-shares that are located at my old nas I am not sure if it is even using ZFS since it is mounted using XFS.ģ. Yes I am using a 10gb interface between freenasUnraidClient computer. Anyway I didn't do any speed tests but it didn't feel like it was an improvement in speed over unraid. To be honest it was hacked this together using several different tutorials and trial and error. Not sure how the speed aspect turned out since freeNAS array is ZFS but when it was connected to unraid the share was formatted XFS, I think that's how it works. the idea was to use the docker in unraid then take advantage of the ZFS files system in freeNAS for better error protection and speed. I like the docker for nextcloud and the docker system in general in unraid better then freeNAS jails and plugins.Ģ. This is what I get, the result is that xfs_repair tries to verify superblock and I get "." continuously until I ctl^c to break out.ġ. I didn't see a way from the GUI to do an xfs_repair, so I tried from the command line. The drive shows up as dev\sdw so I THINK? the iSCSI interface is working correctly, but this could be cashed from when it was working. This is the error I get when I mount the array with unassigned devices for the iSCSI drive. I cant mount the drive under unassigned devices. Unassigned device as it shows up in main menu (hope you can see it) Here is a high level diagram of the setup. The catch is that the file system is located on an iSCSI attached file share accross 10Gig optic, that is mounted using unassigned devices. I have been running this setup without any issues for over a year. It looks like I have a corrupted XFS system that I need to repair. I hope this is the right place to post this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |