comfox Posted July 4, 2018 Share Posted July 4, 2018 Hi there, I just rebooted the array and it came up saying Disk 5 is Unmountable: No Filesystem. I am currently running xfs_repair -v I have attached my tower-diagnostics tower-diagnostics-20180704-1155.zip Link to comment
JorgeB Posted July 4, 2018 Share Posted July 4, 2018 You're already doing what needs to be done, assuming your doing it on the mdX device (or using the GUI). Link to comment
comfox Posted July 4, 2018 Author Share Posted July 4, 2018 Thanks @johnnie.black for the quick response. I did that and the output said I should try -L. I did xfs_repair -L /dev/md5 and it completed successfully. I then stopped and started the array and the drive was picked back up. Does this mean this drive is dead or should it bee good to go for a while? Should I run a parity check now as well? Link to comment
JorgeB Posted July 4, 2018 Share Posted July 4, 2018 18 minutes ago, comfox said: Does this mean this drive is dead or should it bee good to go for a while? Filesystem corruption and drive health are two different things, SMART looks OK so disk should be fine. Link to comment
sonata31380 Posted July 10, 2018 Share Posted July 10, 2018 Hello I am faced with the following problem My unRAID server crashed due to a hardware failure on the motherboard So I realize a new configuration with a new motherboard After starting unRAID there was a Parity Check of the Array which normal My problem: one of the disks displays the message "Unmountable No file system" Nevertheless the disc is not in error: during the Parity check it was read like the other disks So I stopped the Array and restarted it in maintenance mode Then in the terminal I typed the command: xfs_repair -v / dev / md9 I got the following message I then typed the following command xfs_repair -v -L / dev / md9 I got the following message Is the next step formatting the disk as shown in the message: In this case will the disk be rebuilt from the Parity disk? Thanks for your help Louis hcsrv1-diagnostics-20180710-1743.zip Link to comment
JorgeB Posted July 10, 2018 Share Posted July 10, 2018 25 minutes ago, sonata31380 said: In this case will the disk be rebuilt from the Parity disk? No, formatting will delete all data and update parity accordingly. There seems to be a problem with that disk since no SMART data is displayed, there are also various timeout errors on the SASLP, that controller is not recommend for current unRAID since it can cause issue with the disks connected. The current problem may not have anything to do with the above, but to rule out controller issues, and since disk9 is connected on the SASLP swap SATA cable with a disk connected on the onboard controller and run xfs_repair again, if it still fails post new diags. Link to comment
sonata31380 Posted July 10, 2018 Share Posted July 10, 2018 22 minutes ago, johnnie.black said: .... there are also various timeout errors on the SASLP, that controller is not recommend for current unRAID since it can cause issue with the disks connected ... HelloThank you for your replyIn case the controller is in question what other product do you recommend with 8 ports?Louis Link to comment
JorgeB Posted July 10, 2018 Share Posted July 10, 2018 12 minutes ago, sonata31380 said: In case the controller is in question what other product do you recommend with 8 ports? Any LSI with a SAS2008/2308/3008 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed. Link to comment
sonata31380 Posted July 10, 2018 Share Posted July 10, 2018 This model ? LSI SAS 9211-8i Link to comment
JorgeB Posted July 10, 2018 Share Posted July 10, 2018 Yes This model ?LSI SAS 9211-8i Link to comment
sonata31380 Posted July 10, 2018 Share Posted July 10, 2018 Looking at the log file we actually see a lot of error in the controller sata cardSo I decided to change it and I ordered for a LSI SAS 9211-8iIf after this change I still have problems with the disk, by removing the disk partition outside the unRAID server, will this disk be considered a replacement and the array will be rebuilt?Thanks for your helpLouis Link to comment
JorgeB Posted July 10, 2018 Share Posted July 10, 2018 Parity can't help with file system corruption, it could have possibly helped after the crash/shutdown, but you did a correcting check after so now an emulated or rebuilt disk will have the same issues as the current one. Link to comment
sonata31380 Posted July 10, 2018 Share Posted July 10, 2018 What will be the best solution without data loss? Link to comment
JorgeB Posted July 10, 2018 Share Posted July 10, 2018 8 hours ago, johnnie.black said: The current problem may not have anything to do with the above, but to rule out controller issues, and since disk9 is connected on the SASLP swap SATA cable with a disk connected on the onboard controller and run xfs_repair again, if it still fails post new diags. Link to comment
sonata31380 Posted July 10, 2018 Share Posted July 10, 2018 So, no solution, even installing a new drive?Yet the principle of Raid is to reconstruct the loss of a disk? Link to comment
JorgeB Posted July 10, 2018 Share Posted July 10, 2018 Just now, sonata31380 said: Yet the principle of Raid is to reconstruct the loss of a disk? Yes, if a disk fails, it can't protect you in case of filesystem corruption. Link to comment
pwm Posted July 10, 2018 Share Posted July 10, 2018 1 minute ago, sonata31380 said: So, no solution, even installing a new drive?Yet the principle of Raid is to reconstruct the loss of a disk? It is. But it will reconstruct to the state it was it when the parity was generated. And it depends on the drives and controller cards to be trustworthy. Link to comment
JorgeB Posted July 10, 2018 Share Posted July 10, 2018 And let me just mention again it could be a disk problem, and in that case a rebuild (or trying it on the emulated disk) could work, since the way xfs_repair is aborting is consisting with a problem accessing the disk, same for the lack of SMART information, so it might be controller related, it might be the disk. Link to comment
sonata31380 Posted July 10, 2018 Share Posted July 10, 2018 I admit I do not understandThe principle of the raid is to be able to rebuild a disk in case of problemFrom the parity disk and the other disks we must be able to reconstruct a diskWhen we change a disk for another, it recovers the data of the previous oneA priori the parity disk is built from sectors and not from the file system, the latter is only used to access files through samba or nfsWe see on the following image that my disk 9 was read without error for the parity check : the disk is ok Why then if I put a new disc, this one will not recover the data of the disc which it replaces, since this new disc will be first formatted in xfs? Link to comment
JorgeB Posted July 10, 2018 Share Posted July 10, 2018 2 minutes ago, sonata31380 said: Why then if I put a new disc, this one will not recover the data of the disc which it replaces, since this new disc will be first formatted in xfs? If the problem is the disk or the controller, replacing either will fix the problem, if it's really a corrupt filesystem rebuilding will rebuild an exact byte by byte copy of the current disk, including the existing file system corruption. Link to comment
sonata31380 Posted July 10, 2018 Share Posted July 10, 2018 I will wait to receive my new sata controller card and see if the problem comes from the diskThank you again for your helpLouis Link to comment
sonata31380 Posted July 13, 2018 Share Posted July 13, 2018 HelloIn case I could not get my disk with unRAID, could I do it with UFS Explorer?If so, which version?Thank youLouis Link to comment
JorgeB Posted July 13, 2018 Share Posted July 13, 2018 14 minutes ago, sonata31380 said: In case I could not get my disk with unRAID, could I do it with UFS Explorer? Easier to use another Linux distro, e.g. you can boot with a Ubuntu live flash drive Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.