[wellylug] Can't reboot: "cannot open /mnt/etc/fstab: no such file "
Adam Felix Bogacki
afb at paradise.net.nz
Mon Oct 25 12:48:23 NZDT 2004
Hi, using Debian unstable I did an 'apt-get dist-upgrade --fix-missing'
last night and on
booting this morning found login now had audio, and that the post-login
screen had remembered
theme, font-sizes, and other details from my last session. So far so
good - I was impressed.
But when I chose metacity as windows manager and deleted the first
(config) screen
as normal after using it, things started going wrong.
I could not move or use the second gnome-terminal opened at login. It
had no top
border, and clicking it did not give it focus meaning that I could not
enter text.
After some effort I decided that I could not do anything with it and
rebooted.
I don't like doing this but have found that the system can usually recover
after some time. In retrospect, maybe I should have logged out.
On reboot, the kernel loads normally, but them I get the following boot-log
message, followed by the iterated sequence ...
.......<snip>.....
hdb: irqtimeout: status=0xd0 {Busy}
ide0: reset: success
.......<snip>........
I'd be grateful for any constructive advice.
Adam Bogacki,
afb at paradise.net.nz
[Transcribed boot-log follows.]
[hda: is my WinXP drive]
....................................................................................................................................................
hda: DMA disabled
hdb: drive not ready for command
ide0: reset: success
blk: queue d732fa00, I/O limit
/scripts/ext3: add-journal.sh: 30: cannot open /mnt/etc/fstab: no such file
EXT-fs: INFO: recovery required on readonly filesystem
EXT-fs: write access will be enabled during recovery
hdb: irq timeout: status=0xd0 {Busy}
ide: reset: success
hdb: irq timeout: status=0xd0 {Busy}
ide: reset: success
hdb: irq timeout: status=0xd0 {Busy}
ide: reset: success
hdb: irq timeout: status=0xd0 {Busy}
ide: reset: success
hdb: irq timeout: status=0xd0 {Busy}
More information about the wellylug
mailing list