I just had a power down in my house wich caused the server to shut down, when i rebooted i went to //tower but most of my hard drives said: unformatted. That really freaked me out! However, after a few minutes everything went back to normal.

 

But now my question is, is this safe/normal? Since i'm only using unraid for my movies and a parity for back ups i want to take minimum risks.

This is normal, I think its just as the drives are remounted etc on startup. Just make sure your parity check is up to date and regular.

I just had a power down in my house wich caused the server to shut down, when i rebooted i went to //tower but most of my hard drives said: unformatted. That really freaked me out! However, after a few minutes everything went back to normal.

 

But now my question is, is this safe/normal? Since i'm only using unraid for my movies and a parity for back ups i want to take minimum risks.

when re-started, until the transactions in the file-system journals are replayed and committed to the file-systems, the disks will not be "mounted."  unRAID apparently reports (incorrectly) during this time period that they are unformatted.  

 

It probably should say "mounting disk" or something like that.  If the disks were very active just before the abrupt power down it may take 5 or more minutes to replay the transactions.  Normally this takes only a fraction of a second.  Just be patient when re-starting after a power failure.

 

If you are on unRAID 4.5 consider reporting this as a bug in the 4.5 announcement thread.  (You are the second person to report being confused by the wording)

 

Type

tail -f /var/log/syslog

to see what it is doing.

 

Also. consider getting a UPS.

 

Joe L.

I just had a power down in my house wich caused the server to shut down, when i rebooted i went to //tower but most of my hard drives said: unformatted. That really freaked me out! However, after a few minutes everything went back to normal.

 

But now my question is, is this safe/normal? Since i'm only using unraid for my movies and a parity for back ups i want to take minimum risks.

when re-started, until the transactions in the file-system journals are replayed and committed to the file-systems, the disks will not be "mounted."  unRAID apparently reports (incorrectly) during this time period that they are unformatted.  

 

It probably should say "mounting disk" or something like that.  If the disks were very active just before the abrupt power down it may take 5 or more minutes to replay the transactions.  Normally this takes only a fraction of a second.  Just be patient when re-starting after a power failure.

 

If you are on unRAID 4.5 consider reporting this as a bug in the 4.5 announcement thread.  (You are the second person to report being confused by the wording)

 

Type

tail -f /var/log/syslog

to see what it is doing.

 

Also. consider getting a UPS.

 

Joe L.

 

I have version: 4.5-beta13. I will do a parity check today, i can't type tail -f /var/log/syslog on the server because it's not connected to a monitor. I've been searching for ups like you said, what do you exactly mean? Is that a power thing wich when the power goes off it gets power by battery? Or just a prevention for storms?

 

(sorry for my bad english)

I just had a power down in my house wich caused the server to shut down, when i rebooted i went to //tower but most of my hard drives said: unformatted. That really freaked me out! However, after a few minutes everything went back to normal.

 

But now my question is, is this safe/normal? Since i'm only using unraid for my movies and a parity for back ups i want to take minimum risks.

when re-started, until the transactions in the file-system journals are replayed and committed to the file-systems, the disks will not be "mounted."  unRAID apparently reports (incorrectly) during this time period that they are unformatted.  

 

It probably should say "mounting disk" or something like that.  If the disks were very active just before the abrupt power down it may take 5 or more minutes to replay the transactions.  Normally this takes only a fraction of a second.  Just be patient when re-starting after a power failure.

 

If you are on unRAID 4.5 consider reporting this as a bug in the 4.5 announcement thread.  (You are the second person to report being confused by the wording)

 

Type

tail -f /var/log/syslog

to see what it is doing.

 

Also. consider getting a UPS.

 

Joe L.

 

I have version: 4.5-beta13. I will do a parity check today, i can't type tail -f /var/log/syslog on the server because it's not connected to a monitor.

Then all you can do is shut it down non-gracefully.

I've been searching for ups like you said, what do you exactly mean? Is that a power thing wich when the power goes off it gets power by battery?

Yes.  An Un-interruptable Power Supply.

Or just a prevention for storms?

No, those are surge protectors... they do not supply power when the commercial power is lost.

(sorry for my bad english)

No problem.    Good luck.

 

Joe L.

Allright will hook up a monitor asap to be gracefully

 

Edit: i just typed tail -f /var/log/syslog

 

APR 1 12:15:13 tower shfs: duplicate object: /mnt/disk4/films/the mist.mkv

APR 1 12:15:13 tower shfs: duplicate object: /mnt/disk4/films/max payne.mkv

 

The same message 5 times.

 

I would appreciate it if you could tell me what this means: corrupt files or no problems at all?

 

Thanks

Allright will hook up a monitor asap to be gracefully

 

Edit: i just typed tail -f /var/log/syslog

 

APR 1 12:15:13 tower shfs: duplicate object: /mnt/disk4/films/the mist.mkv

APR 1 12:15:13 tower shfs: duplicate object: /mnt/disk4/films/max payne.mkv

 

The same message 5 times.

 

I would appreciate it if you could tell me what this means: corrupt files or no problems at all?

 

Thanks

It simply indicates you have files with those same exact names in a lower numbered disk.

 

Since only one of the files can be accessible through the user-share of a given name, the first file found with a given name is the one you will see in /mnt/user/films/the mist.mkv and /mntuser/films/max payne.mkv

 

You have a file named:

/mnt/disk1/films/max payme.mkv, or /mnt/disk2/films/max payme.mkv, or /mnt/disk3/films/max payme.mkv

(and the same with the "mist.mkv")

 

Get rid of the duplicate file names (in parallel directories on different disks)  and you will get rid of the messages in your syslog.  They are informational, not corrupt files.  It might indicate you copied a file where you did not intend.

 

Joe L.

Aha! thanks for your reply again, really appreciate this community out here