Member Avatar for HoWS

I get error as below when I tried to start my Linux server.

/data contains a file system with errors, check forced.
Error reading block 77000497(Attempt to read block from
file system resulted in short read) while doing inode scan.

/data: UNEXPECTED INCONSISTENCY; RUN fsck manually.
(i.e.; without -a or -p options)
[FAILED]
***An error occured during the file system check.
*** Dropping you to a shell; the system will reboot
***When you leave the shell.
Give root password for maintenance
(or type Control-D for normal startup):


I need advise on this in order to get my Linux server to run

  • 3 Contributors
  • 2 Replies
  • 648 Views
  • 5 Years Discussion Span
  • Latest Post Latest Post by kupolati

Dani AI

Generated

The failure you saw (kernel "short read" while scanning inodes) means the block device behind /data could not deliver a full block — most commonly an I/O error, bad sectors, or a controller/cable problem rather than a purely logical filesystem bug. provided the error output and correctly pointed out that a manual repair is required; below is a safer, more complete workflow and diagnostic checklist to follow before and during repair.

Do not attempt destructive repairs on a mounted filesystem. First confirm which block device corresponds to /data and inspect recent kernel messages; useful commands to run from the maintenance shell or a rescue environment are:

lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINT
blkid
cat /etc/fstab
dmesg | tail -n 50

If /data cannot be unmounted (for example, it lives on the root disk) boot a rescue/live image so the device is offline. Then run the filesystem-specific repair tool for the device node (use the tool appropriate to your filesystem). Let the tool fix inconsistencies, but avoid "aggressive" or automated options until you know the device is healthy.

Because "short read" often signals hardware trouble, check device health and preserve data first. Inspect kernel logs for I/O errors, run SMART tests, and if data is critical create an image with a recovery tool before repairs:

dmesg | grep -i -E "error|fail|I/O"
smartctl -a /dev/sdX
smartctl -t long /dev/sdX
ddrescue -f -n /dev/sdX /root/disk-image.img /root/ddrescue.log

If SMART shows failing attributes or imaging reveals many unreadable sectors, replace the disk and restore from backup; filesystem repairs on a failing device will likely recur. The dbus message noted by is a user-level service warning and not the root cause here. Prioritize hardware checks and imaging, then run the appropriate repair on the raw device from an unmounted/rescue environment.

Recommended Answers

All 2 Replies

Member Avatar for alc6379

Go ahead and do what it says to do: Enter in your root password. That will drop you to single-user mode, and then you can run fsck on /data manually by typing fsck /data . When you do that, just say Y or whatever option allows you to fix it. If the drive itself isn't damaged, that should take care of things for you.

Member Avatar for kupolati

this program cannot be started until you start the dbus system service aborting...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.