ggirao Posted August 24, 2013 Report Share Posted August 24, 2013 Hi, I'm running ok several backups, but this one last times started to give me problemas. When doing Scanning the CPU is about 300% and doesnt go beyond 300GB. This backup source has millions of files and usually is the one that the snapshot (even if it is a small diary backup) lasts about 5 hours. What should I Do? 1 Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted August 25, 2013 Report Share Posted August 25, 2013 If it is a Windows client, run CHKDSK on the client. If it is a Mac Client, repair the hard drive on the client. It's probably easiest to do that by a "safe boot" (During boot/startup, hold down shift until you see a progress bar). Then restart the Mac normally. Quote Link to comment Share on other sites More sharing options...
ggirao Posted August 26, 2013 Author Report Share Posted August 26, 2013 It is a Mac Client, but has it is a RAID with it's "own SO" (LaCie) I cannot repair hard drive. This has only data, not a Mac OS X. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted August 26, 2013 Report Share Posted August 26, 2013 You should be able to repair the disk directory using Apple's Disk Utility, even RAID disks. You don't even have to reboot the computer and do a safe boot for that! Quote Link to comment Share on other sites More sharing options...
ggirao Posted August 27, 2013 Author Report Share Posted August 27, 2013 I did that once and what i got was damaged disk, with read-only acess. I Don't risk do it again... I will restart my RAID and server. EDIT - this disk has maximum 4 months old .... Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted August 27, 2013 Report Share Posted August 27, 2013 I did that once and what i got was damaged disk, with read-only acess. I Don't risk do it again... That was most likely caused by a buggy RAID system, not by Disk Utility. Quote Link to comment Share on other sites More sharing options...
Daniels Posted August 27, 2013 Report Share Posted August 27, 2013 Have you tried a product called Disk Warrior? Quote Link to comment Share on other sites More sharing options...
ggirao Posted August 28, 2013 Author Report Share Posted August 28, 2013 I Dont think it is a problem with disk errors... This because i added a new favorite folder on same Disk and it was very quick! Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted August 28, 2013 Report Share Posted August 28, 2013 I still think it is a problem with the disk directory. The problem is outside the favorite folder you just added. Quote Link to comment Share on other sites More sharing options...
ggirao Posted August 28, 2013 Author Report Share Posted August 28, 2013 I will keep the verify disk to my very last option. Today I will: - Shutdown server where disk is; - Restart or even shutdown RAID Controller (The disk it self); - Propagate Permissions and ACLs on Server Admin for that Share (reminding that retro will backup all over again - the BUG) If that doesnt work, I have to think on that option. Quote Link to comment Share on other sites More sharing options...
prl Posted August 28, 2013 Report Share Posted August 28, 2013 I will keep the verify disk to my very last option.... Why? It's simple and doesn't take particularly long (it checks/repairs the file system's internal data structures, not every block on the device). If you click on the Verify Disk button in DiskUtility>First Aid for the volume it will check the disk's file system without attempting any repairs. Repair Disk will check the disk and attempt to repair its file system. Quote Link to comment Share on other sites More sharing options...
ggirao Posted August 28, 2013 Author Report Share Posted August 28, 2013 Have you tried a product called Disk Warrior? I'm contacting Alsoft to know specs. TY Quote Link to comment Share on other sites More sharing options...
ggirao Posted August 28, 2013 Author Report Share Posted August 28, 2013 Why? It's simple and doesn't take particularly long (it checks/repairs the file system's internal data structures, not every block on the device). If you click on the Verify Disk button in DiskUtility>First Aid for the volume it will check the disk's file system without attempting any repairs. Repair Disk will check the disk and attempt to repair its file system. Yes it's simple... but check my comment: "I did that once and what i got was damaged disk, with read-only acess. I Don't risk do it again..." Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted August 28, 2013 Report Share Posted August 28, 2013 I will keep the verify disk to my very last option. Today I will: - Shutdown server where disk is; - Restart or even shutdown RAID Controller (The disk it self); - Propagate Permissions and ACLs on Server Admin for that Share (reminding that retro will backup all over again - the BUG) If that doesnt work, I have to think on that option. Uncheck: Yes it's simple... but check my comment: "I did that once and what i got was damaged disk, with read-only acess. I Don't risk do it again..." Select "Verify", not "Repair", to avoid trying to make changes. Also see my comment above. Quote Link to comment Share on other sites More sharing options...
ggirao Posted August 28, 2013 Author Report Share Posted August 28, 2013 I've done it! One guy added a folder to this share without the right permissions... GRRRRRR I Moved the folder to other side, and voilá! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.