FreeNas System Alert

[BigDave]

It's hard to know exactly what to do, to address this really strange situation with the DOM
showing one boot environment taking up so much room on the device. Users have not
been reporting problems of this nature with Solid State boot devices AFAIK.

I will caution you to take the following advice with a grain of salt, and before going further,
would recommend you wait for more opinions as to what might be going on here.

I would be comfortable with first performing a long smart test on the DOM as it's SMART
capable. This should not harm the device, and will rule out basic issues or problems.

Next, I would use a utility program to return the device back to a factory default condition.
You can choose what ever software you have experience with or what comes recommended
by the members here. If you are a Windows user, personally, I like DiskPart.
The directions in the linked post are pretty straight forward and easy to follow if you are
comfortable with the command line in Windows. Maybe a forum member can direct you
in how you could do this within FreeNAS making it unnecessary to remove the DOM to
a seperate machine

Once the DOM's current partion has been removed, try a fresh install of FreeNAS without
having any hard disks hooked up (just remove the data cables) and then boot up the new
instance and see if the capacity of the DOM has been corrected.

If any of you other guys and gals in here can help with this, RemyZ and I would be greatful.

 

[RemyZ]

Appreciate all your efforts. Listed a timeline below to help put things into perspective.
Can a long smart test be performed on the Dom within the Freenas gui ? doesn't seem like I can do this

Timeline
1.) Installed FreeNas/Setup Datasets
2.) Played with Permissions and Plex Media Server and was working
3) Tried to make the setup easier to allow for guest access and changed some things around
4) couldnt get it to work and factory reset FreeNas install 2x from the webgui
5) Afterwards ran into these issues. and thats when I started getting the system alerts

As far as the utility tool I have used it before but would like to format the dom while its inside of my server.
May have to create a bootable format tool and do it there

 

[RemyZ]

Would like to run the long smart test first per your suggestion first....
Then make a bootable image from this
https://falconfour.wordpress.com/2013/03/31/falconfours-ultimate-boot-cd-usb-v4-6-f4ubcd/
Format from CLI or load the miniXP environment just to run discpart

 

[BigDave]

Format from CLI or load the miniXP environment just to run discpart

I'm no expert with this, but I'm betting you can get this done. All you need to do is delete the partition... The data will remain but should have no effect on the reinstallation of FreeNAS.
http://www.freebsd.org/cgi/man.cgi?...=FreeBSD+8.3-RELEASE&arch=default&format=html

 

[RemyZ]

I guess the data will remain until its written over.
I guess a low level format is the best

 

[BigDave]

I guess the data will remain until its written over.
I guess a low level format is the best

Yes, zeroing out the drive will not gain you anything as it pertains to wiping the partion.
Writing zeros (or whatever) just uses up a tiny bit of write cycles, totally unnecessary in this case.

 

[RemyZ]

If a low level format isnt need can I just boot from the FreeNas bootable CD i created and then format from there

 

[BigDave]

The idea is to get rid of the current partition on the DOM, but writing zeros to the entire
drive is not necessary.

So if i'm reading the MAN pages correctly, using the CLI from the secure shell, type the gpart command
destroy -F

From the MAN page;

destroy Destroy the partitioning scheme as implemented by geom geom.

Additional options include:

-F Forced destroying of the partition table even if it
is not empty.

 

[RemyZ]

Thanks for clearing that up for me. I see the options below. Is the smart test not an option for the satadomm and is it safe to do this now I have no information that I need to recover

Code:

[root@freenas] ~# gpart
usage: gpart add -t type [-a alignment] [-b start] [-s size] [-i index] [-l label] [-f flags] geom
       gpart backup geom
       gpart bootcode [-b bootcode] [-p partcode -i index] [-f flags] geom
       gpart commit geom
       gpart create -s scheme [-n entries] [-f flags] provider
       gpart delete -i index [-f flags] geom
       gpart destroy [-F] [-f flags] geom
       gpart modify -i index [-l label] [-t type] [-f flags] geom
       gpart set -a attrib [-i index] [-f flags] geom
       gpart show [-l | -r] [-p] [geom ...]
       gpart undo geom
       gpart unset -a attrib [-i index] [-f flags] geom
       gpart resize -i index [-a alignment] [-s size] [-f flags] geom
       gpart restore [-lF] [-f flags] provider [...]
       gpart recover [-f flags] geom
       gpart help
       gpart list [-a] [name ...]
       gpart status [-ags] [name ...]
       gpart load [-v]
       gpart unload [-v]

 

[BigDave]

Is the smart test not an option for the satadomm

The long SMART test can be run before or after, at this point I guess it really doesn't matter, but I would run the
test for good measure. For the benefit of others, please post your CLI commands and outputs. Like after destroying
the partition, post the result of > gpart show -l

 

[RemyZ]

Ran into some issues

Code:

[root@freenas] ~# gpart status ada0p1
gpart: No such geom: ada0p1.
[root@freenas] ~# gpart status ada0
  Name  Status  Components
ada0p1      OK  ada0
ada0p2      OK  ada0
[root@freenas] ~# gpart destroy -F ada0
gpart: Device busy
[root@freenas] ~# gpart destroy -F ada1
gpart: arg0 'ada1': Invalid argument
[root@freenas] ~# gpart show -l
=>         34  11721045101  da0  GPT  (5.5T)
           34           94       - free -  (47k)
          128      4194304    1  1  (2.0G)
      4194432  11716850696    2  1  (5.5T)
  11721045128            7       - free -  (3.5k)

=>         34  11721045101  da1  GPT  (5.5T)
           34           94       - free -  (47k)
          128      4194304    1  1  (2.0G)
      4194432  11716850696    2  1  (5.5T)
  11721045128            7       - free -  (3.5k)

=>         34  11721045101  da2  GPT  (5.5T)
           34           94       - free -  (47k)
          128      4194304    1  1  (2.0G)
      4194432  11716850696    2  1  (5.5T)
  11721045128            7       - free -  (3.5k)

=>         34  11721045101  da3  GPT  (5.5T)
           34           94       - free -  (47k)
          128      4194304    1  1  (2.0G)
      4194432  11716850696    2  1  (5.5T)
  11721045128            7       - free -  (3.5k)

=>       34  125045357  ada0  GPT  (59G)
         34       1024     1  1  (512k)
       1058          6        - free -  (3.0k)
       1064  125044320     2  1  (59G)
  125045384          7        - free -  (3.5k)

 

[BigDave]

I'm an idiot, how can we delete a partition thats in use
Perhaps you could try the UBCD you mentioned earlier,
if not, then remove the DOM to another computer.
I'm sorry, I've got too many irons in the fire today.
It may be time to put on another pot of coffee ;)

 

[RemyZ]

Figured as much no worries lol

 

[marcevan]

So to be clear, every time we get an update to our train, we install it, we should double back to the boot tab and delete an existing one?

I would think best practice would be to hold onto the prior 3 boot sets plus the default and current one.

 

[SweetAndLow]

So to be clear, every time we get an update to our train, we install it, we should double back to the boot tab and delete an existing one?

I would think best practice would be to hold onto the prior 3 boot sets plus the default and current one.

You can hold on to as many boot environment your want. It just depends on how much space you have. I currently have 4 boot environment and they only take up 800MB of space. They just use snapshots so you only have to store the differences between each update. Your system just got messed up from something you tried to do, so don't do whatever that was and you can store lots of boot environments.

 

[RemyZ]

Was able to boot from a Freenas CD and destroy the ada0 dataset. I guess I am at the starting point and will definitely look at video setups before moving forward. The good news is that boot volume is healthy and shows a total of 59Gb and only 500mb used at the moment with no 80% alarms

 

[zoomzoom]

Code:

Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SATA SSD
Serial Number:    B45007570B2400105533
Firmware Version: S9FM02.1
User Capacity:    64,023,257,088 bytes [64.0 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      Unknown (0x0008)
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-3 (minor revision not indicated)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Mar  6 08:46:41 2016 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (   30) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (   2) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000a   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       797
12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       74
168 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       0
169 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       40
170 Unknown_Attribute       0x0013   100   100   010    Pre-fail  Always       -       25
173 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       458753
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       1
194 Temperature_Celsius     0x0023   070   070   000    Pre-fail  Always       -       30
196 Reallocated_Event_Count 0x0000   100   100   000    Old_age   Offline      -       0
218 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       0
231 Temperature_Celsius     0x0013   100   100   000    Pre-fail  Always       -       99
233 Media_Wearout_Indicator 0x0013   100   100   000    Pre-fail  Always       -       68900
241 Total_LBAs_Written      0x0012   100   100   000    Old_age   Always       -       59096
242 Total_LBAs_Read         0x0012   100   100   000    Old_age   Always       -       4421
246 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       12380

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

I've never used this type of drive, however doesn't the temp value seem way off (unless it's using F even though it claims C), as 99C is 210.2F which can't be right.

nvm, just realized there's 2 temp listings... Does anyone know why there's two temp listings?

 

[sef]

1. du -kx /
2. beadm list
3. zfs list -r freenas-boot