You never know what you have until is is gone. I just had my first disk failure on my unRaid system. I have kept my system off while I wait for the replacement drive to be delivered (few days). Without my server, I've started to miss my music/movies/files.

 

I was wondering if its ok to access the files while a disk has been removed? Can I copy some movies to a flash/external drive to entertain myself in the mean time?

You can use the unRAID array as normal.  As strange as it sounds you can even read and write to the failed disk - the parity drive will make up for the missing drive.  The only danger is in loosing a second disk before the first one is completely replaced and regenerated.

I'd recommend copying any essential files to a drive on another machine, if you have one available, then powering the unRAID server off.

 

I use my 2TB/12 Watt LinkStation as a "temp drive" -- I mirror commonly used files from my unRAID servers on there so I have them always available even when the unRAID servers are switched off.

I'd recommend copying any essential files to a drive on another machine, if you have one available, then powering the unRAID server off.

 

I use my 2TB/12 Watt LinkStation as a "temp drive" -- I mirror commonly used files from my unRAID servers on there so I have them always available even when the unRAID servers are switched off.

When you think that 99.99% of the PCs out there have no backup at all, and hold all their owner's precious files, and that most people do not find the lack of a second copy, or potential of a hard disk crash from using their PCs.

 

If the disk will arrive in a few days, I'd use the server.  It is as likely to fail from a power surge, while turned off, but still plugged into the well, as any other reason.    If it is the only copy of your precious data, you have other issues to deal with... since unRAID is not a backup solution.  Backups are on another disk and (typically) off-site.

 

I know I would hear about it if my server was off-line for any length of time.  We really depend upon it for music/movies.

When you think that 99.99% of the PCs out there have no backup at all, and hold all their owner's precious files, and that most people do not find the lack of a second copy, or potential of a hard disk crash from using their PCs.

 

Well, I suppose it depends on how valuable the data is. If the data can be easily replaced, fair enough -- but if not, and another drive dies with data you need on it, data recovery can be very expensive -- I've had it done for clients of mine.

 

I've had two drives fail on me within a week -- that was the impetus to build an unRAID server!

When you think that 99.99% of the PCs out there have no backup at all, and hold all their owner's precious files, and that most people do not find the lack of a second copy, or potential of a hard disk crash from using their PCs.

Thanks. I always have a backup plan. I have backup plans for my backup plans (not just with data, but in life). My server is 1:1 rsync'd with off-site drives routinely. It does amaze me how 99.99% of people don't backup their data.

 

I was unaware how unRaid works with a drive missing. Obviously I'm not going to do a parity check until the new drive has been rebuilt, but was just concerned if I was only reading (my samba shares are read-only) from the system that it would not mess up the parity sectors need to rebuild.

 

Just added note: The bad drive has been unassigned and removed from the system.

When you think that 99.99% of the PCs out there have no backup at all, and hold all their owner's precious files, and that most people do not find the lack of a second copy, or potential of a hard disk crash from using their PCs.

Thanks. I always have a backup plan. I have backup plans for my backup plans (not just with data, but in life). My server is 1:1 rsync'd with off-site drives routinely. It does amaze me how 99.99% of people don't backup their data.

You are correct in that.  It does amaze me too.

I was unaware how unRaid works with a drive missing. Obviously I'm not going to do a parity check until the new drive has been rebuilt, but was just concerned if I was only reading (my samba shares are read-only) from the system that it would not mess up the parity sectors need to rebuild.

Just be certain to NOT press the button labeled as "restore" (if on an older version of unRAID) or invoke the "initconfig" command.  Those would immediately invalidate your parity ans prevent any re-construction onto the replacement drive.

 

It was not necessary for you to un-assign the failed drive.  It would just show as "Missing" in the display.  unRAID would have recognized when the new drive was installed in its slot just fine.  It really doesn't matter, but you performed a step that was not needed if you are replacing a drive.  It is needed of you had a loose cable, since you would have to get the array to forget the model/serial of the existing drive to get it to use it as its own replacement.

 

Regardless, enjoy your movies.  You can read and write to the "un-assigned" drive until you get the replacement installed.  At that time, the data, including all the "writes" made while it was failed/un-assigned will be re-constructed onto its replacement.

 

To install the replacement, just

Stop the array

Power down

Install the replacement Drive

Power up

Press "Start" to begin the re-construction of the old data onto the new drive. (You may need to check the "I'm sure" box to enable the "Start" button)

 

As I said, do NOT press the button labeled as "restore" (if it exists on your version of unRAID) as it is poorly labeled and is actually a "Set Initial Configuration and Immediately Invalidate Parity based on any prior Configuration" button.

 

Just a follow up. I hooked up the new drive. When I rebooted, I was asked on the main unRaid page if I want to re-construct the data. I did not preclear the disk. Many many hours later, the process was complete. When I looked at the disk it looked like some stuff was missing. I simply rebooted and all was just as I left it.

 

Thanks unRaid. My first disk failure left me with NO missing data.