Date: Thu, 24 Dec 2009 08:30:55 -0800 From: Rem P Roberti <remegius@comcast.net> To: Polytropon <freebsd@edvax.de> Cc: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: What happened to /home? Message-ID: <20091224163055.GB1056@bsd.remdog.net> In-Reply-To: <20091224100652.35598f38.freebsd@edvax.de> References: <20091223230111.GA1188@bsd.remdog.net> <20091224100652.35598f38.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I hope you won't see something like > > % cd mnt/poly > mnt/poly: Not a directory. > > % file mnt/poly > mnt/poly: cannot open `mnt/poly' (Bad file descriptor) > That is exactly what I saw, and nothing worked to try and fix the problem. So, as I indicated in an earlier post, I ran fsck -y on the /usr partition and was finally able to deep six /home. No real catastrophe because I had all of /home backed up. So, I just did a mkdir of /home and repopulated it. I'm still scratching my head as to what caused the initial problem. There was no power failure or anything like that. I remember that all of a sudden when I booted the laptop I got this message (I forgot to include this in my first post): FreeBSD/.i386 boot Default:0:ad(0,a)/boot/loader boot: Hardly the normal opening screen, and I had to hit enter to proceed. First time I did that that the computer booted OK, the second time it broke. The only thing that changed between the time of the normal boot and the problem is that I installed a USB hub to this old Compaq because it only has one USB port. Who knows. Rem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091224163055.GB1056>