Jump to content

Can't connect using AFP


luksak

Recommended Posts

I just upgraded my array to unRAID 6.0.0. I am able to connect to it using SMB but when connecting using AFP I get this error:

 

The operation can’t be completed because the original item for “Media” can’t be found.

 

What might me wrong here?

Link to comment
  • 4 weeks later...

Sorry, I was unable to do this earlier... Now i tried to run the check, but it failed:

 

reiserfsck --check /dev/sda
reiserfsck 3.6.24

Will read-only check consistency of the filesystem on /dev/sda
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

reiserfs_open: the reiserfs superblock cannot be found on /dev/sda.
Failed to open the filesystem.

If the partition table has not been changed, and the partition is
valid  and  it really  contains  a reiserfs  partition,  then the
superblock  is corrupted and you need to run this utility with
--rebuild-sb.

 

Am I doing something wrong? Is /dev/sda incorrect?

Link to comment

Sorry, I was unable to do this earlier... Now i tried to run the check, but it failed:

 

reiserfsck --check /dev/sda
reiserfsck 3.6.24

Will read-only check consistency of the filesystem on /dev/sda
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

reiserfs_open: the reiserfs superblock cannot be found on /dev/sda.
Failed to open the filesystem.

If the partition table has not been changed, and the partition is
valid  and  it really  contains  a reiserfs  partition,  then the
superblock  is corrupted and you need to run this utility with
--rebuild-sb.

 

Am I doing something wrong? Is /dev/sda incorrect?

There are two potential issues:

  • If you are going to use the raw devices then you need to include the partition (i.e. /dev/sda1).  However this is not recommended as doing so will invalidate your parity
  • The recommended way is to start the array in Maintenance mode and the use /dev/md?? for the device where ?? corresponds to the disk number in unRAID.  This approach does not invalidate parity.

Link to comment

Sorry, I was unable to do this earlier... Now i tried to run the check, but it failed:

 

reiserfsck --check /dev/sda
reiserfsck 3.6.24

Will read-only check consistency of the filesystem on /dev/sda
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

reiserfs_open: the reiserfs superblock cannot be found on /dev/sda.
Failed to open the filesystem.

If the partition table has not been changed, and the partition is
valid  and  it really  contains  a reiserfs  partition,  then the
superblock  is corrupted and you need to run this utility with
--rebuild-sb.

 

Am I doing something wrong? Is /dev/sda incorrect?

 

This is totally incorrect. Again, see Check Disk Filesystems in my sig. Read the instructions completely and follow them carefully.

 

Link to comment

Sorry, I am not that familiar with linux drives. I ran the checks without any errors:

 

reiserfsck --check /dev/md1
reiserfsck 3.6.24

Will read-only check consistency of the filesystem on /dev/md1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Tue Jul 21 08:33:52 2015
###########
Replaying journal: Done.
Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..  finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
        Leaves 505132
        Internal nodes 3383
        Directories 171664
        Other files 222257
        Data block pointers 467148444 (1799609 of them are zero)
        Safe links 0
###########
reiserfsck finished at Tue Jul 21 10:58:29 2015
###########


-----------------------------------------------------------------------------


reiserfsck --check /dev/md2
reiserfsck 3.6.24

Will read-only check consistency of the filesystem on /dev/md2
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Tue Jul 21 08:34:59 2015
###########
Replaying journal: Done.
Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..  finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
        Leaves 398112
        Internal nodes 2540
        Directories 45898
        Other files 348336
        Data block pointers 344165177 (1189541 of them are zero)
        Safe links 0
###########
reiserfsck finished at Tue Jul 21 09:28:21 2015
###########


-----------------------------------------------------------------------------


reiserfsck --check /dev/md3
reiserfsck 3.6.24

Will read-only check consistency of the filesystem on /dev/md3
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Tue Jul 21 08:35:28 2015
###########
Replaying journal: Done.
Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..  finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
        Leaves 1130262
        Internal nodes 7432
        Directories 489876
        Other files 1865133
        Data block pointers 743420071 (34526487 of them are zero)
        Safe links 0
###########
reiserfsck finished at Tue Jul 21 09:29:44 2015
###########


-----------------------------------------------------------------------------


reiserfsck 3.6.24

Will read-only check consistency of the filesystem on /dev/md4
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Tue Jul 21 08:35:50 2015
###########
Replaying journal: Done.
Reiserfs journal '/dev/md4' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..  finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
        Leaves 729104
        Internal nodes 4674
        Directories 3777
        Other files 42866
        Data block pointers 729725023 (21372400 of them are zero)
        Safe links 0
###########
reiserfsck finished at Tue Jul 21 11:23:49 2015
###########

Link to comment

There you go. This looks supsicious:

 

Jul 26 16:06:36 Tower afpd[7499]: Reading IPC header failed (-1 of 14 bytes read): Connection reset by peer
Jul 26 17:35:47 Tower afpd[28094]: read: Connection timed out
Jul 26 17:35:47 Tower afpd[28094]: dsi_stream_read: len:-1, Connection timed out
Jul 26 19:57:21 Tower afpd[28094]: afp_alarm: child timed out, entering disconnected state

tower-diagnostics-20150728-1034.zip

Link to comment

I probably can't help but.. I'll give it a shot.

You say you can access disks via AFP but not shares.

Are you exporting shares via AFP? Your disk must be set to export via AFP since that works.

How are you accessing them, via the finder or an other way.

What happens when you try to access shares, any dialog or etc.

What version of OS are you using? What Mac?

 

Just read your original post.. Are you using an Alias to access the share?

That is what it sounds like.. 

Link to comment

My shares are exported via AFP. They also show up. But when trying to connect I get this message: "The operation can’t be completed because the original item for “Media” can’t be found."

 

I am trying to connect via Finder.

 

I am running on the latest Mac OSX.

 

No, I am not using an alias.

Link to comment

This isn't going to be much help, but I just enabled AFP and had to disable/enable export to get everything working. Mine is just set public access since it's just on my local network so no logging in as a specific user or anything. I was able to access my folders just fine in Finder, although it took many seconds for it to actually connect up which seemed odd.

 

Did a quick google search and found this that might point to a permissions issue:

 

http://apple.stackexchange.com/questions/131613/the-operation-can-t-be-completed-because-the-original-item-for-foo-can-t-be-fo

 

There are others if you google "afp The operation can’t be completed because the original item cannot be found"

 

Maybe try disabling/enabling the share export and if you're using any security change it to public and see if that helps.

Link to comment

I already tried disabling and enabling without success.

 

I found out something else: I created another share to test and it worked. So this problem only affects this share.

 

Permissions could be causing the issue. Should I try running chown and chmod commands? If so, what should I set the permissions to?

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...