Recent Posts

Pages: [1] 2 3 ... 10
1
General Discussion / Re: Advice: 2 weeks and no data, what now?
« Last post by stevatron on April 22, 2017, 07:37:39 pm »
My main concern with #2 was potentially losing all the data on that disk if the restore doesn't go to plan and the parity is recreated with the DRU as being empty.

The idea behind option #3 was to move as much data as possible off my flexRaid implementation without risking further data loss.

Obviously the downside of #3 is that it's more expensive in the short term.

Thanks for your advice - I'm still trying to weigh these up.
2
General Discussion / Re: Advice: 2 weeks and no data, what now?
« Last post by adridolf on April 22, 2017, 06:44:19 am »
What if you tried number 2 and if it does not work, you can still do number 3, can't you?
3
General Discussion / Advice: 2 weeks and no data, what now?
« Last post by stevatron on April 21, 2017, 06:46:31 pm »
It's been over 2 weeks since an attempted restore on my array failed, and in that time I have not gained the confidence (through documentation, or support in this forum) in what action is required to fix this issue and get my array back online.

While this is my home file server, and doesn't require constant uptime, having it offline for 2 weeks (with no strategy to bring it online) is a little past my comfort zone.  So I'm starting to way up my options, and I would love to get your advice/opinions on the matter.

The options I believe I have are:
  • Keep posting slightly more detailed questions on the forum, and hopefully I'll get a response that results in success.
  • Try my luck with what I believe might work, and attempt another restore.
  • Bite the bullet, and go down the Synology path.  Restoring my critical content from an offsite backup and any data I can recover from my HDDs.

The first option is the most ideal, but is proving to be the least likely.
The second option seems the most risky and likely to result in data loss.
The third option is the most predictable, but will result in some data loss (albeit not critical data).

I'm feeling like option 3 is the only one worth pursuing at the moment.
Thoughts?
4
General Discussion / Re: "Last Chance" prompt for data on parity disks
« Last post by Brahim on April 21, 2017, 10:22:42 am »
If you have data on disks you assign to a storage pool as parity disks in Cruise Control mode, you receive a prompt asking if you want to use the existing data as parity data. If you do not choose to use the existing data as parity data, you get a second box labelled "Last Chance" with "Yes" or "No" as options.

Does this mean Yes, use the existing parity data, or Yes, continue with not using the data as parity data? It is not clear to me.

Thank you, for anyone who can enlighten me.
It means the parity data will be erased and re-created.
5
General Discussion / Re: "Last Chance" prompt for data on parity disks
« Last post by eieigoto on April 21, 2017, 01:26:15 am »
the data as parity data? It is not clear to me.
6
General Discussion / Re: Error when restoring dropped disk (error code 1784)
« Last post by stevatron on April 17, 2017, 05:50:37 pm »
Thanks @adridolf and @Brahim

One point that I'm still not certain on - should I restore my drive with "restore into current drive"?  (as per my last screenshot)?
7
General Discussion / Re: Error when restoring dropped disk (error code 1784)
« Last post by Brahim on April 17, 2017, 08:48:55 am »
@stevatron
This is a community forum. So, never address a question to me directly as it prevents others from joining into the topic.

Restoring to a larger disk is fine. The restored volume will not increase to match that of the new disk. Instead it will remain faithful of the original disk. To utilize the full space of the larger disk, you will need to use a partition manager tool to resize the partition.
8
i am still getting some errors in windows events when i do copy/move with traid.
error 153. the IO operation at logical block address ... disk11 was retried.

it doesn't seem serious.  but its always for that disk that i just replaced, and i replaced the cable, too.  it's the only disk giving errors, but i can't figure out why always the same disk.
It is serious. You definitely want to resolve that or you will end up with file system corruption.
9
General Discussion / Re: Error when restoring dropped disk (error code 1784)
« Last post by adridolf on April 17, 2017, 06:42:02 am »
Although I'm not Brahim, I remember several occasions of "only restore to a disk with the same size" in this forum. I would stick to that...
10
General Discussion / Re: Error when restoring dropped disk (error code 1784)
« Last post by stevatron on April 17, 2017, 03:46:53 am »
Brahim - did my last questions to you make sense?

My array is still offline, and I am yet to perform any action on it as I'd prefer not to lose any data.

I'll await your response as I cannot find any documentation to answer my questions.

Thanks.
Pages: [1] 2 3 ... 10