freeNAS offline

[THE_KINGDOM]

So I get the following emails:

1. starting scrub of pool 'freenas-boot'
2. The boot volume state is ONLINE: One or more devices has experienced an error resulting in data corruption. Applications may be affected.
3.The boot volume state is ONLINE: One or more devices are faulted in response to IO failures.


Now I can't connect to FreeNAS

 

[Fraoch]

Where did you install FreeNAS? On a USB drive? If so, install FreeNAS to another USB drive, looks like the first one has failed. A new installation should auto-import your pool. You can then restore all settings from a backup file.

If you don't have a spare USB drive and have to buy one, buy two and mirror them. This would prevent the problem you just had and you'd still be able to boot.

Your data is probably OK, although you will never be sure because you didn't use ECC RAM.;)

 

[THE_KINGDOM]

But why would the boot drive ever need to be scrubbed??? Makes no sense

 

[SweetAndLow]

Because the boot device uses zfs filesystem, that is why it gets scrubbed.

 

[THE_KINGDOM]

But can't you turn scrubbing off for the boot device? Its only a USB stick.
What about the actual storage drives..? Do they HAVE to undergo scrubbing?

What was the cause of my boot drive failing after a automated scub??

 

[SweetAndLow]

You need to read the documentation.

http://doc.freenas.org/9.3/freenas_storage.html

After that if you still have questions come back.

 

[THE_KINGDOM]

I've read the documentation.

I don't see the point in scrubbing a USB boot drive makes no sense

 

[SweetAndLow]

To know when the USB has corrupt data on it so you can replace it instead of just failing to boot. I don't understand. Why this is an issue. Your USB stick is bad, the scrub told you it was, now you should replace it.

 

[THE_KINGDOM]

It's like a 1 month old USB stick lol....

 

[Rilo Ravestein]

Could be a false alarm. I had it once, 1 day after installing. Formatted reinstalled, never had any trouble with it. (I use mirrored boot usb)

 

[THE_KINGDOM]

Okay well something went wrong here during the scrub, clearly....
Scrubbing large volumes with important data I can understand, but scrubbing a 4-8gb usb boot drive :s
1 month old usb drive certainly has no issues.

So question, can I redo this boot drive and restore the volumes (hard disks)? Are the configuration backups saved to the boot device or the hard drives?

 

[THE_KINGDOM]

Could be a false alarm. I had it once, 1 day after installing. Formatted reinstalled, never had any trouble with it. (I use mirrored boot usb)

So if it was a false alarm surely I should be able to essentially "ignore" it and continue to use this USB stick?

 

[cyberjock]

The definition of "false alarm" is too vague. Here's what you want to know:

1. You *have* lost data in your pool. The warning is tell you that you HAVE lost data. PERIOD. There is no "false alarm" for corrupt data.
2. You need to correct the issue. The first way is to wipe the drive clean and do a fresh install of FreeNAS. Most people would also tell you to not use that USB since it's pretty reasonable that if you had an error before you'll have an error again.
3. Kingston stuff is pretty suspect these days. So if its Kingston I'd get something else.
4. The age of the drive doesn't matter for this. ZFS found an error and knows there is corruption. That's all you need to know to know that you need to take action.

 

[danb35]

1 month old usb drive certainly has no issues.

You seem very certain of this. What is your basis for this certainty? Data on the device is corrupt. Given that, it seems reasonable to conclude that, despite it being only one month old, your USB device is defective. I lost one less than a week old, so it's entirely possible.

The reason you can't get into the system any more is because data has been lost on the boot device. In most cases, if the boot filesystem is corrupt, a system won't work, and that seems to be the case with yours. Replace it, ideally with two devices (so they'll be mirrored, and still work if one fails), upload your config file, and go on your merry way.

 

[Rilo Ravestein]

You are right, my remark was a bit vague. I meant that the drive doesn't necessarely has to be broken. Mine wasn't . I checked the drive, formatted and reinstalled FreeNAS. Haven't had any problems sice.

 

[sremick]

You are right, my remark was a bit vague. I meant that the drive doesn't necessarely has to be broken. Mine wasn't . I checked the drive, formatted and reinstalled FreeNAS. Haven't had any problems sice.

That still doesn't mean your USB drive is ok and isn't failing. If you don't believe me, I'd suggest researching the difference between "catastrophic", "latent" and "upset" electronics failures. And there's very little low-level diagnostics that can take place over a USB connection.

99% of USB flash drives are low-end consumer commodity items with the quality level that comes with that.

 

[Rilo Ravestein]

I believe you. But still i will not replace my usb for this 1 error. First of all, i have mirrored boot drived. if 1 fails again, no biggie, i can still tink about replacing it then. I it were my only boot drive, i could still replace it, import the pool & backed up config file and we're back in business :)

 

[THE_KINGDOM]

hey guys so I just thought I would report back.

So the USB was in fact dead I couldn't reformat it. *Shocked*

I'm guessing that a couple of power outages messed it up, cutting the OS out.

Anyways I've got 2 new USB drives here. Gonna mirror them as advised.

1 question: when I mirror both the USB boot drives do I leave them both connected? And why?

Thanks in advance

 

[danb35]

When you mirror the boot device, yes, you leave both devices connected. That's what a mirror is--two identical filesystems online at the same time, so that if one fails, the other is online with an exact duplicate of the data.