Unmountable : Unsupported or no file system

[spacezmonkey]

Hello, I have an disk error at disk 2 initally  and changed the error disk 2 ( WFP018ZG ). After changing the disk, the system is unable to shutdown and i made a force shutdown to my server. 

 

When the system restart, i am facing this error on disk 1. 

 

 

I have wait until the array to rebuild for my new disk 2 and restart , the error persist. May I know what should I continue to do ?

I have attached a zip copy of diagnostic as well. 

 

On my dashboard, it shows everything is running fine.  Parity is fine, disk 1 and disk 2 are healthy as well. ...

 

 

at the array option, it does show me that i can format disk 2. Should i format the disk ( 1WY10G ) and allow the disk to copy it back from parity? or will a formatted disk write make changes to my parity?

 

homenas-diagnostics-20231014-1112.zip

Edited October 14, 2023 by spacezmonkey

[JorgeB]

Check filesystem on disk1, run it without -n.

[itimpi]

6 hours ago, spacezmonkey said:

Should i format the disk ( 1WY10G ) and allow the disk to copy it back from parity? or will a formatted disk write make changes to my parity?

Whatever you do you must NOT format the disk unless you want to lose all its contents.

[spacezmonkey]

I have start the array in maintenance mode. 

 

click on my affected disk, remove the "-n" and click on check. Error log as displayed below. 

 

 

I think i have to run the xfs_repair using command? 

 

 

[itimpi]

1 hour ago, spacezmonkey said:

I have start the array in maintenance mode. 

 

click on my affected disk, remove the "-n" and click on check. Error log as displayed below. 

 

 

I think i have to run the xfs_repair using command? 

 

 

You need to rerun that check without -n and add -L

[spacezmonkey]

Hello @itimpi thank you for the guide,  i have rerun it without  " -n "  and added  "-L" , however, it still give me an error. 

 

 

secondly, just to confirm, i am running the check with  "maintenance  mode" started.

Edited October 14, 2023 by spacezmonkey

[JorgeB]

It's failing to destroy the log, could the disk capacity be close to fully used?

[spacezmonkey]

I managed to "check " without " -n" and add "-L"  and it managed to complete the process without error.  Now I am able to start the array without any issue and disk is identified as well..  Thank you @JorgeB and @itimpi . It is working well as shown below and I am very glad of your kind assistance. 

 

 

However, I am facing another issue now. My docker containers that was installed previously has disappeared.  

 

 

However, i am still able to see icons of docker that i had installed using "docker-compose" on "Dashboard" page. Is there any method for me to see all my previous installed docker?

 

[JorgeB]

17 minutes ago, spacezmonkey said:

However, i am still able to see icons of docker that i had installed using "docker-compose" on "Dashboard" page.

Probably can't help with that as I never used docker composer, but it's just the on dasboard? Do they show up on the docker page?

[spacezmonkey]

nope..it does not show up in docker page. Anyway i am reinstalling all the docker. Since harddisk is working well, my previous setting for docker containers can be retrieve easily. 

 

Thank you once again for your help.