AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() I'm just trying to find out what is normal because this will surely come up again at some point. ![]() Support actually told me it could be "up to 48 hours". I also feel that if the plan was for file system check to unmount your volume, it would explicitly tell you this, right? You are going to lose access to your files for an indeterminate amount of time if this is the case. etc/init.d/services.sh stop umount /dev/md0 Once the volume’s unmounted you can stop the volume. Select on the data volume and click Manage button. At the right panel, please click on the storage pool to expand it. Please login QTS web page and go to Control Panel -> System Settings -> Storage Management -> Storage Space. And also, I swear I have run this test multiple times in the past and never seen this happen before. Firstly, make sure there’s nothing going on on the NAS, stop the running services and unmount the RAID device. Click on Check File System button to start the file system check. But that doesn't make sense to me because one of my volumes did not unmount, and the check was completed on that volume. I contacted support, and they told me that when you run the file system check, the volume must unmount to do the check. I thought something was wrong, so I rebooted the NAS and then everything seemed fine. If you consistently encounter any of the following alerts, the disks should be replaced. Run a Bad Block scan on the selected disks. ![]() Identify and select any drives with Warning or Error statuses. Unmount the disks you intend to work on before attempting to check or repair them. And this caused various error messages to appear because the log storage location was set to the volume that had now vanished. Identify the issue Go to Storage & Snapshots > Storage > Disks/VJBOD. You can use fsck to check your file system if your system fails to boot, if files on a specific disk become corrupt, or if an attached drive does not act as expected. My other volume, however, was suddenly unmounted. ![]() On one volume, this happened quickly and completed. I started 'Bad Blocks Scan' for all drives and they all completed successfully. of course, it requested to run the file system check, which I did. But we never had the chance again because the device rebooted itself and the RAID5 logical volume became 'Unmounted', so it wasnt possible to start a filesystem check from the GUI anymore since the 'CHECK NOW' button became inactive. I recently got the warning message about the file system not being clean. ![]()
0 Comments
Read More
Leave a Reply. |