I was on the computer and the computer died on its own. Just crashed. I can log into Win7 using grub but Opensuse will stall not start up. I tried recovery mode in grub but I get the same thing.
Did you do an update??
So how far does it get??
If you start it and press esc immediately do you see any error message or at what point does it stop??
On Fri, 28 Nov 2014 19:46:02 +0000, CulpeperMM wrote:
> I was on the computer and the computer died on its own. Just crashed. I
> can log into Win7 using grub but Opensuse will stall not start up. I
> tried recovery mode in grub but I get the same thing.
What specific error messages do you get?
What version of openSUSE are you using?
We need information in order to help you.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
OpenSuse 12.3 kernel 3.7.10-1.40
No recent updates. It gets as far as the first splash screen then goes into terminal mode. The last line is
Buffer I/O error on device sdb6, logical block 0
Looks like a file system problem. You will need to boot to live Linux or the DVD install rescue mode. You will need to run fsck against that partition.
fsck /dev/sdb6
This will probably come back with errors and there will be instruction to attempt a fix.
Note that this can be caused by real damage to a disk and may indicate a failing hard drive.
Running smartctl against the disk in question (/dev/sdb) will give the health of the drive
Note that ver 12.3 is getting old
Traced the problem to a weak surge protector that shut down the computer. It is a Tandy to give you an idea on how old it is. Anyway, this corrupted the boot sequence into Opensuse from Grub. From Win7 I am able to recover data using Ext2Read. I just copy the data folders from the Linux partitition over to Win7. If there isn’t a easy fix to recover booting into Opensuse I may not return to Linux. I really enjoyed the protection of a secure operating system.
Did you run fsck ?
Put in any linux live cd in your pc. ( opensuse rescue disk to name one example)
Reboot pc and let the live cd boot.
Then open up the console and type or copy paste what gogalthorp said.
(fsck /dev/sdb6)
You need to become root for this.
exit console, reboot and with a bit of luck it will all work again as before.
No joy using Live CD. I also tried the suggestions on the other recent power failure then fail to boot thread.
On 2014-11-29 23:36, CulpeperMM wrote:
>
> No joy using Live CD.
Why exactly?
If you say that «From Win7 I am able to recover data using Ext2Read», it
is impossible the live CD doesn’t work.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I didn’t say the Live CD doesn’t work. The advice he gave me did not correct the problem from the terminal using the Live CD. There is not a problem with Win7 or the hard drive. The problem is mounting partitions associated with the installed Linux OS using the Live CD. If there is even a fix that can be had other than a new fresh install. I don’t know. Here is the result on check using GParted
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'><html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en-US' lang='en-US'>
<head>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8' />
<title>GParted Details</title>
</head>
<body>
<p>GParted 0.14.1</p>
<p>Libparted 2.4</p>
<table border='0'>
<tr>
<td colspan='2'>
<b>Check and repair file system (ext4) on /dev/sdb6</b> 00:00:00 ( ERROR )
</td>
</tr>
<tr>
<td> </td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
calibrate /dev/sdb6 00:00:00 ( SUCCESS )
</td>
</tr>
<tr>
<td> </td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
<i>path: /dev/sdb6<br />start: 329,945,088<br />end: 371,888,127<br />size: 41,943,040 (20.00 GiB)</i>
</td>
</tr>
</table>
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
check file system on /dev/sdb6 for errors and (if possible) fix them 00:00:00 ( ERROR )
</td>
</tr>
<tr>
<td> </td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
<b><i>e2fsck -f -y -v /dev/sdb6</i></b>
</td>
</tr>
<tr>
<td> </td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
<i>Could this be a zero-length partition?<br /></i>
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
<i>e2fsck 1.42.6 (21-Sep-2012)<br />e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdb6<br /></i>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
<p>========================================</p>
</body>
</html>
I get the same thing wih sbd7, which is about 288 GiB.
I retrieved the code by CulpeperMM and viewed it as an html page. This is what it says:
GParted 0.14.1
Libparted 2.4
Check and repair file system (ext4) on /dev/sdb6 00:00:00 ( ERROR )
calibrate /dev/sdb6 00:00:00 ( SUCCESS )
path: /dev/sdb6
start: 329,945,088
end: 371,888,127
size: 41,943,040 (20.00 GiB)
check file system on /dev/sdb6 for errors and (if possible) fix them 00:00:00 ( ERROR )
e2fsck -f -y -v /dev/sdb6
Could this be a zero-length partition?
e2fsck 1.42.6 (21-Sep-2012)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdb6
========================================
You do not mount partition to run fsck in fact it won’t totally work if the partition is fully mounted
On 2014-12-01 06:36, CulpeperMM wrote:
>
> I didn’t say the Live CD doesn’t work. The advice he gave me did not
> correct the problem from the terminal using the Live CD. There is not a
> problem with Win7 or the hard drive. The problem is mounting partitions
> associated with the installed Linux OS using the Live CD.
The advice was not to mount, but repair.
On 2014-12-01 13:06, swerdna wrote:
> I retrieved the code by CulpeperMM and viewed it as an html page. This
> is what it says:
Thanks.
> Code:
> --------------------
> GParted 0.14.1
>
> Libparted 2.4
>
> Check and repair file system (ext4) on /dev/sdb6 00:00:00 ( ERROR )
>
> calibrate /dev/sdb6 00:00:00 ( SUCCESS )
>
> path: /dev/sdb6
> start: 329,945,088
> end: 371,888,127
> size: 41,943,040 (20.00 GiB)
> check file system on /dev/sdb6 for errors and (if possible) fix them 00:00:00 ( ERROR )
>
> e2fsck -f -y -v /dev/sdb6
>
> Could this be a zero-length partition?
> e2fsck 1.42.6 (21-Sep-2012)
> e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdb6
> ========================================
> --------------------
It doesn’t look as if the partition table is right. Either that or… or
the disk has faulty sectors. I would try the long SMART test.
That gparted is old: 13.1 has 0.16, the above is 0.14.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Christ, I didn’t try to mount to run the terminal. Every time I post something some know-it-all takes something to the extreme and post some ridiculous comment. The OS is a POS. I will either do a new install or moveon.org. Thanks to those that tried to help. It is not that big of deal. Things happen. I shouldn’t have been using a 20 year old surge protector.