It's referring to the rescue log and thinks it's already complete.

 

First make sure that disk 1 is unassigned, then repeat but use a different log name, such as /boot/ddrescue1.log

This is the 10tb sdb disk. Should I just run -L?

 

1 minute ago, Pyro said:

Should I just run -L?

If you already tried mounting the disk with UD and it doens't mount, yes, use -L.

I didn't have the unassigned devices plug until just now. I missed that step, sorry. I can't seem to mount the disk for some reason. The mount button is grayed out, and hovering over it with the mouse doesn't tell me why. Perhaps for the same reason that disk 1 wont mount, being a clone and all?

 

 

tower-diagnostics-20181203-0650.zip

Edited December 3, 20187 yr by Pyro
Diagnostic file just in case

Don't know why there's no option to mount in UD, can't see anything about it on the syslog.

 

Try mounting the disk manually:

mkdir /temp

mount /dev/sdb1 /temp

 

it it mounts unmount with

umount /temp

 

and run xfs_repair, if it fails run xfs_repair -L

 

 

I'm being extra careful on this one because it's so completely out of my range. This is a failure right?

 

 

The next one I should try is:

xfs_repair -L /dev/sdb1

Correct?

2 minutes ago, Pyro said:

This is a failure right?

Yes, but not the expected one, try:

 

mount -t xfs /dev/sdb1 /temp

 

This is what returned

 

OK, this is the expected error, previous error indicates the original disk1 was used before with another filesystem and there are still traces from it, maybe why UD doesn't enable mount, run xfs_repair with -L

 

xfs_repair -vL /dev/sdb1

 

That seems to have worked, but the disk still won't mount in unassigned devices.

 

 

Edited December 3, 20187 yr by Pyro

You can mount it manually, but first were do you intend to copy that data to?

 

I think I have enough space on my desktop hard drive to copy the remaining files over. That's my plan so far. Alternately, I guess I could move them to the 1.5tb Seagate and 1tb HGST 2.5" drive.

Since UD isn't working for that disk it's more complicated to mount and share over lan, though it can be done, but IIRC your plan is to in the end use the current 8TB parity as an array disk and this 10TB as parity correct?

That is correct. That's my final goal. It sounds like you have an idea that'll work better, and I'm all for that.

 

Plan is fine, but you can already starting creating the new array to make things easier to copy, and faster, so there's no need to copy multiples times, so I suggest you do this:

 

-tools -> new config

-assign the 8TB as disk1

-don't remember if you want to keeps current disks 4 and 5, if yes assign them now in the positions you want

-leave parity slot empty

-start the array, format disk1 (check that it's the only unmountable disk if you have other previously used data disks)

-mount the 10TB disk manually with the same command as above, use midnight commander to copy everything to new disk1 (from /temp to /mnt/disk1)

-when done, stop the array, unmount the 10TB disk and assign it as parity, start the array to begin the parity sync.

 

 

 

 

 

 

I need to look up midnight commander yet, but how does everything look so far? The "more filesystems detected" bit seems like I might have missed a step somewhere.

 

Array looks good, to mount the disk you need to use the second command that specifies the filesystem:

 

mount -t xfs /dev/sdb1 /temp

 

Midnigh commander is very easy to use, similar to Norton commander if you ever used that, on the left window browse to /temp and on the right browse to /mnt/disk1, you can use insert to select multiple folders if needed, then F5 to copy.

4 hours ago, johnnie.black said:

Midnigh commander is very easy to use, similar to Norton commander if you ever used that, on the left window browse to /temp and on the right browse to /mnt/disk1, you can use insert to select multiple folders if needed, then F5 to copy.

I feel like an idiot, I can't figure this out. I can navigate to both folders on the correct screens, highlight the folders I want copied, but nothing happens when I hit F5. What am I missing?

 

12 minutes ago, Pyro said:

nothing happens when I hit F5

I noticed that recently when running mc inside a web terminal window. I think the function keys are getting intercepted for some reason. Maybe it's a bug, or maybe it's my browser - it used to work reliably but it was the first time I'd tried it since upgrading to Unraid 6.6.5. In the interest of getting the job done I gave up and opened an ssh session instead and forgot about the problem until you reminded me. You could use the Windows application puTTY to ssh in or use a keyboard and monitor attached to your server. Or maybe try a different browser.

Direct server input worked. Finally seeing the light at the end of this tunnel.

It looks like I've recovered 100% of my data, thanks so much John_M, trurl, and johnnie.black!

 

Now it looks like the only other, less important thing, I have to do is fix the dockers and plugins. Is it a simple matter of putting config files back and seeing if it still boots, or is there another way besides setting them all up again from scratch? For better or worse, I have the OS queued to update next time I restart.

 

11 minutes ago, Pyro said:

It looks like I've recovered 100% of my data, thanks so much John_M, trurl, and johnnie.black!

 

Now it looks like the only other, less important thing, I have to do is fix the dockers and plugins. Is it a simple matter of putting config files back and seeing if it still boots, or is there another way besides setting them all up again from scratch? For better or worse, I have the OS queued to update next time I restart.

 

Did you mention a docker problem earlier in this thread? The screenshot doesn't indicate anything wrong though some are not started. Could you elaborate on what isn't working?

 

It appears you have cache but aren't using it for your system or appdata share. Why not?

20 minutes ago, trurl said:

It appears you have cache but aren't using it for your system or appdata share. Why not?

Odd, it used to be. Looks like it still doing system, but not appdata. I can fix that later.

The docker issue is that they don't show a webui option, and Plex doesn't seem to be working. I should probably just start over, delete the dockers and plugins to start fresh. I've learned a lot since I originally set the system up overa year ago.

Edited December 5, 20187 yr by Pyro

39 minutes ago, Pyro said:

Odd, it used to be. Looks like it still doing system, but not appdata. I can fix that later.

The docker issue is that they don't show a webui option, and Plex doesn't seem to be working. I should probably just start over, delete the dockers and plugins to start fresh. I've learned a lot since I originally set the system up overa year ago.

The last diagnostics you posted say that neither the system share nor the appdata share are set to use cache. If for some reason system is on cache that must have happened when the setting was different. As for fixing it later, I suggest you fix it first before starting over with your dockers.

 

Go to Settings - Docker and disable the Docker service. If you have any VMs disable that service also.

Change the system and appdata user shares to cache-prefer then run Mover, which will move them to cache.

Then you can delete and recreate docker image if you want.

 

It's actually pretty easy to start your dockers (and plugins) over. There is a Previous Apps feature on the Apps page that will reinstall any and all of your apps with the same settings they had before.

 

 

On 12/4/2018 at 9:09 PM, trurl said:

It's actually pretty easy to start your dockers (and plugins) over. There is a Previous Apps feature on the Apps page that will reinstall any and all of your apps with the same settings they had before.

It would be if I hadn't nuked my config, lol. Seems I'm not as sharp as I thought I was. I've been struggling to get the Plex webui to work. (Says connection refused) I updated to 6.6.6, not that it should matter.

 

In any case, the original topic of this conversation is taken care of. I should probably just get back to Google and YouTube to figure out where I went wrong on dockers again.

 

EDIT: I overcomplicated it. Plex seems to be working again.

Edited December 7, 20187 yr by Pyro