Notifications
Clear all

Progress indicator for Rebuild?

17 Posts
2 Users
0 Reactions
24.3 K Views
(@pthomsen)
Posts: 9
Member
Topic starter
 

I have gone through the steps to replace a bad drive, and SoftRaid (5.6.5) is saying that my volume is rebuilding, but it's not giving any indication of how long for the rebuild to complete.

I watched this video (skipped to the relevant timestamp): https://www.youtube.com/watch?v=vgwoEIbNEA8&t=309s, and it says that I will get a countdown timer telling me how long before the volume is rebuilt.

Am I missing something, or is this just a (slightly) out-of-date video?

Super-helpful video otherwise!

Thanks in advance!

 
Posted : 20/04/2018 9:58 am
(@softraid-support)
Posts: 9200
Member Admin
 

The volume must be mounted read/write to rebuild.

Perhaps the volume is not mounted?

If you cannot get the volume to mount normally, try Disk Warrior.

 
Posted : 20/04/2018 11:38 am
(@pthomsen)
Posts: 9
Member
Topic starter
 

The volume was mounted, but only in read-only.

I have tried unmounting and re-mounting, but now the volume is saying that it's "waiting for mount" in the volume tile in SoftRaid. See screenshot.

What next? Reboot the machine?

 
Posted : 20/04/2018 12:58 pm
(@pthomsen)
Posts: 9
Member
Topic starter
 

A little more info: I tried using diskwarrior to mount the volume, but it won't mount. Gives error code 4902.

As an aside, while it is attempting to mount, RaidSoft appears to be rebuilding, because the 'offset' increments during the mount attempt.

After the mount fails, the offset stops incrementing again.

Thanks for any help you can give!

 
Posted : 20/04/2018 1:09 pm
(@softraid-support)
Posts: 9200
Member Admin
 

There is some kind of problem with the volume.

restart and run Disk Warrior again. Startup from a "clean" system if necessary.

Until the volume can cleanly mount, the rebuild will not progress.

 
Posted : 20/04/2018 3:07 pm
(@pthomsen)
Posts: 9
Member
Topic starter
 

Still won't mount, except in read-only mode.

When you say 'clean' startup, what do you mean, exactly?

Any other ideas?

 
Posted : 20/04/2018 6:28 pm
(@softraid-support)
Posts: 9200
Member Admin
 

If the volume mounts as "read only" by OS X, it is very surprising that Disk Warrior cannot rebuild the directory.

Outside of doing a backup/erase/restore, contact Alsoft support, they may understand what is going on.

 
Posted : 22/04/2018 12:03 am
(@pthomsen)
Posts: 9
Member
Topic starter
 

Oh, I didn't realize that you thought I should rebuild the directory with DiskWarrior...

Here is what I tried with DiskWarrior: After unmounting the read-only volume, I tried mounting it from within DiskWarrior (also tried to mount from SoftRaid). It wouldn't mount. I got error 4902 from DiskWarrior.

I am currently re-backing up all my files from the volume, in case I need to completely rebuild it. As soon as that is complete, I will attempt a rebuild of the directory in diskWarrior. If that works, and I can mount read-write, I will expect the SoftRAID rebuild to start again.

If any of these steps are wrong, please let me know.

 
Posted : 22/04/2018 1:00 pm
(@softraid-support)
Posts: 9200
Member Admin
 

that is correctly done!

Good luck!

Sometimes it takes a couple tries with Disk Warrior, or a different startup volume but when a volume can mount (even read only), it is rare if Disk Warrior cannot repair it.

Once the volume is OK, the rebuild will proceed.

 
Posted : 23/04/2018 6:13 pm
(@pthomsen)
Posts: 9
Member
Topic starter
 

I think I'm in a chicken-and-egg situation here. I can't fix the directory on the volume with DiskWarrior, unless I start 'clean' which I take to mean boot from the DW recovery partition on the DW thumb drive.

The problem with doing that, is that the thumb drive doesn't have the SoftRAID drivers installed, so DW doesn't see the volume, etc.

If I'm missing something, please let me know.

Otherwise, I need to remove the old volume and recreate it from scratch. Sigh...

 
Posted : 25/04/2018 12:11 pm
(@softraid-support)
Posts: 9200
Member Admin
 

There is no need to startup from the Disk Warrior image. (BTW: the DW boot volume does include the SoftRAID driver, but depending on the age of the version of OSX, it may not be able to mount a SoftRAID volume.)

In any case, try a new OS X install onto any external disk or Thumbdrive.

 
Posted : 25/04/2018 1:34 pm
(@pthomsen)
Posts: 9
Member
Topic starter
 

I don't have a 'clean' OS lying around on a separate disk... If the DW recovery volume should be able to do it, I will try that again. I'll also check the version of the OS that is installed on that volume.

 
Posted : 25/04/2018 3:05 pm
(@softraid-support)
Posts: 9200
Member Admin
 

You should always keep a fresh install of OS X around. Any external disk, or large Thumbdrive can do this. OS X can suddenly decide not to startup, then your options for fixing your problem, or getting quick access to your data is limited. It is a good practice.

 
Posted : 26/04/2018 12:35 pm
(@softraid-support)
Posts: 9200
Member Admin
 

I think I'm in a chicken-and-egg situation here. I can't fix the directory on the volume with DiskWarrior, unless I start 'clean' which I take to mean boot from the DW recovery partition on the DW thumb drive.

The problem with doing that, is that the thumb drive doesn't have the SoftRAID drivers installed, so DW doesn't see the volume, etc.

If I'm missing something, please let me know.

Otherwise, I need to remove the old volume and recreate it from scratch. Sigh...

I do not know how old the system is with a Disk Warrior startup image, but it should be able to see/mount SoftRAID volumes.

 
Posted : 26/04/2018 12:36 pm
(@pthomsen)
Posts: 9
Member
Topic starter
 

The OS is pretty old FYI. The 'About this Mac' menu item is greyed out, so I don't know exactly how old, but the button styles seem like it might be Lion or thereabouts.

Regardless, I tried several times, and wasn't able to get DW to see the Volume, or even the individual disks.

So, I bit the bullet and re-initialized the entire 12TB volume. I'm restoring data back to it now, and it seems to be working fine.

 
Posted : 26/04/2018 1:06 pm
Page 1 / 2
Share:
close
open