Tag: fsck

Categories
Knowledge Support Support exacqVision Server exacqVision Hardware

exacqVision Input/Output, Media, or Write Errors

Description 

Meaning of Input/Output Errors, Media Errors, or Write Errors seen in Storage or exacqVision logs.

Product 

exacqVision Server

Information

These messages are normally due to a corrupted filesystem or bad blocks on the disk(s).

Solution

Run ‘chkdsk’ or ‘fsck’.

If problem returns, replace the drive.

<br>

Categories
Knowledge Support Support exacqVision Server exacqVision Hardware

exacqVision Bad Superblock Message

Description 

Meaning Bad Superblock message in logs

Product 

exacqVision Server

Information

A superblock is a block of data written at the beginning of a partition that contains metadata about the filesystem. If this block becomes corrupted, a ‘Bad Superblock’ message results. 

Solution

There are several backups of this data throughout the hard drive and it can be restored. 

Run ‘chkdsk’ or ‘fsck’ using an alternate superblock.

<br>

Categories
Knowledge Support Support exacqVision Server exacqVision Hardware

ExacqVision CRC Errors

Title

ExacqVision CRC Errors

Description 

Meaning of CRC Errors noted from ExacqVision

Product 

ExacqVision Server

Information

When data is transmitted from one place to another, checksum value is created to ensure the data has not been altered during the process of being sent. If a discrepancy exists, a CRC Error results.

This could result from bad cabling, network interference, registry issues, network storage disconnection, etc. 


Solution

Often resolved by fixing the connection problem, then running ‘chkdsk’ or ‘fsck’. 

The drive is probably fine.

Categories
Knowledge Support Support Categories Products exacqVision Hardware

How to force disk check (fsck) in Linux.

One way to determine if the drive is failing in Linux is to run the following command in the terminal

dmesg | less 

This should give you an error list you can scroll through for read/write errors.  
If you see a problem on a data drive perform the following:

  1. Stop the exacq vision server service
    sudo /etc/init.d/edvrserver stop<br><br>
  2. Unmount the drive that is having trouble
    sudo umount /dev/sdb1<br><br>
  3. Run file system check on that drive
    sudo fsck -f -y /dev/sdb1<br><br>
  4. Reboot the system.

If the problem shows on the master drive you will need to do the following:

  1. Login as the root<br><br>
  2. Change directory to root (/) directory
    cd / <br><br>
  3. Create a file called forcefsck
    touch /forcefsck <br><br>
  4. Now reboot the system
    reboot<br><br>

The system should run the disk check when it boots back up in to the operating system.

Categories
Knowledge Support Support exacqVision Server Categories Products exacqVision Hardware

Manually Checking a Drive for Errors in Linux

Run fsck

On Linux systems, if a disk encounters a filesystem error, the physical drive may still be good but require a file system consistency check. Perform the following steps to attempt to correct this.

If the affected volume is a video storage volume:

  1. Stop the ExacqVision server service. Open a Terminal window and enter:
    sudo service edvrserver stop<br><br>
  2. Unmount the volume:
    sudo umount /mnt/edvr/X

    Replace the ‘X’ with your volume number.
    Example: If you have a write error on /mnt/edvr/2, you would enter:
    sudo umount /mnt/edvr/2

    NOTE: If this command fails, see Appendix below.<br><br>
  3. Run fsck on this volume, again replacing ‘X’ with the volume number:
    sudo fsck -yv /mnt/edvr/X

    This command will tell the system to automatically attempt to fix any issues it encounters. This may take minutes or several hours depending on the number of filesystem errors and the size of the volume. When completed, the Terminal will return to a prompt awaiting a new command. <br><br>
  4. When you have run fsck on all the affected storage volumes, reboot the system by entering:
    reboot

    OR

    Return to the Desktop and use the power icon to restart the machine. The drives will remount upon boot up.<br>br>

<br>

Appendix

If drive fails to unmount, you will need to open the fstab file and comment out the mount point of the drive in question.
sudo gedit /etc/fstab

  1. You will need to place a ‘#‘ character to the left of ‘Label=/mnt/edvr/X’
  2. Save
  3. Reboot the machine.
  4. The drive that was commented out should not be mounted at this point.

Continue with step 3 above.
Reminder: Do not forget to re-edit the fstab after the fsck is finished and remove the # you added.

<br>

What does fsck do?

The fsck command performs a consistency check and attempts to repair the filesystem from errors.

What causes filesystem errors?

When system processes or user activity require saving data or making changes to the filesystem, that data is first written to a buffer in memory (RAM). The system periodically moves the data waiting in the buffer to the hard disk. Therefore, at any moment, there is a difference between file changes waiting to be written to disk and what exists on the disks.

Filesystem errors and inconsistencies can develop due to hardware degradation, system halts, or unclean shutdowns. Sudden power loss and forced shutdowns occurring before the changes in the buffer are moved to permanent disk storage.

Components checked by fsck

Inodes
Inodes contain metadata about a file, which includes information like: whether the file is read/write or read-only, the type of file, the user ID of the file owner, file creation and modification date and time, and the number of bytes in the file.

Data Blocks
These contain the data that actually makes up the file.

Superblocks
The superblock contains details about the filesystem, such as the state of the filesystem, the filesystem size, the filesystem name and volume name(s), path name of the mount point, and number of inodes. Every change to the inodes also requires changes to the superblock.

<br>