Suse Linux ES 10 failed to start properly by giving the message : fsck failed for at least one filesystem (not /) Please re[pair manually a
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Suse Linux ES 10 failed to start properly by giving the message : fsck failed for at least one filesystem (not /) Please re[pair manually a
error on stat() /dev/disk/by-id/scsi-3600a0b80002947900000070ac80d-part1:No such file or directory
error on stat() /dev/disk/by-id/scsi-3600a0b80002946b4000009f 1473ac664-part1:No such file or directory
ailed to open the device '/dev/disk/by-id/scsi-3600a0b80002947900000070a473ac80d-part1' : No such file or Directory
fsck.reiserfs /dev/disk/ by-id/scsi-3600a0b80002947900000070ac80d-part1 failed (status 0x8) , Run Manually!
error on stat() /dev/disk/by-id/scsi-3600a0b80002946b4000009f 1473ac664-part1:No such file or directory
error on stat() /dev/disk/by-id/scsi-3600a0b80002946b4000009f 1473ac664-part1:No such file or directory
Failed to open the device '/dev/disk/by-id/scsi-3600a0b80002946b4000009f 1473ac664-part1:No such file or directory
fsck.reiserfs /dev/disk/by-id/scsi-3600a0b80002946b4000009f 1473ac664-part1 failed (status 0x8) , Run Manually! failed
blogd: no message logging because /var file system is not accessible
reiserFS: sda2: warning: clm-2200: last commit 2584286457, current 2584286458
ehci-hcd ohci-hcd uhci-hcd USB universalHost Controller interface driver v2.3
usb-ohci usb-uhci
wait 3 seconds for USB initialisation ...
ide-cd: cmd 0x3 timed out
hda: lost interrupt
reiserFS: sda2: warning: clm-2200: last commit 2584286458, current 2584286459
reiserFS: sda2: warning: clm-2201: last flush 2584286456, current 2584286457
reiserFS: sda2: warning: clm-2201: last flush 2584286457, current 2584286458
reiserFS: sda2: warning: clm-2201: last flush 2584286458, current 2584286459
/etc/init.d/kbd: line275:echo:write error: No space left on device
Loading keymap i386/qwerty/us.map.gz
ReiserFS: sda2: warning: clm-2200: last flush 2584286459, current 258428660
Start unicode mode
Loading console fontlat9w-16, psfu -m trivial G0: loadable
fsck failedfor at least one filesystem (not /)
Please repair manually and reboot.
The root file system is already mounted read-write.
Attention: only CONTROL-D will reboot the system in this maintenance mode. shutdown or reboot will not work.
Give root password for login:
ReiserFS: sda2: warning: clm-2200: last flush 2584286460, current 258428661
after this you can give the root password , but we dont know what we should proceed to solve the problem
IS there any one who can provide us solution it will be very helpful and appreciated.
Partition 1 can't be accessed, partition 2 has problems, and /dev/hda has a lost interrupt.
Sounds like a dodgy disk. And all this on ES10, which has been out of support for years.
I'd replace the disk, restore the system from most recent good backups, and proceed from there. How often do you do full system backups ?.
Because of "fsck failed ... (not /)", /etc/fstab should be able to be edited without need for any rescue boot to prevent the failed filesystem from automounting, should a more normal boot to perform repairs actually be required. At the same time, space can be made available on the filesystem with no space left, as well as running the appropriate filesystem check manually. More help is likely possible if you post the content of /etc/fstab. As John VV implied, since that version of SUSE is ancient, upgrading to something supported and restoring data from backup likely makes much better sense than trying to repair if manual checking fails.
1. We have problems on not having the current one which the users are requesting
us.
2. We tried to make available around 9Gb of space the errors are the same.
3. Regarding the /etc/fstab file is shown as below.
Seems like one the these "sdd1,sdg1,sde1" . May has bad blocks. try running fsck with these partitions in dry run mode (i think -N option) first & check what happens.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.