It happened to me during a powerup after unscheduled shutdown.  Drives showed as "unformatted" while the FS logs were being committed.  (Does that make sense?  That is the best I could do from reading the syslog myself.)  I can post it here if needed.

 

SirWired

Never mind.  I have 4.5 base, not 4.5.3.

It happened to me during a powerup after unscheduled shutdown.  Drives showed as "unformatted" while the FS logs were being committed.  (Does that make sense?  That is the best I could do from reading the syslog myself.)  I can post it here if needed.

 

SirWired

Yes, it makes sense, as the disks are not yet mounted.

 

An un-mounted disk is mis-labeled as un-formatted no matter what the underlying cause.

And as mentioned, it doesn't seem to be tied to a specific release, just that in the latest 4.5.3 it's possibly more prone to be encountered than earlier releases.

And as mentioned, it doesn't seem to be tied to a specific release, just that in the latest 4.5.3 it's possibly more prone to be encountered than earlier releases.

In the prior releases until a given disk's transaction log is replayed, the disk was not yet mounted, and showed as un-formatted.  It was still a invalid description and the format button was incorrectly (and dangerously) displayed, but typically the mount completed by the time the user pressed the "refresh" button on the browser. 

 

In rare cases, it would take as long as 5 or 6 minutes for a disk's transaction journal to be replayed.  I've seen syslogs where it took that long.  In all cases, unless a file-system was corrupt, the disk did eventually mount. A user just had to press refresh after giving the system enough time to complete the mount operation.

 

It is different... in 4.5.3 the disks all fail to mount, and they all fail to mount immediately.

 

Joe L.