gideva Posted April 30, 2019 Author Share Posted April 30, 2019 7 minutes ago, johnnie.black said: Start the array, disk should mount now. Yesss!!! Disk mounted with no issues and The Parity-Sync/Data rebuilt on Disk 6 is started. Will inform you about the results once the operation is finished (hopefully in a positive way). For the time I would like to thank you all for the great help and the even greater patience! Quote Link to comment
JorgeB Posted April 30, 2019 Share Posted April 30, 2019 If there's are errors or it crawls to a stop grab new diags before rebooting. Quote Link to comment
gideva Posted April 30, 2019 Author Share Posted April 30, 2019 12 minutes ago, johnnie.black said: If there's are errors or it crawls to a stop grab new diags before rebooting. I will for sure (lesson learned...) Quote Link to comment
gideva Posted May 17, 2019 Author Share Posted May 17, 2019 Here we are again... Once again after 2 weeks working fine I have another disk failure! As suggested by johnnie.black I have a diagnostic before I touch the server (I am anyway miles away and I can only access remotely). Here it is... I really hope you can help me guys with this because the failures seems to be endless monstruo-diagnostics-20190517-0655.zip Quote Link to comment
gideva Posted May 17, 2019 Author Share Posted May 17, 2019 One more thing... It is surely a cascade issue. Before the #6 failed and now is #7. I am quite sure that if I fix #7 I will have the same issue on #8 than Quote Link to comment
JorgeB Posted May 17, 2019 Share Posted May 17, 2019 Unfortunately log is spammed with errors like these and nothing else: Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/Backups Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/Documentari Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/Documenti Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/Foto Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/Musica Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/Video Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/appdata Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/domains Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/isos Apr 28 04:40:02 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/system Apr 28 04:40:03 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/Backups Apr 28 04:40:03 Monstruo emhttpd: error: get_fs_sizes, 6302: Input/output error (5): statfs: /mnt/user/Documentari But looking at the disabled disk is appears to be failing big time, you should be able to confirm by running an extended SMART test. Quote Link to comment
gideva Posted May 17, 2019 Author Share Posted May 17, 2019 (edited) I will do the test now. "Unfortunately log is spammed with errors like these and nothing else:" What does it mean? Can I do something in regards? The failure of the disks in a cascade (one after the other and all of them in a couple of months) to what might be related? Any idea? Edited May 17, 2019 by gideva Quote Link to comment
JorgeB Posted May 17, 2019 Share Posted May 17, 2019 45 minutes ago, gideva said: Can I do something in regards? Rebooting will clear it, then check it's no longer spamming. 45 minutes ago, gideva said: Any idea? That appears to be just a normal failing disk, don't remember if the other ones that failed also had bad SMART. Quote Link to comment
gideva Posted May 17, 2019 Author Share Posted May 17, 2019 35 minutes ago, johnnie.black said: Rebooting will clear it, then check it's no longer spamming. That appears to be just a normal failing disk, don't remember if the other ones that failed also had bad SMART. Not really as far as I know... Quote Link to comment
gideva Posted May 17, 2019 Author Share Posted May 17, 2019 36 minutes ago, johnnie.black said: Rebooting will clear it, then check it's no longer spamming. That appears to be just a normal failing disk, don't remember if the other ones that failed also had bad SMART. The weird thing is that if it was a normal failing disk why they are doing it one after the other (5,6,7...) and all of them in about 30 days time? Just coincidence? If it is no bigg deal (I will change the disk and ok, but I am afraid there is something else involved Quote Link to comment
JorgeB Posted May 17, 2019 Share Posted May 17, 2019 35 minutes ago, gideva said: Just coincidence? If the others were OK then most likely yes, this one appears to be just a failing disk. Quote Link to comment
gideva Posted May 17, 2019 Author Share Posted May 17, 2019 5 minutes ago, johnnie.black said: If the others were OK then most likely yes, this one appears to be just a failing disk. Ok if you say so now at lkeast I am not going to look further for a hidden reason... Quote Link to comment
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.
Note: Your post will require moderator approval before it will be visible.