Ayer, Paul W wrote:
Good afternoon,
Recently had a problem where after doing a mkinitrd and booting the
system it came up in panic mode (or should I way would not come up) ..
After some research found that someone who was intending to backup
/etc/fstab had actually had emptied it out.
This was done after a good boot so the system was up and working find.
The /etc/fstab was not deleted just empty.
I then came along and added some new disk and updated via mkinitrd ...
all fine no errors at all...
Booted the system and got (last few messages);
======================================================================
dasd(eckd): 0.0.0179: (4kB blks): 2403360kB at 48kB/trk compatible disk
layout
dasdap:VOL1/ 0X0179: dasdap1
dasd(eckd): 0.0.0200: 3390/0A(CU:3990/01) Cyl:3338 Head:15 Sec:224
dasd(eckd): 0.0.0200: (4kB blks): 2403360kB at 48kB/trk compatible disk
layout
dasdaq:VOL1/ 0X0200: dasdaq1
Loading dasd_fba_mod.ko module
Creating root device
Mounting root filesystem
mount: missing mount point
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000
00040DA0;
======================================================================
Everything is all set now and fixed .. but what I am wondering is if
mkinitrd or a forked process it kicks off
Why do you think that?
should at least give a warning message that the /etc/fstab is empty and
do not boot or you won't come back up ....
Why?
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Please do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
