/boot/message read error

English Install/Boot/Login
#1

Hello,

Back after a while. I was trying to edit the ori of openSuse’s bootsplash, using this way :


$ mkdir /home/my_username/cpio
$ mkdir /home/my_username/cpio/work
$ cd /home/my_username/cpio/work
$ cp /boot/message .
$ cpio -idv <> ../message
$ cd ..
$ su
# cp message /boot/message
# exit
$ rm -Rf work

But I am stucked at 5th step. It gave me error : cpio: premature end of archive

So I didn’t continue it.After I reboot my netbook, there is an error:

hd(0,8) /boot/message : read error.

But then, the ‘old’ grub (grub with black screen) is appeared and if I choose the menu, It is like usual. Just the error message annoying me :

hd(0,8) /boot/message : read error.

How could I fixed that thing?

Thank you for any responses

#2

On 07/28/2011 04:46 AM, mynameisthom wrote:

> How could I fixed that thing?

sorry, i don̈́t have any idea what you are trying to do (because i’m not a
programmer, script writer or student of either)…

but, i do know that it is better to ask these programming/scripting
kinds of questions in the correct forum: http://tinyurl.com/5v695w4

that way the programmers and script writers who hang out there will find
them easily…

(on the other hand, there are script writers here too…maybe one of
them has a different helpful hint for you…)

–
DD
openSUSE®, the “German Engineered Automobiles” of operating systems!

#3

Hi DenverD, thank you for your response. But I think it’s not about ‘programming’ thing, but grub/boot error thing. That’s why I am asking here… :slight_smile:

#4

II have to contemplate a bit, but

cpio -idv <> ../message

looks a bit strange to me. What does the* <* redirect redirect from?

#5

Without checking all the details for what it is doing (I would ALLWAYS check all those statements reading their man pages for what they are going to do before executing them), I found this one:

$ mkdir /home/yourname/cpio
$ mkdir /home/yourname/cpio/work
$ cd /home/yourname/cpio/work
$ cp /boot/message .
$ cpio -idv < message
$ mv message ../message-old
$ cp /home/yourname/Documents/favpic.jpg back.jpg
$ ls | cpio -ov > ../message
$ cd ..
$ su
$ cp message /boot/message
$ exit
$ rm -Rf work

It is not the <, but the > that spoils the fun (and makes the < useless).

#6

I exactly dont know about the steps. I got the steps from the internet… :frowning:

#7

Isn’t that a bit dangerous? There could be statements there (intentionaly or by accident/typo) that break your system. I allways take them as suggestions and then check them against man pages, etc. Also, when you do not have any knowledge about what those bash statements do (I refer to e.g. those redirects), you will not understand what the slightest typo you make will create.

Is that

cpio -idv <> ../message

realy exactly in the source you got it from (from the internet)?

And next time you want advice about something “from the internet” please state where you found it. Then people here can at least look there also and give advice based on more information then the vague “from the internet”.

#8

Hehehehe… Here is the link http://opensuse.or.id/panduan/tips-trick/kustomisasi-bootsplash-pada-opensuse/. It’s Indonesian local community. It’s an Indonesian article, about changing the bootsplash. I’ve joined the mailing-list too. But since the mailing list is soo ‘quiet’, I can’t depends on it so much :frowning:

Umm… what do you think about re-installing the GRUB? It that will help me out of this? I’m planning to.

#9

My guess is that you did not backup the original file like you should have. Right? Any time you plan to make a change to an important file you should backup the original.

Re installing grub from Yast may do it at least in theory.

#10

Unfortunately yeah. I didnot. My bad. Another point to be learned :smiley:

A few days ago, I did reinstalling the grub from Yast. Twice, just to make it sure. But it didn’t change anything. So, my last hope is on re-installing it using a live-DVD.

I’ll tell you all what’s happened once I complete the step… :wink:

#11

I still do not get a complete picture.
From the statements you gave in post #1 above, line number 5 is wrong (as I explained above). You stopped from there because you got an error (that is the cleverest thing to do: stop as soon as strange things happen and then ask). Now how can you have destroyed anything as you did not do the statements thyt followd the wrong one? In other words how, when you did not even go to the statments where you became root, could you have damaged anything in /boot?

#12

I just have no idea too :smiley: But after I got error, I got my grub has ‘strange’ behavior. It might be I run it as root when I try it, so it affected the ori file. The code I show is from the web I told before… My bad…

But the good thing is, I’ve my GRUB working as usual. The error caused by line 5th made the ori file ‘not recognized’ or by system. What I do was copy ‘message’ file from my friend’s openSuse. I just copy-paste’d it and work. But, of course, I first opened the cpio archive, just to make sure if the file has common configuration :smiley:

Case Closed, btw :smiley: Thank you all for time, posts and the help. I appreciate it so much.