-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/03/07 16:39, Bogart Salzberg wrote:
Dear Debian Users,
I partitioned and installed an ext3 filesystem on an external 250 GB
Western Digital USB 2.0 drive. It mounts OK manually and I can
read/write it. I added this line to /etc/fstab in order to mount the
drive at boot time:
/dev/sdc1 /archive ext3 defaults 0 3
Upon reboot, I got an error at the console re: fsck not finding a
valid
filesystem. But when I exit the maintenance shell and continue
booting,
the drive mounts as specified and "fsck /dev/sdc1" reports clean.
Are the USB drivers not loading in time? I tried changing the "pass"
value in column 6 of /etc/fstab to 0. This had the desired effect of
skipping the fsck checks, but the drive did not automount either.
Has anyone else out there encountered this problem with mounting USB
drives at boot?
Stock Debian binary kernel or home-rolled?
Also, does anyone have any hints for recovering all of the startup
console messages after boot? I get a lot out of "dmesg" and
"/var/log/kern.log", but some messages are missing. For example, the
fsck messages. Are they being wiped out by messages from higher/other
run levels?
Also, the box stalled during POST after reboot, which I found
remarkable. Is it possible the USB drive has introduced an interrupt
problem?
Well that's Bad. Just one time?
Whoa, that's three issues in one message. ;-)
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHVIhMS9HxQb37XmcRAmfSAJ9ouYCNDEqHi3wgEIWM8oE7QZPotACffF6W
T0FxZERsyDP+dNpwJvyF/gs=
=tyAH
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org