Harddisk problem
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 problem: pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# fsck -f /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, PARTIALLY TRUNCATED INODE I=4498435 SALVAGE? [yn] y INCORRECT BLOCK COUNT I=4498438 (673600 should be 667584) CORRECT? [yn] y INCORRECT BLOCK COUNT I=4498439 (467936 should be 459392) CORRECT? [yn] y INCORRECT BLOCK COUNT I=19595269 (838304 should be 829248) CORRECT? [yn] y PARTIALLY TRUNCATED INODE I=20843652 SALVAGE? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) * FILE SYSTEM STILL DIRTY * * FILE SYSTEM WAS MODIFIED * * PLEASE RERUN FSCK * pepe# fsck -f -y /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) * FILE SYSTEM STILL DIRTY * * PLEASE RERUN FSCK * pepe# fsck -f -y /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) * FILE SYSTEM STILL DIRTY * * PLEASE RERUN FSCK * pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error 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? -taavi k6ps tänavsuu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Harddisk problem
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 suddenly got the following problem: pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# fsck -f /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, PARTIALLY TRUNCATED INODE I=4498435 SALVAGE? [yn] y INCORRECT BLOCK COUNT I=4498438 (673600 should be 667584) CORRECT? [yn] y INCORRECT BLOCK COUNT I=4498439 (467936 should be 459392) CORRECT? [yn] y INCORRECT BLOCK COUNT I=19595269 (838304 should be 829248) CORRECT? [yn] y PARTIALLY TRUNCATED INODE I=20843652 SALVAGE? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) * FILE SYSTEM STILL DIRTY * * FILE SYSTEM WAS MODIFIED * * PLEASE RERUN FSCK * pepe# fsck -f -y /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) * FILE SYSTEM STILL DIRTY * * PLEASE RERUN FSCK * pepe# fsck -f -y /dev/ad3s1d ** /dev/ad3s1d ** Last Mounted on /mnt/suur_ketas ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ BLK: 51184064 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080, 160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks, 0.0%fragmentation) * FILE SYSTEM STILL DIRTY * * PLEASE RERUN FSCK * pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error pepe# mount /dev/ad3s1d /mnt/suur_ketas/ mount: /dev/ad3s1d: Input/output error 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? -taavi k6ps tänavsuu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] . Taavi, I'm not an expert but the smartmontools port may help, I am installing it now to keep me informed of hdd status. I can remember reading in the documentation about repairing drives. http://smartmontools.sourceforge.net/ http://www.linuxjournal.com/article/6983 I hope this helps in some way, Ivan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Harddisk problem
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 think.
Download the Samsung diagnostics for your disk and try them. If the
disk fails those, then you should be able to get a warranty
replacement. Before that, you could try installing the smartmontools
port and running smartctl -a /dev/{your disk}. That will tell you if
the disk itself thinks it is dying.
2) But before you do any of that, try changing the cable that connects
your disk. It may be as simple as that, but your errors are a bit too
specific for me to believe this is the problem. After changing the
cable try your fsck again. But really, this looks like a long shot.
3) Before any of those things, copy your files somewhere else, if you
can. Dying disks often get worse. Not quite sure how you'll manage
that given that you don't seem to be able to mount the disk. Maybe
someone here will have an idea. Something with dd ought to work, if you
have somewhere to dd to.
--Alex
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddisk problem in the 5.x series
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 [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 lot of errors, but finally accepts it and everything just works fine. If I remove the hard drive the CDROM is recognised without problems. My guess is that the system tries to use higher PIO mode on the disk than it is good for or something like that. Can anybody explain how I can tune the kernel to avoid the error messages? (BTW I have a GENERIC kernel.) dmesg messages from the 4.11 and the 5.4-RC3 versions are below. I'm nothing like an ATA expert, but I wonder whether it might now fail on 4.11 also... (bad cabling, etc.) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddisk problem in the 5.x series
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 lot of errors, but finally accepts it and everything just works fine. If I remove the hard drive the CDROM is recognised without problems. My guess is that the system tries to use higher PIO mode on the disk than it is good for or something like that. Can anybody explain how I can tune the kernel to avoid the error messages? (BTW I have a GENERIC kernel.) dmesg messages from the 4.11 and the 5.4-RC3 versions are below. I'm nothing like an ATA expert, but I wonder whether it might now fail on 4.11 also... (bad cabling, etc.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
harddisk problem in the 5.x series
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 it and everything just works fine. If I remove the hard drive the CDROM is recognised without problems. My guess is that the system tries to use higher PIO mode on the disk than it is good for or something like that. Can anybody explain how I can tune the kernel to avoid the error messages? (BTW I have a GENERIC kernel.) dmesg messages from the 4.11 and the 5.4-RC3 versions are below. Thanks in advance Zoltan Relevant parts of the dmesg from the 4.11-RELEASE version. FreeBSD 4.11-RELEASE #0: Fri Jan 21 17:27:16 GMT 2005 atapci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 3098MB IBM-DAQA-33240 [6296/16/63] at ata0-master WDMA2 ad1: 28629MB QUANTUM FIREBALLP AS30.0 [58168/16/63] at ata0-slave WDMA2 ad3: 6149MB Maxtor 86480D6 [13328/15/63] at ata1-slave WDMA2 acd0: CD-R CR-2801TE at ata1-master PIO3 Relevant parts of the dmesg from 5.4-RC3 FreeBSD 5.4-RC3 #0: Sun Apr 17 09:23:46 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC atapci0: Intel PIIX3 WDMA2 controller port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ad0: 3098MB IBM-DAQA-33240/R6ORA53A [6296/16/63] at ata0-master WDMA2 ad1: 28629MB QUANTUM FIREBALLP AS30.0/A1Y.1300 [58168/16/63] at ata0-slave WDMA2 ata1-master: timeout sending command=ef ata1-master: error issueing SETFEATURES SET TRANSFER MODE command ata1-master: timeout sending command=ef ata1-master: error issueing SETFEATURES SET TRANSFER MODE command ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE timed out ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE timed out ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE timed out ata1-master: timeout sending command=ef ata1-master: error issueing SETFEATURES SET TRANSFER MODE command ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE timed out ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE timed out ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE timed out acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command acd0: CDROM CR-2801TE/1.07 at ata1-master BIOSPIO acd0: timeout sending command=ef acd0: error issueing SETFEATURES SET TRANSFER MODE command ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command ad3: FAILURE - SETFEATURES ENABLE RCACHE timed out acd0: timeout sending command=ef acd0: error issueing SETFEATURES SET TRANSFER MODE command ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command ad3: FAILURE - SETFEATURES ENABLE WCACHE timed out acd0: timeout sending command=ef acd0: error issueing SETFEATURES SET TRANSFER MODE command ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command ad3: FAILURE - SET_MULTI timed out ad3: 6149MB Maxtor 86480D6/NAVX171F [13328/15/63] at ata1-slave BIOSPIO ad3: TIMEOUT - READ retrying (2 retries left) LBA=12594897 acd0: timeout sending command=ef acd0: error issueing SETFEATURES SET TRANSFER MODE command ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command ad3: TIMEOUT - READ retrying (1 retry left) LBA=12594897 acd0: timeout sending command=ef acd0: error issueing SETFEATURES SET TRANSFER MODE command ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command acd0: timeout sending command=ef acd0: error issueing SETFEATURES SET TRANSFER MODE command ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out ad3: FAILURE - SETFEATURES SET TRANSFER MODE timed out acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command ad3: FAILURE - READ timed out acd0: timeout sending command=a0 acd0: error issuing ATA PACKET command acd0: timeout sending command=a0 acd0: error issuing
harddisk problem and/or fsck problem?
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 fsck /dev/da0s1a, and I'm just told of NO WRITE for the fs, and the phases shown without error. But I *can* write there -- my / partition. OK, FYI -- This happens on 4.9-RELEASE and 5.2.1-RELEASE-i386 both. I have an IBM UltraStar Ultra160 SCSI disk, model no. IC35L018UDW210-0 ... Runs on a Tyan S2462 Thunder K7 dual Athlon-MP board, using the GENERIC kernel. I've run the onboard Adaptec-controller's format and verify utilities, which I presume run without error, since they just do their thing without error messages and just say when they're done. I install the above via the miniinst CDs, cvsup the lastest sources, and that's it for usage. But the machine boots and runs fine otherwise. Is this something to really worry about? Is it safe to proceed with making world? Should I try forcing fsck to do anything? Or, should I try running fsck having booted from CD? Other ideas or suggestions? Thanks all for any help offered! Cheers, -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddisk problem and/or fsck problem?
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 because you are supposed to boot -s into single user mode. Then, you don't have write access and the fsck works. BTW, the whole point of booting into single user mode is to avoid a bad kernel. When you drop into single user mode, you aren't testing the new kernel. Kent /dev/da0s1a: NO WRITE ACCESS /dev/da0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. I run fsck /dev/da0s1a, and I'm just told of NO WRITE for the fs, and the phases shown without error. But I *can* write there -- my / partition. OK, FYI -- This happens on 4.9-RELEASE and 5.2.1-RELEASE-i386 both. I have an IBM UltraStar Ultra160 SCSI disk, model no. IC35L018UDW210-0 ... Runs on a Tyan S2462 Thunder K7 dual Athlon-MP board, using the GENERIC kernel. I've run the onboard Adaptec-controller's format and verify utilities, which I presume run without error, since they just do their thing without error messages and just say when they're done. I install the above via the miniinst CDs, cvsup the lastest sources, and that's it for usage. But the machine boots and runs fine otherwise. Is this something to really worry about? Is it safe to proceed with making world? Should I try forcing fsck to do anything? Or, should I try running fsck having booted from CD? Other ideas or suggestions? Thanks all for any help offered! Cheers, -Rich -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddisk problem and/or fsck problem?
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 this alarming output of fsck -p: Well, you missed reading something because you are supposed to boot -s into single user mode. Then, you don't have write access and the fsck works. BTW, the whole point of booting into single user mode is to avoid a bad kernel. When you drop into single user mode, you aren't testing the new kernel. Kent Doh! Yes, I guess I was reading too quickly. And of course it makes sense that I'd not need to fsck and mount things if I just drop into single-user mode. But I wasn't yet testing a new kernel... I haven't yet made the buildworld target. I see later on, though, where I'm supposed to boot -s after installing a newly built kernel. Thanks for your help! -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddisk problem and/or fsck problem?
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 prep for making world. Even then, it seems OK, except for this alarming output of fsck -p: Well, you missed reading something because you are supposed to boot -s into single user mode. Then, you don't have write access and the fsck works. BTW, the whole point of booting into single user mode is to avoid a bad kernel. When you drop into single user mode, you aren't testing the new kernel. Kent Doh! Yes, I guess I was reading too quickly. And of course it makes sense that I'd not need to fsck and mount things if I just drop into single-user mode. But I wasn't yet testing a new kernel... I haven't yet made the buildworld target. I see later on, though, where I'm supposed to boot -s after installing a newly built kernel. 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 system useless until you repair if if you do the installworld before booting to the new kernel. The sequence is /usr/src/UPDATING is there for a reason. You can change the order but if it breaks your system, you could have to repair it using the fixit disk or re-install. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddisk problem and/or fsck problem?
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 system useless until you repair if if you do the installworld before booting to the new kernel. The sequence is /usr/src/UPDATING is there for a reason. You can change the order but if it breaks your system, you could have to repair it using the fixit disk or re-install. Kent Yes, I'm hip to all that... Thanks, again! -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
