Great to be of a little help. I've marked this with solved for the convenience of readers of the archive. Ups - it should be like this. -- /vbj On 26/01/15 15:38, Constant Brouerius van Nidek wrote:

On Monday 26 January 2015 10:07:46 Vagn Bjørno wrote:

...

On 24/01/15 17:40, Larry Finger wrote:

...

On 01/23/2015 11:29 PM, Constant Brouerius van Nidek wrote:

...

...

Changed packages: Does not know what package have caused my problem but after yesterdays zypper dup my main computer does not boot any more. This computer was fully updated Tumbleweed and worked okay up to the last update which updated some 286 packages. I have tried al installed kernel packages without success. With the

On Saturday, January 24, 2015 12:40:58 AM Ludwig Nussel wrote: older kernels the error messages differed slight.

After the reboot I was/am stuck with the cryptic message: ....................................... root (hd1,0)

Filesystem type is ext2fs, parition type 0x83

kernel /boot/vmlinuz-3.18.1-1-default root=/def/disk/by-label/susesdb1 resume=/dev/by-label/swap splash=silent quiet nomodeset

[Linux-bzImage, setup=0x4200, size=0x5289b0]

initrd /boot/initrd-3.18.1-1-default

[Linux-initrd @ 0x37870000, 0x77f754 bytes]

[ 4.723024] usb 1-1: device descriptor read/all, error =75 [ 6.911699] sd 5:0:0:0: [sdg ] Asking for cache data failed [ 6.911699] sd 5:0:0:0: [sdg ] Assuming drive cache: write through [ 14.256028] ata2: SRST failed (errno=-16) [ 24.268028] ata2: SRST failed (errno=-16) - ........................................

Have no idea how I can reslove the mess in which I find myself in. On the affected machine I am still using Grub. On the machine I am using now I have Grub2 but I have not stopped a planned update for the time being. Both machines are Pentium IV.

When I read that the same failure happens even with older kernels, the "hardware" flag went off in my head. Those ata2: failures look very suspicious. Error number -16 is -EBUSY, which implies that the disk system has not finished some operation that was previously started.

If your BIOS includes any disk diagnostics, run them. If no such routines are available, then boot a live image and run smartctl to look at the statistics for the disk. If nothing is obvious, then run the long disk test. I suspect that it will fail. It is not totally dead, or the kernel and initrd would not have loaded.

Larry

I ran into a somewhat similar catastrophy this morning after updating - I've not been using the machine for some days, so there where a lot of updates.

When rebooting I got stuck with a line somewhat like the above. I changed console to F7, which had a recovery prompt; I ran journalctl, which recommended running fsck, so that I did. After having repaired the filesystem I could boot OK.

Hope this helps.

Thanks. It helped because "fsck" seems to have solved my problem too. Was planning to work on that machine on Monday but your tip was just what I needed. Saved the Monday :).

-- Mvh Vagn Bjørno ================================================== In a 'Life without Walls(tm)' - who needs windows? http://en.windows7sins.org/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org