A power outage can, in rare cases cause file system corruption to the wireless controller. If file system corruption occurs, the controller might not be able to start up and provide service. This section describes how to recover the controller in such a situation.
To recover the controller from file system corruption:
INIT: version 2.86 booting Starting the hotplug events dispatcher: udevd. Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated...done. Mounting readonly root filesystem...done. Checking root file system...fsck 1.40 (29-Jun-2007) /dev/hda2 has gone 14817 days without being checked, check forced. Inodes that were part of a corrupted orphan linked list found. /dev/hda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.(i.e., without -a or -p options) fsck failed (exit code 4). Please repair manually and reboot. Please note that the root file system is currently mounted read-only. To remount it read-write: # mount -n -o remount,rw / CONTROL-D will exit from this shell and REBOOT the system. Give root password for maintenance (or type Control-D to continue):
bash-3.00# fsck.ext3 -fycv /dev/hda2
e2fsck 1.40 (29-Jun-2007) Checking for bad blocks (read-only test): done Pass 1: Checking inodes, blocks, and sizes Inodes that were part of a corrupted orphan linked list found. Fix? yes Inode 17765 was part of the orphaned inode list. FIXED. Inode 17786 was part of the orphaned inode list. FIXED. Inode 64432 was part of the orphaned inode list. FIXED. Inode 64433 was part of the orphaned inode list. FIXED. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/hda2: ***** FILE SYSTEM WAS MODIFIED ***** /dev/hda2: ***** REBOOT LINUX ***** 12087 inodes used (15.61%) 83 non-contiguous inodes (0.7%) # of inodes with ind/dind/tind blocks: 636/5/0 83316 blocks used (53.88%) 0 bad blocks 0 large files 10967 regular files 742 directories 2 character device files 0 block device files 6 fifos 1418 links 359 symbolic links (359 fast symbolic links) 2 sockets -------- 13496 files bash-3.00# reboot
Following the reboot, the wireless controller should proceed with the normal startup.