This article describes the issue of the Cannot find file system superblock error message being generated, after the device boots up.
The following error message is generated, when the device boots up:
Cannot find file system superblock 32 is not a file system superblock 28740192 is not a file system superblock ** /dev/ad1s1f LOOK FOR ALTERNATE SUPERBLOCKS? yes SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE -b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8). tunefs: /var: could not read superblock to fill out disk mount: /dev/ad1s1f : Invalid argument WARNING: WARNING: /var mount failed, building emergency /var WARNING: Creating initial configuration...mgd: commit complete Setting initial options: debugger_on_panic=NO debugger_on_break=NO. Starting optional daemons: usbd.
You may be able to re-add the HDD to the boot list by perform the following procedure:
1. Start the shell:
su (if not logged in as root)
2. To view the current boot list, use the following command:
root@m5% sysctl -a | grep bootdevs
3. To re-build the boot list to its normal/proper structure, use the following command:
root@m5% sysctl -w machdep.bootdevs=pcmcia-flash,compact-flash,disk,lan
4. To check if hard drive (disk) has been re-added to the boot list, use the following command:
root@m5% sysctl -a | grep bootdevs
If the disk (HDD) has been successfully re-added to the boot list, then reboot the router and make sure that the HDD (ad1) is in use.
Note: When the boot list is restored to its proper order, you have to reboot the system. If the device is removed again (that is not visible in the output of ‘show system storage’ or ‘df -k’ ), a RMA has to be created for the RE.