TS /etc/inittab missing: error install: %pre scriptlet failed exit code 255

zaiwen

I am troubleshooting the missing of /etc/inittab on RHEL 4.0. When I am running this command to install initscripts in rescue mode:

rpm -ivh --force --root /mnt/sysimage /mnt/source/Redhat/RPMS/packagename

got error:

error: %pre(initscripts-7.93.11.EL-1) scriptlet failed, exit status 255
error: install: %pre scriptlet failed (2), skipping initscripts-7.93.11.EL-1

If I add --noscripts option to this command, it works. I just need to change the default run level in /etc/inittab from 3 to 5 and machine reboots.

# rpm -ivh --force --noscripts
    --root /mnt/sysimage /mnt/source/Redhat/RPMS/initscripts-7.93.11.EL-1

I don't read this in the old postings. Anyone encountered the same situation? Is it a good practice to use "--noscipts"?

Thanka a lot............

squallabc

我好像也碰到这个问题,查了一下,好像是http://www.linuxsir.cn/bbs/showthread.php?t=164419

yongjian

Another way:
Under rescue mode, do this:

1. 
   
2. cd /tmp
   
3. rpm2cpio /mnt/source/RedHat/RPMS/iniscripts*.rpm | cpio -idvm
   
4. cd etc/
   
5. cp inittab /mnt/sysimage/etc/
   

复制代码

then reboot. You simply avoid to install the whole package again.

OR:

1. 
   
2. mount -o bind /mnt/source /mnt/sysimage/mnt/source
   
3. chroot /mnt/sysimage
   
4. rpm -Uvh --force --nodeps /mnt/source/iniscripts*.rpm
   

复制代码

Make sure you have all the partitions mounted correctly before you do chroot.

zaiwen

I have tested both ways you suggested.

The first one (avoid install the whole package) works very well. I like this way.

The second one (--nodeps)  doesn't work, same error (pre scripts failed). I have to use "--noscripts " option.

Thanks a lot for the response. Now I have a clear picture of what to do when running "rpm -ivh" in rescue mode.

yongjian

Post by zaiwen
I have tested both ways you suggested.

The first one (avoid install the whole package) works very well. I like this way.

The second one (--nodeps)  doesn't work, same error (pre scripts failed). I have to use "--noscripts " option.

Thanks a lot for the response. Now I have a clear picture of what to do when running "rpm -ivh" in rescue mode.

That's strange cause the second way works just fine on my RHEL4

hnull

Dear yongjian, Could u kindly explain why this issue happened? In another way,what cause that we have to use rpm2cpio?

yongjian

Post by hnull
Dear yongjian, Could u kindly explain why this issue happened? In another way,what cause that we have to use rpm2cpio?

I think its because in the rescue env, you don't have a real root env, so you will have to chroot to the local root env to run rpm (then you will have all rpm prereqs, libs and all that stuff...). But it seems not always like that...

hnull

Post by yongjian
I think its because in the rescue env, you don't have a real root env, so you will have to chroot to the local root env to run rpm (then you will have all rpm prereqs, libs and all that stuff...). But it seems not always like that...

Thanks a lot :rolleyes: