January 22, 201016 yr Good day everyone. I'm in need of some help here as I'm fearing the worst. I have a simple array, 3 disks in total. I recently replaced one of the drives with one of a larger capacity. I brought the system up and started the array causing the rebuild to begin. Everything seemed fine however, post rebuild is showing that 2 of the 3 drives are unformatted. This is not good. I could really use some assistance.
January 22, 201016 yr Not that I can help, but make sure you post a syslog. I have the same general issue as you in that one of my drives is also showing as unformatted, but I cannot determine the cause or how to fix it. This is the link: http://tower/log/syslog Replace "tower" with the name of your server
January 22, 201016 yr Good day everyone. I'm in need of some help here as I'm fearing the worst. I have a simple array, 3 disks in total. I recently replaced one of the drives with one of a larger capacity. I brought the system up and started the array causing the rebuild to begin. Everything seemed fine however, post rebuild is showing that 2 of the 3 drives are unformatted. This is not good. I could really use some assistance. Post a syslog. It is the only way anybody can help other than to say do NOT press a format button. unRAID, when starting, goes through the process of mounting each assigned data disk on its affiliated mount point. Any disk that cannot be mounted is labeled as "Un-Formatted" There are many reasons the "mount" can not occur. The disk is busy replaying transactions from its journal. This process of replaying transactions has been observed to take from a few seconds to over five minutes. All you can do in this situation is to press the "refresh" button on your browser every 30 seconds or so, and wait until the disk is mounted. The reiser file-system on the disk is corrupted in a way where it cannot mount. You must repair it before it will mount using reiserfsck. The disk does not contain any file system, and has never been formatted. (This is one situation where pressing the "Format" button is the correct next step) The disk contains a file-system, but it is not a reiser fs. It is one from a previous use of the drive in another computer. (Again, this might be an occasion to format the disk, assuming of course you intended to reuse the disk in unRAID) In the same way, on versions of unRAID prior to 4.5, it was possible to also see disks as un-formatted when stopping the array. These were incorrectly reported when one of more disks was "busy" (in use, with either an open file, or as the current directory of a process) and is unable to be un-mounted. You would need to terminate the process keeping the disk busy and press "Stop" once more. When this happens the array is unable to stop... however those disks that could be un-mounted, and are already un-mounted, are then incorrectly reported as un-formatted. This is very misleading, as the disks are just not mounted. A fix in one of the last 4.5beta versions corrected this and it now shows "un-mounting" on all the disks until they are all un-mounted. The only way to know what is happening on your server is for you to post a syslog. Joe L.
January 24, 201016 yr Author Thanks for the input, I appreciate the help. I took a deep breath and tried not to panic. Bouncing the server seems to have resolved the issue. All drives are back on line and the new disk is being reported properly. All data seems to be intact. Thanks again.
Archived
This topic is now archived and is closed to further replies.