Hi,
Got a brand new Samsung 250 GB IDE harddisk, added it to my home PC running
FreeBSD 5.3, created FreeBSD filesystem there. I have been using it for
several months, keeping relatively large (5-10 GB) home video files there,
and it has been working fine.
But now suddenly got the following
Taavi Tänavsuu wrote:
Hi,
Got a brand new Samsung 250 GB IDE harddisk, added it to my home PC
running
FreeBSD 5.3, created FreeBSD filesystem there. I have been using it for
several months, keeping relatively large (5-10 GB) home video files
there,
and it has been working fine.
But now
Taavi Tänavsuu wrote:
I'm not yet very familiar with harddisks, filesystems, and FreeBSD,
but is
there anything else i could try to make the disk usable again, or is it
somehow physically damaged?
There are two possibilities:
1) The disk is damaged. From your output that's what I'd
Hi,
Thanks for your mail. Yes I tried again with 4.11 and
it still works without the error messages. It does not
really matter, because it works in 5.4 too. I just
have to live with the error messages I guess.
Thnaks anyway
Zoltan
--- Lowell Gilbert
[EMAIL PROTECTED] wrote:
zoltan sandor
zoltan sandor [EMAIL PROTECTED] writes:
I have the following problem. I moved my system from
FreeBSD 4.11 to 5.4-RC3 by reinstalling everything.
The 4.11 system had no problem finding my MAXTOR hard
disk as ad3 as slave on the secondary IDE behind the
CDROM. The new 5.4 system indicates a
Hi everybody!
I have the following problem. I moved my system from
FreeBSD 4.11 to 5.4-RC3 by reinstalling everything.
The 4.11 system had no problem finding my MAXTOR hard
disk as ad3 as slave on the secondary IDE behind the
CDROM. The new 5.4 system indicates a lot of errors,
but finally accepts
Greetings, fellow FreeBSD users!
Everything so far works fine for me, until I drop into single-
user mode to prep for making world. Even then, it seems OK,
except for this alarming output of fsck -p:
/dev/da0s1a: NO WRITE ACCESS
/dev/da0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
I run
On Friday 26 March 2004 10:06 am, Richard Dawes wrote:
Greetings, fellow FreeBSD users!
Everything so far works fine for me, until I drop into single-
user mode to prep for making world. Even then, it seems OK,
except for this alarming output of fsck -p:
Well, you missed reading something
On Fri, Mar 26, 2004 at 11:55:06AM -0800, Kent Stewart wrote:
On Friday 26 March 2004 10:06 am, Richard Dawes wrote:
Greetings, fellow FreeBSD users!
Everything so far works fine for me, until I drop into single-
user mode to prep for making world. Even then, it seems OK,
except for
On Friday 26 March 2004 01:02 pm, Richard Dawes wrote:
On Fri, Mar 26, 2004 at 11:55:06AM -0800, Kent Stewart wrote:
On Friday 26 March 2004 10:06 am, Richard Dawes wrote:
Greetings, fellow FreeBSD users!
Everything so far works fine for me, until I drop into single-
user mode to
On Fri, Mar 26, 2004 at 02:09:35PM -0800, Kent Stewart wrote:
The sequence that is designed to keep your out of trouble is buildworld,
buildkernel, installkernel, boot -s, and installworld, followed by a
mergemaster.
There are times as the statfs change to current that would render your
11 matches
Mail list logo
