Backup dest is non-existent local share (CASE 17959304)

[jspeigel]

I have an external hard drive (ext3) connected to the upper port in the back of my Ultra 4. In Front View it shows up under Volumes>USB Storage but it does not show as a USB Share under Share>Share Listing. As a result, when I try to run a newly created scheduled backup it fails when it runs and gives the following error:

--------------------------------------------------------------------------------
FULL Backup started.

Job: 001
Protocol: local
Source: [media]/
Destination: [USB_HDD_1]/


Backup failed. Mon Feb 20 23:31:57 EST 2012.

Reason for failure:
The backup destination is a non-existent local share.

[mdgm]

What version of RAIDiator?

What name is shown for the hard drive under Volumes > USB Storage?

Can you connect to it e.g. via CIFS (\\ip.address.of.nas or \\hostname)?

How did you format it to EXT3? Using the NAS? Using a Linux machine? How was it formatted before that? Using a Windows machine? Using a Linux machine? Using a Mac?

What capacity is the USB disk?

[jspeigel]

RAIDiator 4.2.19
Name: USB_HDD_1
I cannot connect via CIFS but can connect via AFP
It was originally formatted via a Windows machine and I reformatted it to EXT3 via Frontview
USB disk is 2TB

[mdgm]

Under Volumes > USB Storage in Frontview, disconnect the USB disk, then disconnect the USB disk reboot the NAS and connect the USB disk to the NAS again.

[jspeigel]

I disconnected the USB disk via Frontview, then unplugged the USB cord from the NAS, then rebooted the NAS, and reconnected the USB disk. I confirmed that the screen on the front of the NAS confirmed the USB was connected and then used RAIDar to go back into Frontview. The USB still shows in Volumes but not in Shares.

[mdgm]

Very odd.

Do you have any add-ons installed?

If you download your System > Config Backup and extract the zip contents does your /etc/frontview/samba/Shares.conf include mention of the USB disk?

[jspeigel]

No add-ons installed and no mention of USB disk in /etc/frontview/samba/Shares.conf

I had an issue with a back-up folder filling up the whole OS partition (Case#17878027). The level 3 fixed it and when I rebooted it did a rsync from disk 1 to disk 2. I had previously had a backup scheduled (this is the one that caused the problem) so I deleted it and then re-added it but this is now the one that is not working.

[mdgm]

Disconnect the USB disk, then install this add-on: http://www.readynas.com/contributed/ewok/Clean_USB_Storage_0.1-x86.bin

After this add-on installs try connecting the USB disk again. If it still doesn't work, then you should try an OS Re-install: http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu

It's possible that when the OS partition got filled up some things got corrupted and that the OS Re-install "may" fix it. If it doesn't then you may need a level 3 to have another look at the NAS.

[jspeigel]

I ran the add-on and it did clear the USB storage. This did not resolve the problem however.

Unfortunately my readynas refuses to go to a boot menu (I assume it is supposed to say "boot menu") so I will wait for the level 3 help. Thanks for your help -- your ideas were good ones but just didn't work out this time!

[mdgm]

So you followed these instructions exactly?: http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu#ultra_4_ultra_4_plus_pro_4_nv_v2

Powering off unit, pressing and holding reset button on back of the unit (location is indicated in the hardware manual: http://www.readynas.com/docs) using a paperclip, turning NAS on by briefly pressing the power button, continuing to hold reset button until you see the boot menu message on the screen?

[jspeigel]

yep -- it never says "boot menu". It just says "booting..." and then boots all the way through. I had run into the same issue with Case#17878027 and researched around to see if others had problems getting to the boot menu. I read enough about human errors to make sure to follow the steps carefully but it just never works.

[mdgm]

Does sound like there's something wrong with your unit. You should definitely be able to access the boot menu. Sounds like there may be a problem with the flash. Support may have a suggestion that may address this.