Safepoint create error 1100

Royce_Lithgo · January 30, 2016, 7:55pm

I’ve tried three different FW versions and safepoint create failed on all of them.

This as in the alert email:
Event description:2 - There was an error creating your safepoint Main on the Passport_Ultra share on WDMyCloud.

Severity:warning

Event code:1100

This is a new MC and new Passport Ultra drive attached to the USB.

Morden2004 · January 30, 2016, 11:22pm

What hard drive size and manufacturer?

Paul

Royce_Lithgo · January 31, 2016, 12:18am

WD Passport Ultra 3TB - brand new drive purchased specifically for this purpose.

No firmware update is required for the drive (I already checked).

SectorGZ · January 31, 2016, 3:56am

If you haven’t … have you tried a “System Restore and Reboot” after each firmware upgrade/downgrade? Sometimes, at least in my case, this has helped.

Royce_Lithgo · January 31, 2016, 6:21am

Well I’ve done that and restarted the safepoint.

For some reason doing the restore broke the mycloud.com access to my drive for Chrome on my Mac. Works for other browsers. Have tried clearing the cache but didn’t help.

Getting really tired of all the issues with this device.

rac8006 · January 31, 2016, 9:18pm

I decided to create a sharepoint on My Cloud A. So I went into the dashboard and created the sharepoint on my other My Cloud B. I told it not to start the backup until 2am tomorrow.
After the sharepoint was created. I noticed that the other My Cloud B was mounted on My Cloud A as //192.168.10.219/Public 5809669936 189631276 5620038660 4% /media/WDSAFE/182363853338136281313974967723235549772. On My Cloud B in the Public directory was a folder named _WDPROT/WDSAFE/test_share. In this folder were one file and three directories. 182363853338136281313974967723235549772.info backup shares system. I also noticed that there was a cron job in /etc/cron.d/WDSAFE Which looked as follows:
0 2 1 2 * root sudo perl /usr/local/NSPT/WDSafe/safeptExec.pl --operation=create --handle=182363853338136281313974967723
235549772
This says to start safeptExec.pl at 2AM in the morning
to create the safepoint. safeptExec.pl is the safepoint manager code. It is written in perl.
Now I know that the connection between My Cloud A and the safepoint on My Cloud B is a mounted filesystem.

Take a look at the info file created on the sharepoint system. It has information about the system that created the sharepoint including its ip address. Which might create problems if it changes.

RAC

Royce_Lithgo · January 31, 2016, 10:11pm

I am well aware of the existence of the .info file - I use it to remotely monitor progress of the safepoint create. However I don’t see how that helps at all in resolving my issue.

When you talk about sharepoints in your post above, don’t you mean safepoints?

rac8006 · February 1, 2016, 1:08am

Yes it is called safepoint. The error code 1100 is a failed to create.
alert-param.sh:wdsafeCreateFailed=“1100”

You can also look into the wdnas.log for messages about safepoints. This information was to help other people look into the way safepoints are handled.

RAC

rac8006 · February 1, 2016, 2:57pm

This morning I checked the log and found a error 1100. Which indicates that it failed to create. But when I go to the backup system and look at the test_share folder it looks like everything was copied correctly.

RAC

Bennor · February 1, 2016, 4:30pm

I had the same happen yesterday when experimenting with Safepoint and an external USB hard drive. Got the 1100 error and the “the safepoint is in an invalid state, try updating to fix the problem” message on the Safepoint screen. Doing a System Only restore then setting up a new Safepoint from the Dashboard worked for me. No longer get either message when doing a Safepoint update to the external USB drive.

rac8006 · February 1, 2016, 4:46pm

Also tried to do the update it failed also. Not sure why because it looks like all files were copied over to the backup system. In fact it backed up folders that I didn’t want backed up. I thought it would only backup Public. But it backed up everything mounted to /nfs.

RAC

Royce_Lithgo · February 1, 2016, 7:36pm

I am so sick and tried of this crappy My Cloud.

Safepoint create failed yet again with error 1100. I have tried 3 different FW versions, factory restore and still it doesn’t work. Safepoints are broken functionality on this device.

WD support has so far failed to resolve this problem.

I hate WD My Cloud. Worst product ever.

Log follows:
Event title:There was an error creating your safepoint.

Event description:2 - There was an error creating your safepoint Main on the Passport_Ultra share on WDMyCloud.

Severity:warning

Event code:1100

Event time:02-01-2016 08:58:35 AM

Firmware version: 04.04.02-105

Royce_Lithgo · February 1, 2016, 7:38pm

This last attempt was after doing s System Only restore and setting up new safepoint.
Still didn’t work for me.

Morden2004 · February 1, 2016, 8:01pm

I would be suspicious of that external hard drive rather than the MyCloud. It has been reported (somewhere here) that some hard drives are not a happy fit with the MyCloud, and size also seems to be an issue…

What native format is the drive?
And what size is this drive and what size is your MyCloud?

Paul

Bennor · February 1, 2016, 8:21pm

Have you tried using a different external hard drive or different network location to store the safepoint?

I’d also make sure there is no _ (underscore) or special characters in the external hard drive name too just to be on the safe side. For example rename Passport_Ultra to PassportUltra then try a new Safepoint backup to the drive.

rac8006 · February 1, 2016, 9:11pm

If you check for your safepoint mount name using “df” command. YOu can then cd to that mount point. You should see a folder called _WDPROT inside that folder will be a folder called WDSAFE. Inside that folder will be your safepoint backups. Mine was called test_share. in this folder is the .info file for the safepoint along with three folders called backup shares and system. The shares folder will have your backup files.

RAC

Royce_Lithgo · February 1, 2016, 9:28pm

So this is what I see in wdnas.log:

2016-02-01T08:58:34.717310-08:00 di=Q8BW7BEPwI err logger: ERROR: CopyHandler(501): Failed to complete rsync command to copy data - rsync failed with error, 24
2016-02-01T08:58:34.717466-08:00 di=Q8BW7BEPwI err logger: ERROR: CopyHandler(531): Failed to copy data from /DataVolume/shares to /var/media/Passport_Ultra//_WDPROT/WDSAFE/Main/shares
2016-02-01T08:58:34.722782-08:00 di=Q8BW7BEPwI err logger: ERROR: SafeptRunHandler(1358): 305503205734702764497429295211298619239: Failed to process shares to Safe-Point
2016-02-01T08:58:34.813396-08:00 di=Q8BW7BEPwI err logger: ERROR: SafeptRunHandler(352): 305503205734702764497429295211298619239: Safe-Point Run Failed
2016-02-01T08:58:42.123566-08:00 di=Q8BW7BEPwI err logger: ERROR: safeptExec(1036): OUTPUT Status: FAILED; Failed to complete rsync command to copy data - rsync failed with error, 24
Status: FAILED; Failed to complete rsync command to copy data - rsync failed with error, 24

And rsync error 24 is:
24 Partial transfer due to vanished source files

Does this mean any changes to source files while safepoint create is running will cause safepoint create failure? Considering that it takes at least 2 days to create the safepoint, I would need to ensure that no backups are done during that period. If that’s the case, then its just another reason why this device is so useless.

rac8006 · February 1, 2016, 9:51pm

I just checked my safepoint. with the exception of the .wdmc folder all other folders were copied to the backup safepoint. Here is my wdnas.log
2016-01-30T10:57:38.421897-05:00 di=TCG2w1CF6F notice wdAutoMounter[7717]: AutoMounter started
2016-01-30T10:57:41.770871-05:00 di=TCG2w1CF6F info logger: INFO: Device added: device=2, vendor=Verbatim, model=STORE N GO, serial_number=071058E90E5F9529, revision=1.10
2016-01-30T10:57:44.653464-05:00 di=TCG2w1CF6F info logger: INFO: Mode sense to Power condition didn’t return enough info to be supported. Verbatim STORE N GO
2016-01-30T10:57:47.524256-05:00 di=TCG2w1CF6F info logger: INFO: attached USB partition, reduce inotify limit to: 20000
2016-01-30T10:58:04.526654-05:00 di=TCG2w1CF6F info logger: updateShareBindMntDir.sh:–add VERBATIM_5
2016-01-30T10:58:06.696981-05:00 di=TCG2w1CF6F info logger: INFO: Partition added: device=2, partition=1, share_name=VERBATIM_5, label=VERBATIM, type=vfat, uuid=1154-6475
2016-01-30T10:58:13.696066-05:00 di=TCG2w1CF6F info logger: updateShareBindMntDir.sh:–delete VERBATIM_5
2016-01-30T10:58:13.850393-05:00 di=TCG2w1CF6F info logger: updateShareBindMntDir.sh:umount succeded
2016-01-30T10:58:14.663510-05:00 di=TCG2w1CF6F info logger: INFO: Partition ejected: device=2, partition=1, share_name=VERBATIM_5, label=VERBATIM, type=vfat, uuid=1154-6475
2016-01-30T10:58:15.382500-05:00 di=TCG2w1CF6F info logger: INFO: Device ejected: device=2, vendor=Verbatim, model=STORE N GO, serial_number=071058E90E5F9529, revision=1.10
2016-01-30T10:58:15.753464-05:00 di=TCG2w1CF6F notice wdAutoMounter[7717]: AutoMounter stopped
2016-01-31T15:38:16.532694-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptActionScheduler(212): Schedule not found for action ‘update’ on handle ‘182363853338136281313974967723235549772’
2016-01-31T15:38:16.556525-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptActionScheduler(255): Schedule Get Failed for action update on handle 182363853338136281313974967723235549772
2016-01-31T15:38:16.582593-05:00 di=TCG2w1CF6F err logger: ERROR: safeptExec(1036): OUTPUT Status: NOTFOUND; Schedule not found for action ‘update’ on handle ‘182363853338136281313974967723235549772’
2016-01-31T16:05:21.410016-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: INVALID; Value expected for option --operation
2016-01-31T16:05:43.658449-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: INVALID; Value expected for option --operation
2016-01-31T16:06:50.847298-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: NOTSUPPORTED; getinfo is not supported
2016-01-31T16:07:05.384813-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: INVALID; Invalid argument
2016-01-31T16:07:31.995389-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: INVALID; Invalid argument
2016-01-31T16:07:45.314002-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: INVALID; Invalid Option test-share
2016-01-31T16:07:50.581752-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: INVALID; Invalid Option test_share
2016-01-31T16:08:47.110673-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: INVALID; Invalid Option 182363853338136281313974967723235549772
2016-01-31T16:10:56.949117-05:00 di=TCG2w1CF6F err root: ERROR: SafeptActionScheduler(83): Mandatory Property ‘action’ not set
2016-01-31T16:10:56.972494-05:00 di=TCG2w1CF6F err root: ERROR: SafeptInstance(1239): 182363853338136281313974967723235549772: Failed to instantiate Safe-Point Action Scheduler
2016-01-31T16:10:56.997755-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: FAILED; 182363853338136281313974967723235549772: Failed to instantiate Safe-Point Action Scheduler
2016-01-31T16:11:15.161339-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: NOTSUPPORTED; getinfo is not supported
2016-01-31T16:14:55.311652-05:00 di=TCG2w1CF6F err root: ERROR: SafeptActionScheduler(83): Mandatory Property ‘action’ not set
2016-01-31T16:14:55.335104-05:00 di=TCG2w1CF6F err root: ERROR: SafeptInstance(1239): 182363853338136281313974967723235549772: Failed to instantiate Safe-Point Action Scheduler
2016-01-31T16:14:55.360255-05:00 di=TCG2w1CF6F err root: ERROR: safeptExec(1036): OUTPUT Status: FAILED; 182363853338136281313974967723235549772: Failed to instantiate Safe-Point Action Scheduler
2016-02-01T02:37:39.647821-05:00 di=TCG2w1CF6F err logger: ERROR: CopyHandler(501): Failed to complete rsync command to copy data - rsync failed with error, 23
2016-02-01T02:37:39.672269-05:00 di=TCG2w1CF6F err logger: ERROR: CopyHandler(531): Failed to copy data from /DataVolume/shares to /media/WDSAFE/182363853338136281313974967723235549772//_WDPROT/WDSAFE/test_share/shares
2016-02-01T02:37:39.696420-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptRunHandler(1358): 182363853338136281313974967723235549772: Failed to process shares to Safe-Point
2016-02-01T02:37:39.875532-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptRunHandler(352): 182363853338136281313974967723235549772: Safe-Point Run Failed
2016-02-01T02:37:44.083375-05:00 di=TCG2w1CF6F err logger: ERROR: safeptExec(1036): OUTPUT Status: FAILED; Failed to complete rsync command to copy data - rsync failed with error, 23
Status: FAILED; Failed to complete rsync command to copy data - rsync failed with error, 23
2016-02-01T10:03:50.793786-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptActionScheduler(212): Schedule not found for action ‘update’ on handle ‘182363853338136281313974967723235549772’
2016-02-01T10:03:50.817768-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptActionScheduler(255): Schedule Get Failed for action update on handle 182363853338136281313974967723235549772
2016-02-01T10:03:50.842736-05:00 di=TCG2w1CF6F err logger: ERROR: safeptExec(1036): OUTPUT Status: NOTFOUND; Schedule not found for action ‘update’ on handle ‘182363853338136281313974967723235549772’
2016-02-01T10:08:19.381291-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptActionScheduler(212): Schedule not found for action ‘update’ on handle ‘182363853338136281313974967723235549772’
2016-02-01T10:08:19.404783-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptActionScheduler(255): Schedule Get Failed for action update on handle 182363853338136281313974967723235549772
2016-02-01T10:08:19.429991-05:00 di=TCG2w1CF6F err logger: ERROR: safeptExec(1036): OUTPUT Status: NOTFOUND; Schedule not found for action ‘update’ on handle ‘182363853338136281313974967723235549772’
2016-02-01T11:11:52.631764-05:00 di=TCG2w1CF6F err logger: ERROR: CopyHandler(501): Failed to complete rsync command to copy data - rsync failed with error, 23
2016-02-01T11:11:52.657136-05:00 di=TCG2w1CF6F err logger: ERROR: CopyHandler(531): Failed to copy data from /DataVolume/shares to /media/WDSAFE/182363853338136281313974967723235549772//_WDPROT/WDSAFE/test_share/shares
2016-02-01T11:11:52.711517-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptRunHandler(1358): 182363853338136281313974967723235549772: Failed to process shares to Safe-Point
2016-02-01T11:11:52.822119-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptRunHandler(352): 182363853338136281313974967723235549772: Safe-Point Run Failed
2016-02-01T11:11:55.266122-05:00 di=TCG2w1CF6F err logger: ERROR: safeptExec(1036): OUTPUT Status: FAILED; Failed to complete rsync command to copy data - rsync failed with error, 23
Status: FAILED; Failed to complete rsync command to copy data - rsync failed with error, 23
2016-02-01T11:11:59.182345-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptActionScheduler(212): Schedule not found for action ‘update’ on handle ‘182363853338136281313974967723235549772’
2016-02-01T11:11:59.205616-05:00 di=TCG2w1CF6F err logger: ERROR: SafeptActionScheduler(255): Schedule Get Failed for action update on handle 182363853338136281313974967723235549772
2016-02-01T11:11:59.230890-05:00 di=TCG2w1CF6F err logger: ERROR: safeptExec(1036): OUTPUT Status: NOTFOUND; Schedule not found for action ‘update’ on handle ‘182363853338136281313974967723235549772’

Royce_Lithgo · February 1, 2016, 9:58pm

23 Partial transfer due to error

Different error than mine. The log is completely useless in identifying the error that caused the failure (as is my log).

I am running an update now, but I doubt it will fix the error. The update is redoing the entire safepoint create. I would have hoped that there was some speed improvement by the fact that over 1TB was already copied during the first create, but it looks like its doing it all again.

rac8006 · February 1, 2016, 10:06pm

I tried an update and it also failed. What I did do was do a “du Public” in both the backup and the main system. They both had the same size.

RAC