Failed FrontView backup, how to fix?

What filesystem is on the USB disk?

I/O errors do suggest there may be a hardware problem with a disk.

Can you send me your logs zip file (see ink in my sig)?

mdgm wrote:
What filesystem is on the USB disk? I/O errors do suggest there may be a hardware problem with a disk. Can you send me your logs zip file (see ink in my sig)?

The USB disk is formatted EXT4.

Agree that I/O suggests hardware, but also thinking there may be something weird going on with permissions. The files in question were created by Carbon Copy Cloner and I've recently had issues with CCC setting file/directory visibility to invisible after the backup job. Mike Bombich's support is excellent and he helped me fix the problem, but I wonder if some residual cruft is messing up FrontView.

Zip file sent. Thanks for your help!

--dhl

Disks do appear to be fine.

I guess if you can successfully backup your data somewhere else you may wish to afterwards try reformatting the USB disk and do a fresh backup to that.

Also your NAS was last factory reset back in 2010. If you can make an up to date backup, do a factory default (wipes all data, settings, everything) and restore your data from backup that could be useful. There have been a number of filesystem improvements since 4.2.11

mdgm wrote:

Disks do appear to be fine. I guess if you can successfully backup your data somewhere else you may wish to afterwards try reformatting the USB disk and do a fresh backup to that. Also your NAS was last factory reset back in 2010. If you can make an up to date backup, do a factory default (wipes all data, settings, everything) and restore your data from backup that could be useful. There have been a number of filesystem improvements since 4.2.11

I've backed up and deleted the CCC problem directory from the Pro NAS source. Will run the share backup again tonight and see if it succeeds this time. If it does, then I'll try again after restoring the CCC directory from the backup. Hopefully this will help isolate the source of the problem.

This is probably a good time to get a new 5TB USB HD and just backup the whole C volume. I could then do a Factory Default as you suggest.

This system is actually overdue for a completely new set of upgraded disks as the current 4x2TB set has been running 24/7 since 2010. This is the second of two systems you generously helped my LA partners and I with last January.

The LA system is working well. Mine is in SF and I finally have some funds to buy new disks and a back-up NAS (I'm considering the 314 for longevity rather than a 104). A couple questions re: the current state of 0S6 -

• Will OS6 support greater than 16TB volumes on the 314, either not or in the future?
• What are the current thoughts on OS6 on unsupported legacy hardware like the Pro 6? I've read as much as I can in the forum but am still a bit confused. Since this NAS is used for production, I want to be sure it will be safe.

Any serious downsides at this point? Have the fan/temperature control/UI issues been solved? Any other considerations I should be aware of if I want to go OS6 on the new disk set?

Thanks again,
--dhl

dhl wrote:
This is probably a good time to get a new 5TB USB HD and just backup the whole C volume. I could then do a Factory Default as you suggest. This system is actually overdue for a completely new set of upgraded disks as the current 4x2TB set has been running 24/7 since 2010. This is the second of two systems you generously helped my LA partners and I with last January.

If you're going to get new disks, after you've done the backup, power down and remove the old disks (label order) and do the factory default with the new disks installed. That way if you have a problem you've at least got your old array available to use.

dhl wrote:
The LA system is working well. Mine is in SF and I finally have some funds to buy new disks and a back-up NAS (I'm considering the 314 for longevity rather than a 104). A couple questions re: the current state of 0S6 - • Will OS6 support greater than 16TB volumes on the 314, either not or in the future?

Yes. >16TB volumes are supported on all our models that use x86_64 CPUs including the 314.

dhl wrote:

• What are the current thoughts on OS6 on unsupported legacy hardware like the Pro 6? I've read as much as I can in the forum but am still a bit confused. Since this NAS is used for production, I want to be sure it will be safe. Any serious downsides at this point? Have the fan/temperature control/UI issues been solved? Any other considerations I should be aware of if I want to go OS6 on the new disk set?

There is the support situation, but if you maintain regular backups you can always restore from backup if needed.

It should work well. Fan control should work well now, but if you don't like it you can downgrade back to 4.2.27. This does of course require another factory default (wipes all data, settings, everything).

OS6 on x86_64 hardware (all models with Intel CPUs that are able to run OS6) does have the advantage that you can expand a volume past 16TB so if you need a volume > 16TB on OS6 you don't need to do a factory default with all the drives in place.

mdgm wrote:
If you're going to get new disks, after you've done the backup, power down and remove the old disks (label order) and do the factory default with the new disks installed. That way if you have a problem you've at least got your old array available to use.

Yes, absolutely essential.

mdgm wrote:
Yes. >16TB volumes are supported on all our models that use x86_64 CPUs including the 314.

Great news, I'll go with a 314.

mdgm wrote:

There is the support situation, but if you maintain regular backups you can always restore from backup if needed. It should work well. Fan control should work well now, but if you don't like it you can downgrade back to 4.2.27. This does of course require another factory default (wipes all data, settings, everything). OS6 on x86_64 hardware (all models with Intel CPUs that are able to run OS6) does have the advantage that you can expand a volume past 16TB so if you need a volume > 16TB on OS6 you don't need to do a factory default with all the drives in place.

Excellent, especially as larger disks become available. Sounds like OS6 has come a long way since last year. Glad to hear that. I'll give it a try and report back.

My Pro 6 warranty expired a while ago, but thanks to your and this community's excellent support, it's still running strong. It's a very solid box and I look forward to pushing it even further.

Update:

The backup worked properly after I removed the CCC problem directory from the source. After a bit more testing, I found that the CCC problem directory on the USB destination is corrupt is the source of the I/O error. I tried removing it in terminal but it doesn't delete:

localhost:FCPX Libraries dhl$ sudo rm -r corrupt_folder
Password:
rm: corrupt_folder: Invalid argument
localhost:FCPX Libraries dhl$

I have a support request open with Mike Bombich since CCC is the source of the problem so hopefully he'll be able to help. I think there may be a couple files in the directory with bad visibility or permission flags that are making rm balk.

In any event, the USB drive seems fine for now, but this motivates me to deal with the bigger backup issue I've been putting off this year...

After more tests and some back and forth with Mike from CCC, I've narrowed it down to two corrupt directories inside the directory I want to delete. They throw an I/O error when I touch them in any way.

When I run a Filesystem check on the USB drive from the drop down menu in FrontView, I get a report that there were problems found and corrected. But I'm still unable to delete the corrupt directories.

I'm wondering if fsck would fix the problem? Is there any way to run fsck on the USB drive from terminal? Right now it won't run because the volume is mounted. Is there a command that will unmount /dev/sde1 but leave it attached so I can run fsck?

Thanks!

ReadyNAS_Pro:/USB_HDD_2/Epocrates/production/FCPX Libraries# mount
/dev/md0 on / type ext3 (rw,noatime,nodiratime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
tmpfs on /ramfs type ramfs (rw)
tmpfs on /USB type tmpfs (rw,size=16k)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/c/c on /c type ext4 (rw,noatime,nodiratime,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1)
/c/Production on /home/ftp/Production type bind (rw,bind)
/c/Projects on /home/ftp/Projects type bind (rw,bind)
/c/Transfer on /home/ftp/Transfer type bind (rw,bind)
/dev/sde1 on /USB/USB_HDD_2 type ext4 (rw,noatime,barrier=1,acl)
ReadyNAS_Pro:/USB_HDD_2/Epocrates/production/FCPX Libraries# fsck /dev/sde1
fsck 1.42.12 (29-Aug-2014)
e2fsck 1.42.12 (29-Aug-2014)
/dev/sde1 is mounted.
e2fsck: Cannot continue, aborting.


ReadyNAS_Pro:/USB_HDD_2/Epocrates/production/FCPX Libraries# 

To unmount you would use the umount command

mdgm wrote:
To unmount you would use the umount command

Perfect! ran fsck and corrected the errors. I could then delete the bad folder.

Problem solved! Thank you! :mrgreen: