Question about state after a power loss

[hominamad]

Hi all - I'm currently running Freenas version 0.7.2 Sabanda (revision 5543).

It's been running for months now with absolutely zero problems. We had a big electrical storm and lost power for an hour last week and I unplugged the computer and left it off for a few days. When I went to turn it back on today, it came up fine, but after about a minute or two, the file system became slow to the point that it was inaccessible. I also noticed the hard drive light of the box was permanently lit up.

Meanwhile, I have no problem getting into the web interface. I checked out the logs and statuses of various things, but I am new to FreeBSD and am not sure what to look for. The one thing I did notice was that fsck_ufs process has been running for a while.

I did some research and think that this is some kind of disk checking utility that runs after an abnormal shut down. Is this correct and expected behavior after an event such as this?

Should I just let it run? Any info would be greatly appreciated.

Thanks,

H

PS If it is helpful to post log files or snapshots of the running processes I can provide. Below is the latest log in any case:

Date & Time User Event
Sep 10 20:57:08 freenas kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_PR_.CPU1._OSC] (Node 0xffffff000d46d3a0), AE_ALREADY_EXISTS
Sep 10 20:57:08 freenas kernel: coretemp1: <CPU On-Die Thermal Sensors> on cpu1
Sep 10 20:57:08 freenas kernel: est1: <Enhanced SpeedStep Frequency Control> on cpu1
Sep 10 20:57:08 freenas kernel: p4tcc1: <CPU Frequency Thermal Control> on cpu1
Sep 10 20:57:08 freenas kernel: acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Sep 10 20:57:08 freenas kernel: device_attach: acpi_hpet0 attach returned 12
Sep 10 20:57:08 freenas kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
Sep 10 20:57:08 freenas kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Sep 10 20:57:08 freenas kernel: kbd0 at atkbd0
Sep 10 20:57:08 freenas kernel: atkbd0: [GIANT-LOCKED]
Sep 10 20:57:08 freenas kernel: atkbd0: [ITHREAD]
Sep 10 20:57:08 freenas kernel: ppc0: cannot reserve I/O port range
Sep 10 20:57:08 freenas kernel: sc0: <System console> at flags 0x100 on isa0
Sep 10 20:57:08 freenas kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Sep 10 20:57:08 freenas kernel: sio1: configured irq 3 not in bitmap of probed irqs 0
Sep 10 20:57:08 freenas kernel: sio1: port may not be enabled
Sep 10 20:57:08 freenas kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Sep 10 20:57:08 freenas kernel: Timecounters tick every 1.000 msec
Sep 10 20:57:08 freenas kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to accept, logging limited to 5 packets/entry by default
Sep 10 20:57:08 freenas kernel: iSCSI boot driver version 0.1.3
Sep 10 20:57:08 freenas kernel: md0: Preloaded image </mfsroot> 188743680 bytes at 0xffffffff80db7fe8
Sep 10 20:57:08 freenas kernel: ad4: 1907729MB <WDC WD20EARS-00MVWB0 51.0AB51> at ata2-master SATA150
Sep 10 20:57:08 freenas kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
Sep 10 20:57:08 freenas kernel: (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Sep 10 20:57:08 freenas kernel: (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
Sep 10 20:57:08 freenas kernel: (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
Sep 10 20:57:08 freenas kernel: (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
Sep 10 20:57:08 freenas kernel: (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
Sep 10 20:57:08 freenas kernel: SMP: AP CPU #1 Launched!
Sep 10 20:57:08 freenas kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Sep 10 20:57:08 freenas kernel: da0: <JetFlash Transcend 8GB 8.07> Removable Direct Access SCSI-2 device
Sep 10 20:57:08 freenas kernel: da0: 40.000MB/s transfers
Sep 10 20:57:08 freenas kernel: da0: 7660MB (15687680 512 byte sectors: 255H 63S/T 976C)
Sep 10 20:57:08 freenas kernel: Trying to mount root from ufs:/dev/md0
Sep 10 20:57:08 freenas kernel: WARNING: /mnt/MountPoint was not properly dismounted
Sep 10 20:57:09 freenas lighttpd[1713]: (log.c.166) server started
Sep 10 20:57:09 freenas login: login on ttyv0 as root
Sep 10 20:57:32 freenas nmbd[1566]: [2011/09/10 20:57:32.218885, 0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
Sep 10 20:57:32 freenas nmbd[1566]: *****
Sep 10 20:57:32 freenas nmbd[1566]:
Sep 10 20:57:32 freenas nmbd[1566]: Samba name server FREENAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.4
Sep 10 20:57:32 freenas nmbd[1566]:
Sep 10 20:57:32 freenas nmbd[1566]: *****
Sep 10 20:58:01 freenas kernel: This module (opensolaris) contains code covered by the
Sep 10 20:58:01 freenas kernel: Common Development and Distribution License (CDDL)
Sep 10 20:58:01 freenas kernel: see http://opensolaris.org/os/licensing/opensolaris_license/
Sep 10 20:58:01 freenas kernel: WARNING: ZFS is considered to be an experimental feature in FreeBSD.
Sep 10 20:58:01 freenas kernel: ZFS filesystem version 3
Sep 10 20:58:01 freenas kernel: ZFS storage pool version 13
Sep 10 21:00:12 freenas lighttpd[1713]: (connections.c.137) (warning) close: 9 Socket is not connected

 

[survive]

Hi hominamad,

Assuming your volume is UFS, if the system wasn't shutdown properly it will want to check it's volumes and make sure everything is ok. fsck_ufs is the process that does this. Just let it do it's thing and it should complete in a little while.

-Will

 

[hominamad]

Thanks Will. When it is finished should that process go away?

 

[ProtoSD]

hominamad - These forums are for FreeNAS version 8.x, there is a link in the title bar at the top of the page. In the future please post FreeNAS version .7 questions there.

To answer your question, that process should go away after it finishes checking your disks.