Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!in2.uu.net!ott.istar!istar.net!van.istar!uniserve!oronet!news.acsu.buffalo.edu!news.drenet.dnd.ca!crc-news.doc.ca!nott!nntp.igs.net!usenet From: cskinner@bml.ca (Chris K. Skinner) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Hardware or misconfig causes file system not to mount. Date: Thu, 04 Jul 1996 10:24:31 GMT Organization: Bytown Marine Limited, Nepean/Kanata, Ont, Canada Lines: 46 Message-ID: <4rg6fo$6ul@nntp.igs.net> NNTP-Posting-Host: ttyc0b.ott.igs.net X-Newsreader: Forte Free Agent 1.0.82 Hi. Help Me! I was merrily working away when my system spontaneously rebooted. I had just added an additional memory SIMM and was working to backup my hand-crafted config files when the booting happend. I've removed the suspect SIMM, but now the system says that it can't stat the device that has my root file system on it... When I cd to /dev and do an ls, a bunch of the dev files complain that they are bad file descriptors. This happened after doing find / -newer /etc/namedb/edu.zone \ -fstype local -type f -print >/usr/home/bob/jnk.sh then editing the jnk.sh file to get rid of the lines with files that I didn't want to backup. Then I had a 2 Gbyte EIDE Seagate disk that was partitioned using Disk Manager Dynamic Drive overlay on /dev/wd3 for the full 2 Gigs, and I changed fstab so that it would mount that partition as read/write instead of read-only, then I re-booted with these changes in effect. Then I did the following tar command: tar cSzlvfTP /mnt6/back_tar.gz /usr/home/bob/jnk.sh In the middle of the command, I noticed that a gif file that was in perfect working order said that was going to be padded out to 240 Mbytes or some such. I pressed control break because this was completely untrue. The file was normally only 150 kbytes or less. I checked the /mnt6/back_tar.gz file and it was about 6 Mbytes at that time. I deleted the file. I did an fsck and said yes for every idiosyncracy that it wanted to fix. I re-booted and all seemed well. I navigated to a directory or two and did ls, then I accidentally typed pwdd<enter> and then the machine spontaneously rebooted on me after a five second delay, and now I've got the situation that it says that fsck says that the /dev devices for most of my file system components cannot be stat'ed or some such. What's my next step after removing that Ram SIMM in order to make the files on my disk accessible again? TIA. Regards, Chris K. Skinner