Re: Should newfs include -S 4096? was Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On Fri, 23 Nov 2012, free...@johnea.net wrote: One of the complications was getting old metadata off of the drive. After trying a couple of 'dd' invocations: # overwriting the first sector dd if=/dev/zero of=/dev/ada0 bs=512 count=1 # also tried overwriting the last sector diskinfo ada0 | cut -f4 3907029168 (subtract 34, per WB) (I actually just subtracted the trailing 68) dd if=/dev/zero of=/dev/ada0 seek=3907029100 This would still seem to not delete all of the metadata, since after issuing: gmirror label -b split gm0 /dev/ada0 gmirror load # repartition new mirror gpart create -s MBR mirror/gm0 # ignore "mirror/gm0s1 added, but partition is not aligned on 4096 bytes" after add gpart add -t freebsd -a 4k mirror/gm0 # create the bsdlabel partitions in slice 1 (s1) gpart create -s BSD mirror/gm0s1 I would see that the old gm0s1a and gm0s1b had reappeared, even though I had not yet issued the 'add -t freebsd-ufs'. I'm not sure if they came back with the 'add -t freebsd' or the 'create -s BSD'. Saved this since yesterday, thinking maybe I could come up with an idea, but so far I can't think what would cause that. It might not hurt to force a retaste after the dd. The only thing that seemed to fix it was: gpart destroy -F /dev/ada0 I also tried at one point: gpart destroy -F ada0 gpart create -s gpt ada0 gpart destroy -F ada0 The thing I wonder about now: Should newfs include -S 4096? I used: newfs -U /dev/mirror/gm0s1a Will this lead to 512 byte sector access to the disk through the file system? Will this impact performance or longevity of the mirror? It's a good question; I have not tried it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Should newfs include -S 4096? was Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On 2012-11-20 21:10, Warren Block wrote: > On Tue, 20 Nov 2012, free...@johnea.net wrote: > >> On 2012-11-20 14:28, Gary Aitken wrote: >>> On 11/20/12 13:34, free...@johnea.net wrote: >> freebsd-update upgrade -r 9.1-RC3 >> ... "Not UFS" "No ada0" "No boot" >> >>> >>> Seems like it isn't supposed to work for 9.1-RC2 >>> >> >> I previously used binary update to migrate from 9.0 to 9.1, via: >> >> freebsd-update upgrade -r 9.1-RC1 >> freebsd-update install >> reboot >> freebsd-update install >> reboot >> >> I'm starting to think having the swap partition in gm0s1a and the booting >> UFS partition in ada0s1b is the problem: >> http://forums.freebsd.org/showthread.php?t=31954 >> >> The "Not UFS" error comes immediately on boot. >> >> If I boot from rescue media, I can start the gmirror, mount it and chroot >> into it. >> >> The whole install seems fine except for the first stage boot loader finding >> the UFS partition. >> >> A handy bootloader config trick would be greatly appreciated! > > boot(8) says > > The automatic boot will attempt to load /boot/loader from partition > `a' of either the floppy or the hard disk. > > You could try setting the correct device path in /boot/boot.config, but I > suspect that won't be read until too late. > > gptboot looks for the first UFS partition. Maybe /boot/boot can be modified > to do that also. I ended up booting from rescue media, removing one drive and stopping the gmirror, creating a new gmirror on the removed drive to place the UFS partition first, and performing a dump/restore to transfer the system. Then I was able to boot from the new gmitrror and add the second drive to it. One of the complications was getting old metadata off of the drive. After trying a couple of 'dd' invocations: # overwriting the first sector dd if=/dev/zero of=/dev/ada0 bs=512 count=1 # also tried overwriting the last sector diskinfo ada0 | cut -f4 3907029168 (subtract 34, per WB) (I actually just subtracted the trailing 68) dd if=/dev/zero of=/dev/ada0 seek=3907029100 This would still seem to not delete all of the metadata, since after issuing: gmirror label -b split gm0 /dev/ada0 gmirror load # repartition new mirror gpart create -s MBR mirror/gm0 # ignore "mirror/gm0s1 added, but partition is not aligned on 4096 bytes" after add gpart add -t freebsd -a 4k mirror/gm0 # create the bsdlabel partitions in slice 1 (s1) gpart create -s BSD mirror/gm0s1 I would see that the old gm0s1a and gm0s1b had reappeared, even though I had not yet issued the 'add -t freebsd-ufs'. I'm not sure if they came back with the 'add -t freebsd' or the 'create -s BSD'. The only thing that seemed to fix it was: gpart destroy -F /dev/ada0 I also tried at one point: gpart destroy -F ada0 gpart create -s gpt ada0 gpart destroy -F ada0 After that I could create the new partitions within the slice, with freebsd-ufs first: # size of ufs partition must be calculated, from 'diskinfo -v /dev/ada0': 2000398934016 # media size in bytes (1.8T) ; 1024*1024*1024 1073741824 ; 2000398934016/1073741824 1863.01668548583984375 # subtract 8G from 1863 = 1855G gpart add -t freebsd-ufs -a 4k -s 1855G mirror/gm0s1 gpart add -t freebsd-swap -a 4k mirror/gm0s1 Everything looks good with 4K alignment, and freebsd-ufs first: gpart show =>63 3907029104 mirror/gm0 MBR (1.8T) 63 63 - free - (31k) 126 3907028979 1 freebsd [active] (1.8T) 3907029105 62 - free - (31k) => 0 3907028979 mirror/gm0s1 BSD (1.8T) 0 2- free - (1.0k) 2 3890216960 1 freebsd-ufs (1.8T) 389021696216812016 2 freebsd-swap (8.0G) 3907028978 1- free - (512B) After newfs, I was able to dump/restore to transfer the installed system from ada1 to gm0 (which is 9.1-RC3 now). The thing I wonder about now: Should newfs include -S 4096? I used: newfs -U /dev/mirror/gm0s1a Will this lead to 512 byte sector access to the disk through the file system? Will this impact performance or longevity of the mirror? Thanks again for the sage advice! johnea ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: gpt booting (Was: Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3)
On Wed, 21 Nov 2012, Arthur Chance wrote: On 11/21/12 05:11, Warren Block wrote: gptboot looks for the first UFS partition. Maybe /boot/boot can be modified to do that also. It's a little more complicated than that Warren. AIUI gptboot first looks (in partition order) for partitions with both the bootme and bootonce attributes set. If it doesn't find any, or if they all failed to boot it then tries booting partitions with just the bootme attribute. It only boots the first UFS partition if no partitions have the bootme attribute set, and IIRC that is for compatibility with the 8.x gptboot which didn't know the boot* attributes. Confusingly, there's no manual page for gptboot to document this. It's sort of implicit in the gpart manual page, in the section on ATTRIBUTES for GPT, but the best way to understand it is to read the code for gptfind in /usr/src/sys/boot/common/gpt.c Well, yes. The point is that gptboot doesn't just assume that p2, say, is where the bootable UFS partition must be. I've also noted the lack of a gptboot man page, and it's on my long list of Things That Should Be Done. There was a thread on -doc: http://lists.freebsd.org/pipermail/freebsd-doc/2012-June/020060.html Help would be greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
gpt booting (Was: Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3)
On 11/21/12 05:11, Warren Block wrote: gptboot looks for the first UFS partition. Maybe /boot/boot can be modified to do that also. It's a little more complicated than that Warren. AIUI gptboot first looks (in partition order) for partitions with both the bootme and bootonce attributes set. If it doesn't find any, or if they all failed to boot it then tries booting partitions with just the bootme attribute. It only boots the first UFS partition if no partitions have the bootme attribute set, and IIRC that is for compatibility with the 8.x gptboot which didn't know the boot* attributes. Confusingly, there's no manual page for gptboot to document this. It's sort of implicit in the gpart manual page, in the section on ATTRIBUTES for GPT, but the best way to understand it is to read the code for gptfind in /usr/src/sys/boot/common/gpt.c ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On Tue, 20 Nov 2012, free...@johnea.net wrote: On 2012-11-20 14:28, Gary Aitken wrote: On 11/20/12 13:34, free...@johnea.net wrote: freebsd-update upgrade -r 9.1-RC3 ... "Not UFS" "No ada0" "No boot" Seems like it isn't supposed to work for 9.1-RC2 I previously used binary update to migrate from 9.0 to 9.1, via: freebsd-update upgrade -r 9.1-RC1 freebsd-update install reboot freebsd-update install reboot I'm starting to think having the swap partition in gm0s1a and the booting UFS partition in ada0s1b is the problem: http://forums.freebsd.org/showthread.php?t=31954 The "Not UFS" error comes immediately on boot. If I boot from rescue media, I can start the gmirror, mount it and chroot into it. The whole install seems fine except for the first stage boot loader finding the UFS partition. A handy bootloader config trick would be greatly appreciated! boot(8) says The automatic boot will attempt to load /boot/loader from partition `a' of either the floppy or the hard disk. You could try setting the correct device path in /boot/boot.config, but I suspect that won't be read until too late. gptboot looks for the first UFS partition. Maybe /boot/boot can be modified to do that also. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On 2012-11-20 14:28, Gary Aitken wrote: > On 11/20/12 13:34, free...@johnea.net wrote: >> freebsd-update upgrade -r 9.1-RC3 ... >> "Not UFS" "No ada0" "No boot" > > Seems like it isn't supposed to work for 9.1-RC2 > I previously used binary update to migrate from 9.0 to 9.1, via: freebsd-update upgrade -r 9.1-RC1 freebsd-update install reboot freebsd-update install reboot I'm starting to think having the swap partition in gm0s1a and the booting UFS partition in ada0s1b is the problem: http://forums.freebsd.org/showthread.php?t=31954 The "Not UFS" error comes immediately on boot. If I boot from rescue media, I can start the gmirror, mount it and chroot into it. The whole install seems fine except for the first stage boot loader finding the UFS partition. A handy bootloader config trick would be greatly appreciated! johnea ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On 11/20/12 13:34, free...@johnea.net wrote: > > Hello, > > I recently installed a 9.1-RC2 system using gmirror with MBR, and swap in > first bsdlabel. > > orsbackup# gpart show > =>63 3907029104 mirror/gm0 MBR (1.8T) >63 63 - free - (31k) > 126 3907028979 1 freebsd [active] (1.8T) >3907029105 62 - free - (31k) > > => 0 3907028979 mirror/gm0s1 BSD (1.8T) > 0 2- free - (1.0k) > 216777216 1 freebsd-swap (8.0G) > 16777218 3890251760 2 freebsd-ufs (1.8T) >3907028978 1- free - (512B) > > The drive was setup with the following commands: > > orsbackup# gpart create -s MBR mirror/gm0 > mirror/gm0 created > orsbackup# gpart add -t freebsd -a 4k mirror/gm0 > # ignored "mirror/gm0s1 added, but partition is not aligned on 4096 bytes" > # create the bsdlabel partitions in slice 1 (s1) > orsbackup# gpart create -s BSD mirror/gm0s1 > orsbackup# gpart add -t freebsd-swap -a 4k -s 8g mirror/gm0s1 > orsbackup# gpart add -t freebsd-ufs -a 4k mirror/gm0s1 > # put bootcode on the MBR and mark the first slice active > orsbackup# gpart bootcode -b /boot/mbr mirror/gm0 > orsbackup# gpart set -a active -i 1 mirror/gm0 > # put bootcode on the bsdlabel > orsbackup# gpart bootcode -b /boot/boot mirror/gm0s1 > > > The system rebooted several times without issue. This system is a testbed for > 9.1 and is not yet deployed as a production server. > > I thought I'd update to 9.1-RC3, so I ran: > > freebsd-update upgrade -r 9.1-RC3 > freebsd-update install > reboot > > The system won't boot and complains about: > > "Not UFS" "No ada0" "No boot" > > Before I charge ahead with reissuing the gpart bootcode commands I thought > I'd: > > a) make others aware there may be issues in freebsd-update with the 9.1 > release candidates > > b) ask about the best way to resolve this bootloader issue. > > Thanks you for any pointers in resolving this bootloader issue! > > johnea Not sure, but this might apply: The freebsd-update tool is used to fetch, install, and rollback binary updates to the FreeBSD base system. Note that updates are only available if they are being built for the FreeBSD release and architecture being used; in particular, the FreeBSD Security Team only builds updates for releases shipped in binary form by the FreeBSD Release Engineering Team, e.g., FreeBSD 7.3-RELEASE and FreeBSD 8.0-RELEASE, but not FreeBSD 6.3-STABLE or FreeBSD 9.0-CURRENT. Seems like it isn't supposed to work for 9.1-RC2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: boot problem
Attached sata Disk. it is not usb Namely, The sata disk is attached to new machine. It is connected by sata cable. On Thu, 21 Apr 2011, Yavuz Maşlak wrote: > I have a freebsd7 box. I also have another PC . I removed the disk from > freebsd installed machine and fixed it to the another PC. How is it connected? USB? > It Works but there is a problem. > While opening the server it waits at boot > > FreeBSD/i386 boot: > Default:0:ad(0,a)/boot/loader > Boot: > > If I press enter, the server opens and it Works. > > How can I get rid off this ? Adding kern.cam.boot_delay=1 to /boot/loader.conf helps with some USB drives. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: boot problem
On Thu, 21 Apr 2011, Yavuz Maşlak wrote: I have a freebsd7 box. I also have another PC . I removed the disk from freebsd installed machine and fixed it to the another PC. How is it connected? USB? It Works but there is a problem. While opening the server it waits at boot FreeBSD/i386 boot: Default:0:ad(0,a)/boot/loader Boot: If I press enter, the server opens and it Works. How can I get rid off this ? Adding kern.cam.boot_delay=1 to /boot/loader.conf helps with some USB drives.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: boot problem after custom kernel
On Mon, Aug 06, 2007 at 03:29:14PM +1000, Paul Fraser wrote: > Alain G. Fabry wrote: > >First 'unload kernel' followed by 'boot /boot/kernel.GENERIC/kernel', but > >it mentions > >that it cannot find the kernel. > > > > > > >What can I do to boot my GENERIC kernel so I can rebuild from it and my > >system will boot > >normal again. > > Hi Alain, > > Try replacing 'kernel.GENERIC' with 'kernel.old' in your example. If you > don't remember actually making a copy of your kernel and naming it > kernel.GENERIC, you'll be more likely to succeed with kernel.old. > > -- > Regards, > > Paul Fraser // Independent Technical Consultant // Ph: +61 405 341 905 > // furyc0de.net > > This correspondence and any related attachments are confidential. > Distribution, reproduction, or release (public domain or otherwise) > without the author's prior written consent is STRICTLY FORBIDDEN. > Failure to distribute any of the aforementioned without this footer > (intact and unmodified) is also STRICTLY FORBIDDEN. Failure to abide by > these terms and conditions can result in legal action. > > If you have received this correspondence in error, or believe any of > these terms have been breached, you are requested to contact the author > immediately and take steps to destroy all copies in your possession. > Thanks, it works. Somehow I though since the old seems to be in italics that you needed to change it with the old kernel name (which in my case was GENERIC) Back up and running. Alain > PGP KeyID: 0x64E635B1 > Keyserver: pgp.mit.edu:11371 > Key fingerprint: CDA3 0797 68B9 0EC1 D4D3 A7B9 D7D7 4924 64E6 35B1 > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem after custom kernel
Alain G. Fabry wrote: First 'unload kernel' followed by 'boot /boot/kernel.GENERIC/kernel', but it mentions that it cannot find the kernel. What can I do to boot my GENERIC kernel so I can rebuild from it and my system will boot normal again. Hi Alain, Try replacing 'kernel.GENERIC' with 'kernel.old' in your example. If you don't remember actually making a copy of your kernel and naming it kernel.GENERIC, you'll be more likely to succeed with kernel.old. -- Regards, Paul Fraser // Independent Technical Consultant // Ph: +61 405 341 905 // furyc0de.net This correspondence and any related attachments are confidential. Distribution, reproduction, or release (public domain or otherwise) without the author's prior written consent is STRICTLY FORBIDDEN. Failure to distribute any of the aforementioned without this footer (intact and unmodified) is also STRICTLY FORBIDDEN. Failure to abide by these terms and conditions can result in legal action. If you have received this correspondence in error, or believe any of these terms have been breached, you are requested to contact the author immediately and take steps to destroy all copies in your possession. PGP KeyID: 0x64E635B1 Keyserver: pgp.mit.edu:11371 Key fingerprint: CDA3 0797 68B9 0EC1 D4D3 A7B9 D7D7 4924 64E6 35B1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem after custom kernel
Alain G. Fabry wrote: First 'unload kernel' followed by 'boot /boot/kernel.GENERIC/kernel', but it mentions that it cannot find the kernel. try, at loader prompt: unload kernel load /boot/kernel.old/kernel boot -- Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708 Senior System Admin - Riderway, Inc. http://riderway.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem after GEOM setup
On Sat, 2007-04-21 at 11:39 -0400, Robert Fitzpatrick wrote: > Following the doc below, I am trying to mirror an existing disk, ad0, > which holds the root and /usr partitions (a second disk holds /var). I > have an exact same disk in as ad2 in the system and did everything in > this document top section through dumping the data and setting up > /etc/fstab and loader.conf. I created the /boot.config as shown except I > replaced the '1' with '2' just like I did for the other steps, but this > does not appear correct. I now stall when booting at the boot: prompt. > What can I type in the boot: prompt to get back in my system and make > the necessary changes? Also, what should the /boot.config look like to > boot to my new disk and continue through the steps for adding the first > disk to the mirror? I guess it looks like this now: 1:ad(2,a)/boot/loader. > > http://people.freebsd.org/~rse/mirror/ > I was able to recover with a FreeSBIE and go back, seems I was close. I have the GEOM working now as shown below. However, after successfully synchronizing and doing a reboot, it shows up DEGRADED after every reboot and synchronizes again, is that normal? genoa# gmirror list Geom name: gm0 State: DEGRADED Components: 2 Balance: round-robin Slice: 4096 Flags: NONE SyncID: 1 ID: 4224071626 Providers: 1. Name: mirror/gm0 Mediasize: 15364338688 (14G) Sectorsize: 512 Mode: r4w3e2 Consumers: 1. Name: ad0 Mediasize: 15364339200 (14G) Sectorsize: 512 Mode: r0w1e1 State: SYNCHRONIZING Priority: 0 Flags: DIRTY, SYNCHRONIZING SyncID: 1 Synchronized: 28% ID: 4099754703 2. Name: ad2 Mediasize: 15364339200 (14G) Sectorsize: 512 Mode: r4w3e3 State: ACTIVE Priority: 0 Flags: DIRTY SyncID: 1 ID: 3454124143 Geom name: gm0.sync Consumers: 1. Name: mirror/gm0 Mediasize: 15364338688 (14G) Sectorsize: 512 Mode: r1w0e0 -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem
On Tue, Jun 27, 2006 at 11:49:59AM -0700, Winston wrote: > > Any hint? > Find a live cd and boot it. Mount partition and edit files that you munged. -- Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem - how can I access the file system
Robert Fitzpatrick wrote: I made a mistake to my /boot/loader.conf file and now the system hangs after pressing F1 and before the boot options menu. How can I access the file to edit it? I have the install CD, but can't seem to figure out how to get to the file system. Hi Robert, I'd get FreesBie (live FreeBSD CD, like knoppix is to linux) from http://www.freesbie.org/ and use it. it's a fully working system in a CD so you wont have to fight with the restricted shells of fixit CDs,etc (which most of the times I've found to be more frustrating than the actual problem I'm trying to solve). good luck, Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem - how can I access the file system
http://uranus.it.swin.edu.au/~jn/linux/ and specifically: http://uranus.it.swin.edu.au/~jn/linux/rawwrite.htm these are all windows programs that take away the frustration of installing linux. however freebsd and any os follows the same concept when it comes to boot disks (.img) - so give rawwrite a try. if you really want to do it "unix style" via dd he has a windows copy of dd on there: http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm Let me know if you need any help making the fixit disk via any of the utilities i just mentioned. -Ben Robert Fitzpatrick wrote: On Sat, 2005-09-03 at 13:31 -0500, Kevin Kinsey wrote: What resources do you have? Don't have another FreeBSD machine at this location. I have my SuSE 9.2 linux workstation and Windows 2003 server machine. 2] Fixit CD or Fixit floppy. Available via FTP from ftp.freebsd.org. I tried the Fixit CD (disc 2) and it says 'ldconfig could not create the ld.so hints' and that my dynamic executables from the disc most likely won't work. When I Alt+F4, typing any command such as 'ls' gives me a segmentation fault. I am running 5.3 on a old AMD 500 with 512MB RAM. Not sure how to get the images for floppies on to my floppy. The 'dd' command does not seem to work in my linux env and I don't find the fdimage.exe for Windows. Appreciate any help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem - how can I access the file system
On Sat, 2005-09-03 at 13:31 -0500, Kevin Kinsey wrote: > What resources do you have? Don't have another FreeBSD machine at this location. I have my SuSE 9.2 linux workstation and Windows 2003 server machine. > 2] Fixit CD or Fixit floppy. Available via FTP > from ftp.freebsd.org. I tried the Fixit CD (disc 2) and it says 'ldconfig could not create the ld.so hints' and that my dynamic executables from the disc most likely won't work. When I Alt+F4, typing any command such as 'ls' gives me a segmentation fault. I am running 5.3 on a old AMD 500 with 512MB RAM. Not sure how to get the images for floppies on to my floppy. The 'dd' command does not seem to work in my linux env and I don't find the fdimage.exe for Windows. Appreciate any help. -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem - how can I access the file system
Robert Fitzpatrick wrote: I made a mistake to my /boot/loader.conf file and now the system hangs after pressing F1 and before the boot options menu. How can I access the file to edit it? I have the install CD, but can't seem to figure out how to get to the file system. When it happened to me, I had the good fortune to have another FBSD system nearby. Mounted it there, edited mistake, voila. What resources do you have? Further thoughts: 1] Boot off of a live CD (Matt Olander posted a link to a nice, fairly small one on advocacy@ yesterday, IIRC). 2] Fixit CD or Fixit floppy. Available via FTP from ftp.freebsd.org. 3] sysinstall's emergency holographic shell - dunno if it can edit. Might be able to cp a backup, though, if you have one. HTH, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem - how can I access the file system
On Sat, 2005-09-03 at 13:31 -0500, Kevin Kinsey wrote: > >I made a mistake to my /boot/loader.conf file and now the system hangs > >after pressing F1 and before the boot options menu. How can I access the > >file to edit it? I have the install CD, but can't seem to figure out how > >to get to the file system. > 3] sysinstall's emergency holographic shell - >dunno if it can edit. Might be able to cp >a backup, though, if you have one. > I booted from CD and initiated the holographic shell, where can I find help on how to access the drive and edit the file? Thanks. -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem RESOLVED
On Wed, 2005-08-31 at 17:26, Robert Slade wrote: > On Wed, 2005-08-31 at 00:21, Vizion wrote: > > On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to > > the > > dialogue on- > > Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > > > >On Tue, 2005-08-30 at 21:20, Vizion wrote: > > >> On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to > > >> the dialogue on- > > >> > > >> Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >> >On Tue, 2005-08-30 at 20:10, Vizion wrote: > > >> >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed > > >> >> to the dialogue on- > > >> >> > > >> >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >> >> >Hiya, > > >> >> > > > >> >> >I've been working on this beasty on and off for some time. It's a > > >> >> >Quad > > >> >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > > >> >> >controller setup as 2 raid arrays + 1 spare. > > >> >> > > > >> >> >The machine works fine with 5.4 release #0 with the supplied generic > > >> >> >kernel. > > >> >> > > > >> >> >The problem(s) I have been having are: > > >> >> > > > >> >> >1. When I recompiled the Kernel with SMP support, I get random > > >> >> > reboots. It also fails to boot sometimes failing at the point after > > >> >> > waiting for the scsi drives to settle. I get some error codes and > > >> >> > Fbsd fails to find the boot device. > > >> >> > > > >> >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > > >> >> >support. This does to boot at all. It gets as far as the waiting 15s > > >> >> > for scsi devices to settle, then (appears to) reset the scsi > > >> >> > controller and immediately tries to access the drives (does not > > >> >> > wait). I have tried recompiling with scsi_delay set to 3 (30s) > > >> >> > with no change. > > >> >> > > > >> >> >I have checked dmesg and message logs but there is nothing related to > > >> >> >the problem(s) there. > > >> >> > > > >> >> >I have gone back to the 5.4 release #0 single processor kernel for > > >> >> >now > > >> >> >which is a shame as the machine is slow without the multi processor > > >> >> >support. > > >> >> > > > >> >> >The only thing out of the ordinary I have noted is a tx underunn -- > > >> >> >increasing threshold to 512 bytes message which appears related to > > >> >> >running kde remotely via vncserver and tinync. > > >> >> > > > >> >> >Any ideas, I can send conf files etc if needed. > > >> >> > > > >> >> >Thanks > > >> >> > > > >> >> >Rob > > >> >> > > >> >> What are your bios setting? > > >> >> My guess is that you have not made the right setting using the > > >> >> siftware > > >> >> and configuration utilities > > >> >> david > > >> > > > >> >David, > > >> > > > >> >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk > > >> >geometry) and the machine passes all the diagnostics. > > >> > > > >> >Rob > > >> > > >> I cannot remember - but I have sneaking notion that you need to set it as > > >> linux > > > > > >Tried that too :-). I think that the problem is that with 5.4 release #2 > > >it is trying to access that scsi drives immediately then inducing the > > >kernel panic for 15s. Rather than inducing the panic 1st. > > > > > >Rob > > > > > > > Did you follow my suggestion and search the HP resources with freebsd and > > your > > model. I have had the same problem myself I am pretty certain it was fixed > > by changes using the Proliant Essrntial Foundation Pack.. but my memory may > > not be accurate. > > david > > David, > > I did update the system and controller ROMs whne the machine was running > windows. I have been on the HP site and as far as I can tell I have the > latest. > > Rob For the record, lucking under SCO Unix is an update to the Raid Controller firmware which fixes the problem. You do need Dos or Windows to create the self booting disks. Only disk 1 is needed for the SMART 2P controller. The update appears to be only listed under SC Unix though. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Wed, 2005-08-31 at 00:21, Vizion wrote: > On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the > dialogue on- > Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >On Tue, 2005-08-30 at 21:20, Vizion wrote: > >> On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to > >> the dialogue on- > >> > >> Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > >> >On Tue, 2005-08-30 at 20:10, Vizion wrote: > >> >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed > >> >> to the dialogue on- > >> >> > >> >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: > >> >> >Hiya, > >> >> > > >> >> >I've been working on this beasty on and off for some time. It's a Quad > >> >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > >> >> >controller setup as 2 raid arrays + 1 spare. > >> >> > > >> >> >The machine works fine with 5.4 release #0 with the supplied generic > >> >> >kernel. > >> >> > > >> >> >The problem(s) I have been having are: > >> >> > > >> >> >1. When I recompiled the Kernel with SMP support, I get random > >> >> > reboots. It also fails to boot sometimes failing at the point after > >> >> > waiting for the scsi drives to settle. I get some error codes and > >> >> > Fbsd fails to find the boot device. > >> >> > > >> >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > >> >> >support. This does to boot at all. It gets as far as the waiting 15s > >> >> > for scsi devices to settle, then (appears to) reset the scsi > >> >> > controller and immediately tries to access the drives (does not > >> >> > wait). I have tried recompiling with scsi_delay set to 3 (30s) > >> >> > with no change. > >> >> > > >> >> >I have checked dmesg and message logs but there is nothing related to > >> >> >the problem(s) there. > >> >> > > >> >> >I have gone back to the 5.4 release #0 single processor kernel for now > >> >> >which is a shame as the machine is slow without the multi processor > >> >> >support. > >> >> > > >> >> >The only thing out of the ordinary I have noted is a tx underunn -- > >> >> >increasing threshold to 512 bytes message which appears related to > >> >> >running kde remotely via vncserver and tinync. > >> >> > > >> >> >Any ideas, I can send conf files etc if needed. > >> >> > > >> >> >Thanks > >> >> > > >> >> >Rob > >> >> > >> >> What are your bios setting? > >> >> My guess is that you have not made the right setting using the siftware > >> >> and configuration utilities > >> >> david > >> > > >> >David, > >> > > >> >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk > >> >geometry) and the machine passes all the diagnostics. > >> > > >> >Rob > >> > >> I cannot remember - but I have sneaking notion that you need to set it as > >> linux > > > >Tried that too :-). I think that the problem is that with 5.4 release #2 > >it is trying to access that scsi drives immediately then inducing the > >kernel panic for 15s. Rather than inducing the panic 1st. > > > >Rob > > > > Did you follow my suggestion and search the HP resources with freebsd and > your > model. I have had the same problem myself I am pretty certain it was fixed > by changes using the Proliant Essrntial Foundation Pack.. but my memory may > not be accurate. > david David, I did update the system and controller ROMs whne the machine was running windows. I have been on the HP site and as far as I can tell I have the latest. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Wed, 2005-08-31 at 07:01, Ted Mittelstaedt wrote: > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] Behalf Of Vizion > >Sent: Tuesday, August 30, 2005 4:21 PM > >To: freebsd-questions@freebsd.org > >Cc: Robert Slade > >Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem > > > > > >Did you follow my suggestion and search the HP resources with > >freebsd and your > >model. I have had the same problem myself I am pretty certain > >it was fixed > >by changes using the Proliant Essrntial Foundation Pack.. but > >my memory may > >not be accurate. > > Yeah, what a awful design! You have to load an entire full-blown > Windows install just to update the microcode in the SCSI raid > controller. I saw they had done this the last time I setup a > Compaq server and nearly barfed. > > You can still firmware update the machines' BIOS with a bootable > floppy but that's it. To get anything else, helo Windows! > > At least you get the satisfaction of scratching it off once you've > done the update. > > Ted > -- Thanks Ted & David, The HP site does not turn up anything about FreeBSD and the Proliant. However I have found out that the Smart-2 family controllers do have an update. There is a Linux version of the flash utility so I'll try that first. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Proliant 5000 sever Fbsd 5.4 (re)boot problem
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Vizion >Sent: Tuesday, August 30, 2005 4:21 PM >To: freebsd-questions@freebsd.org >Cc: Robert Slade >Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem > > >Did you follow my suggestion and search the HP resources with >freebsd and your >model. I have had the same problem myself I am pretty certain >it was fixed >by changes using the Proliant Essrntial Foundation Pack.. but >my memory may >not be accurate. Yeah, what a awful design! You have to load an entire full-blown Windows install just to update the microcode in the SCSI raid controller. I saw they had done this the last time I setup a Compaq server and nearly barfed. You can still firmware update the machines' BIOS with a bootable floppy but that's it. To get anything else, helo Windows! At least you get the satisfaction of scratching it off once you've done the update. Ted -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.17/85 - Release Date: 8/30/2005 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 16:21, the author Vizion contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: >On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the >dialogue on- > > Is this any use: http://ezine.daemonnews.org/23/cpqraid.html -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: >On Tue, 2005-08-30 at 21:20, Vizion wrote: >> On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to >> the dialogue on- >> >> Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: >> >On Tue, 2005-08-30 at 20:10, Vizion wrote: >> >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed >> >> to the dialogue on- >> >> >> >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: >> >> >Hiya, >> >> > >> >> >I've been working on this beasty on and off for some time. It's a Quad >> >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid >> >> >controller setup as 2 raid arrays + 1 spare. >> >> > >> >> >The machine works fine with 5.4 release #0 with the supplied generic >> >> >kernel. >> >> > >> >> >The problem(s) I have been having are: >> >> > >> >> >1. When I recompiled the Kernel with SMP support, I get random >> >> > reboots. It also fails to boot sometimes failing at the point after >> >> > waiting for the scsi drives to settle. I get some error codes and >> >> > Fbsd fails to find the boot device. >> >> > >> >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP >> >> >support. This does to boot at all. It gets as far as the waiting 15s >> >> > for scsi devices to settle, then (appears to) reset the scsi >> >> > controller and immediately tries to access the drives (does not >> >> > wait). I have tried recompiling with scsi_delay set to 3 (30s) >> >> > with no change. >> >> > >> >> >I have checked dmesg and message logs but there is nothing related to >> >> >the problem(s) there. >> >> > >> >> >I have gone back to the 5.4 release #0 single processor kernel for now >> >> >which is a shame as the machine is slow without the multi processor >> >> >support. >> >> > >> >> >The only thing out of the ordinary I have noted is a tx underunn -- >> >> >increasing threshold to 512 bytes message which appears related to >> >> >running kde remotely via vncserver and tinync. >> >> > >> >> >Any ideas, I can send conf files etc if needed. >> >> > >> >> >Thanks >> >> > >> >> >Rob >> >> >> >> What are your bios setting? >> >> My guess is that you have not made the right setting using the siftware >> >> and configuration utilities >> >> david >> > >> >David, >> > >> >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk >> >geometry) and the machine passes all the diagnostics. >> > >> >Rob >> >> I cannot remember - but I have sneaking notion that you need to set it as >> linux > >Tried that too :-). I think that the problem is that with 5.4 release #2 >it is trying to access that scsi drives immediately then inducing the >kernel panic for 15s. Rather than inducing the panic 1st. > >Rob > Did you follow my suggestion and search the HP resources with freebsd and your model. I have had the same problem myself I am pretty certain it was fixed by changes using the Proliant Essrntial Foundation Pack.. but my memory may not be accurate. david >___ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tue, 2005-08-30 at 21:20, Vizion wrote: > On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to the > dialogue on- > Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >On Tue, 2005-08-30 at 20:10, Vizion wrote: > >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to > >> the dialogue on- > >> > >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: > >> >Hiya, > >> > > >> >I've been working on this beasty on and off for some time. It's a Quad > >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > >> >controller setup as 2 raid arrays + 1 spare. > >> > > >> >The machine works fine with 5.4 release #0 with the supplied generic > >> >kernel. > >> > > >> >The problem(s) I have been having are: > >> > > >> >1. When I recompiled the Kernel with SMP support, I get random reboots. > >> >It also fails to boot sometimes failing at the point after waiting for > >> >the scsi drives to settle. I get some error codes and Fbsd fails to find > >> >the boot device. > >> > > >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > >> >support. This does to boot at all. It gets as far as the waiting 15s for > >> >scsi devices to settle, then (appears to) reset the scsi controller and > >> >immediately tries to access the drives (does not wait). I have tried > >> >recompiling with scsi_delay set to 3 (30s) with no change. > >> > > >> >I have checked dmesg and message logs but there is nothing related to > >> >the problem(s) there. > >> > > >> >I have gone back to the 5.4 release #0 single processor kernel for now > >> >which is a shame as the machine is slow without the multi processor > >> >support. > >> > > >> >The only thing out of the ordinary I have noted is a tx underunn -- > >> >increasing threshold to 512 bytes message which appears related to > >> >running kde remotely via vncserver and tinync. > >> > > >> >Any ideas, I can send conf files etc if needed. > >> > > >> >Thanks > >> > > >> >Rob > >> > >> What are your bios setting? > >> My guess is that you have not made the right setting using the siftware > >> and configuration utilities > >> david > > > >David, > > > >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk > >geometry) and the machine passes all the diagnostics. > > > >Rob > > I cannot remember - but I have sneaking notion that you need to set it as > linux Tried that too :-). I think that the problem is that with 5.4 release #2 it is trying to access that scsi drives immediately then inducing the kernel panic for 15s. Rather than inducing the panic 1st. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tue, 2005-08-30 at 20:10, Vizion wrote: > On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the > dialogue on- > Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >Hiya, > > > >I've been working on this beasty on and off for some time. It's a Quad > >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > >controller setup as 2 raid arrays + 1 spare. > > > >The machine works fine with 5.4 release #0 with the supplied generic > >kernel. > > > >The problem(s) I have been having are: > > > >1. When I recompiled the Kernel with SMP support, I get random reboots. > >It also fails to boot sometimes failing at the point after waiting for > >the scsi drives to settle. I get some error codes and Fbsd fails to find > >the boot device. > > > >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > >support. This does to boot at all. It gets as far as the waiting 15s for > >scsi devices to settle, then (appears to) reset the scsi controller and > >immediately tries to access the drives (does not wait). I have tried > >recompiling with scsi_delay set to 3 (30s) with no change. > > > >I have checked dmesg and message logs but there is nothing related to > >the problem(s) there. > > > >I have gone back to the 5.4 release #0 single processor kernel for now > >which is a shame as the machine is slow without the multi processor > >support. > > > >The only thing out of the ordinary I have noted is a tx underunn -- > >increasing threshold to 512 bytes message which appears related to > >running kde remotely via vncserver and tinync. > > > >Any ideas, I can send conf files etc if needed. > > > >Thanks > > > >Rob > > > What are your bios setting? > My guess is that you have not made the right setting using the siftware and > configuration utilities > david David, Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk geometry) and the machine passes all the diagnostics. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the dialogue on- Proliant 5000 sever Fbsd 5.4 (re)boot problem: >Hiya, > >I've been working on this beasty on and off for some time. It's a Quad >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid >controller setup as 2 raid arrays + 1 spare. > >The machine works fine with 5.4 release #0 with the supplied generic >kernel. > >The problem(s) I have been having are: > >1. When I recompiled the Kernel with SMP support, I get random reboots. >It also fails to boot sometimes failing at the point after waiting for >the scsi drives to settle. I get some error codes and Fbsd fails to find >the boot device. > >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP >support. This does to boot at all. It gets as far as the waiting 15s for >scsi devices to settle, then (appears to) reset the scsi controller and >immediately tries to access the drives (does not wait). I have tried >recompiling with scsi_delay set to 3 (30s) with no change. > >I have checked dmesg and message logs but there is nothing related to >the problem(s) there. > >I have gone back to the 5.4 release #0 single processor kernel for now >which is a shame as the machine is slow without the multi processor >support. > >The only thing out of the ordinary I have noted is a tx underunn -- >increasing threshold to 512 bytes message which appears related to >running kde remotely via vncserver and tinync. > >Any ideas, I can send conf files etc if needed. > >Thanks > >Rob > What are your bios setting? My guess is that you have not made the right setting using the siftware and configuration utilities david -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Proliant 5000 sever Fbsd 5.4 (re)boot problem
Hiya, I've been working on this beasty on and off for some time. It's a Quad processor 1 Gbyte of memory and 5 scsi drives using the 2p raid controller setup as 2 raid arrays + 1 spare. The machine works fine with 5.4 release #0 with the supplied generic kernel. The problem(s) I have been having are: 1. When I recompiled the Kernel with SMP support, I get random reboots. It also fails to boot sometimes failing at the point after waiting for the scsi drives to settle. I get some error codes and Fbsd fails to find the boot device. 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP support. This does to boot at all. It gets as far as the waiting 15s for scsi devices to settle, then (appears to) reset the scsi controller and immediately tries to access the drives (does not wait). I have tried recompiling with scsi_delay set to 3 (30s) with no change. I have checked dmesg and message logs but there is nothing related to the problem(s) there. I have gone back to the 5.4 release #0 single processor kernel for now which is a shame as the machine is slow without the multi processor support. The only thing out of the ordinary I have noted is a tx underunn -- increasing threshold to 512 bytes message which appears related to running kde remotely via vncserver and tinync. Any ideas, I can send conf files etc if needed. Thanks Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
Hi guys, Just wanted to say thanks for all the helpful suggestions. Played with things and got into the geometry idea as the possible cause. Did some more work, adjusting bios and geometry settings around the disk and just a few minutes ago after yet another go at installing the laptop just booted up! I in fact looked twice to make sure it booted on its own and not with the cd installed, it was not completely inserted and I still pulled the disk out completely to convince myself. What I finally did was to do a fdisk during a FixIT session and marked down the settings. The laptop bios would not take all six digits of the cylinders, so I entered five of them, adjusted the heads, and when setting up the disk during the install of FreeBSD set the geometry of the disk to match what fdisk reported and that seemed to do the trick. It is an older laptop so I guess that it was not designed with a 60G hard drive in mind. The previous drive was only 6G. Big difference. Again, the laptop has booted, and is currently doing some compiling. Hopefully the rest will go without problems, the laptop ran fine with the 6G drive so I am not expecting any other problems. The only real annoying part is that it is a real pain to find detailed info on this western digital drive, Thanks again, Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
At 02:47 PM 8/27/2005, Gary W. Swearingen wrote: Glenn Dawson <[EMAIL PROTECTED]> writes: > I doubt there's nothing wrong with the MBR per se, but if it's looking in the wrong place for the third stage loader > you'll see exactly the problem you have. Where "it's" probably refers to "boot code", not to the MBR, which doesn't look for anything except the confusingly-named "first-stage" boot loader (same as /boot/boot1) in the first sector of your 4th primary partition. Then that loads the second-stage boot loader (same as /boot/boot2) which gives the "boot:" prompt after failing to run /boot/loader and failing to run a kernel. It seems that finding boot1 and boot2 is possible with bad geometry, but finding /boot/loader or the kernel is not. ??? The restriction on where stage 2 finds the stage 3 loader, /boot/loader, is that it must be on the 'a' partition. Something like: /dev/ad0s1a If it's somewhere else, like /dev/ad0s1e, then you'll land at the boot: prompt every time. -Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
At 02:40 PM 8/27/2005, Sean wrote: Glenn Dawson wrote: At 02:13 PM 8/27/2005, Sean wrote: Glenn Dawson wrote: At 06:04 AM 8/27/2005, Sean wrote: Just installed on a new system and I am unable to boot. Currently when that system boots it comes up with what looks like the following example from the handbook >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: from my reading this is a boot2 stage booting from cd and going into Fixit it fdisk shows partition 1, 2, and 3 unused, and Freebsd is on partition 4. I thought it should be on partition 1? How did you arrange the file systems when you installed. Did you use the defaults, or your own layout? The defaults would have given you 5 partitions inside of the first slice. For example: ad0s1a - / ad0s1b - swap ad0s1d - /var ad0s1e - /tmp ad0s1f - /usr Did you not use the 'a' partition for your root file system? Second stage boot code only knows how to find third stage on the 'a' partition. More details on your installation would help in trying to figure out what the problem is. -Glenn Note: on install I choose the Standard boot manager. I created the above partitions you listed manually and specified to my choice sizes, and i did choose 'a', or entire disk on creation. The "entire disk" option is in the screen that lest you create slices, which is completely different from the screen that lets you create your partitions. (a, b, d, e, f, etc) Keep in mind that what is called a "partition" in other OS's is called a slice in FreeBSD. You mentioned above that FreeBSD was installed in partition 4. Assuming that's slice 4, are the device names something like /dev/ads4x. where the x is the partition. Through Fitit, fdisk shows partions 1,2,and 3 unused, and Freebsd sitting in 4. Can you send the output that shows that? bsdlabel shows on /dev/ad0s1 the six partitions, a, b, c, d, e, f /dev/ad0s1 is slice one. (partition 1 in the dos/windows world) Sysinstall, from the boot cd, shows the following disk name: ad0 and freebsd on ad0s1 That is exactly as it should be. disklabel shows ad0s1a, ad0s1d, ad0s1b, ad0s1e, ad0s1f, none of these partitions currently show a mount point, with the exception of b, which is swap. so now am even more puzzled by no mount showing. disklabel output can't give you mount points. Can you provide the output from disklabel? That would help in figuring out what's going on. Here's a sample output from one of my systems: # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD0 0 0 b: 2045600 524288 swap c: 209647620unused0 0 # "raw" part, don't edit d: 524288 25698884.2BSD0 0 0 e: 524288 30941764.2BSD0 0 0 f: 17346298 36184644.2BSD0 0 0 -Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
Glenn Dawson <[EMAIL PROTECTED]> writes: > I doubt there's nothing wrong with the MBR per se, but if it's looking in the > wrong place for the third stage loader > you'll see exactly the problem you have. Where "it's" probably refers to "boot code", not to the MBR, which doesn't look for anything except the confusingly-named "first-stage" boot loader (same as /boot/boot1) in the first sector of your 4th primary partition. Then that loads the second-stage boot loader (same as /boot/boot2) which gives the "boot:" prompt after failing to run /boot/loader and failing to run a kernel. It seems that finding boot1 and boot2 is possible with bad geometry, but finding /boot/loader or the kernel is not. ??? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
Glenn Dawson wrote: At 02:13 PM 8/27/2005, Sean wrote: Glenn Dawson wrote: At 06:04 AM 8/27/2005, Sean wrote: Just installed on a new system and I am unable to boot. Currently when that system boots it comes up with what looks like the following example from the handbook >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: from my reading this is a boot2 stage booting from cd and going into Fixit it fdisk shows partition 1, 2, and 3 unused, and Freebsd is on partition 4. I thought it should be on partition 1? How did you arrange the file systems when you installed. Did you use the defaults, or your own layout? The defaults would have given you 5 partitions inside of the first slice. For example: ad0s1a - / ad0s1b - swap ad0s1d - /var ad0s1e - /tmp ad0s1f - /usr Did you not use the 'a' partition for your root file system? Second stage boot code only knows how to find third stage on the 'a' partition. More details on your installation would help in trying to figure out what the problem is. -Glenn Note: on install I choose the Standard boot manager. I created the above partitions you listed manually and specified to my choice sizes, and i did choose 'a', or entire disk on creation. The "entire disk" option is in the screen that lest you create slices, which is completely different from the screen that lets you create your partitions. (a, b, d, e, f, etc) Keep in mind that what is called a "partition" in other OS's is called a slice in FreeBSD. You mentioned above that FreeBSD was installed in partition 4. Assuming that's slice 4, are the device names something like /dev/ads4x. where the x is the partition. Through Fitit, fdisk shows partions 1,2,and 3 unused, and Freebsd sitting in 4. bsdlabel shows on /dev/ad0s1 the six partitions, a, b, c, d, e, f Sysinstall, from the boot cd, shows the following disk name: ad0 and freebsd on ad0s1 disklabel shows ad0s1a, ad0s1d, ad0s1b, ad0s1e, ad0s1f, none of these partitions currently show a mount point, with the exception of b, which is swap. so now am even more puzzled by no mount showing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
Sean <[EMAIL PROTECTED]> writes: > Just installed on a new system and I am unable to boot. You might get better help if you include details like what you installed. > Currently when that system boots it comes up with what looks like the > following example from the handbook > > >> FreeBSD/i386 BOOT > Default: 0:ad(0,a)/kernel > boot: Of course, standard 5.x kernel is in /boot/kernel/kernel > booting from cd and going into Fixit it fdisk shows partition 1, 2, and 3 > unused, and Freebsd is on partition 4. > I thought it should be on partition 1? I suppose you've tried 0:ad(3,a)/kernel but maybe not: 0:ad(3,a)/boot/loader but I doubt if either will work because it's supposed to be done automatically. But if you got to the "boot:" prompt, you shouldn't need to worry about the boot manager (i.e., the MBR). It looks like the system is reading the boot records at the start of some FreeBSD primary partition (presumably, the 4th) and it should then try to run /boot/loader. Some disk geometry problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
At 02:13 PM 8/27/2005, Sean wrote: Glenn Dawson wrote: At 06:04 AM 8/27/2005, Sean wrote: Just installed on a new system and I am unable to boot. Currently when that system boots it comes up with what looks like the following example from the handbook >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: from my reading this is a boot2 stage booting from cd and going into Fixit it fdisk shows partition 1, 2, and 3 unused, and Freebsd is on partition 4. I thought it should be on partition 1? How did you arrange the file systems when you installed. Did you use the defaults, or your own layout? The defaults would have given you 5 partitions inside of the first slice. For example: ad0s1a - / ad0s1b - swap ad0s1d - /var ad0s1e - /tmp ad0s1f - /usr Did you not use the 'a' partition for your root file system? Second stage boot code only knows how to find third stage on the 'a' partition. More details on your installation would help in trying to figure out what the problem is. -Glenn Note: on install I choose the Standard boot manager. I have tried playing with fdisk and disklabel to try to cure this problem, but continually get the example shown above. With none of the above efforts working I have tried changing the boot manager and no luck, both by reinstalling and just by using sysinstall to modify the boot manager.I did get F1 FreeBSD when trying the FreeBSD boot manager option, but it still did not start the system. Thanks Sean I created the above partitions you listed manually and specified to my choice sizes, and i did choose 'a', or entire disk on creation. The "entire disk" option is in the screen that lest you create slices, which is completely different from the screen that lets you create your partitions. (a, b, d, e, f, etc) Keep in mind that what is called a "partition" in other OS's is called a slice in FreeBSD. You mentioned above that FreeBSD was installed in partition 4. Assuming that's slice 4, are the device names something like /dev/ads4x. where the x is the partition. No matter how I approach this problem I always wind up in the same place. I am guessing now that the MBR has a problem. I doubt there's nothing wrong with the MBR per se, but if it's looking in the wrong place for the third stage loader you'll see exactly the problem you have. -Glenn Thanks Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
Glenn Dawson wrote: At 06:04 AM 8/27/2005, Sean wrote: Just installed on a new system and I am unable to boot. Currently when that system boots it comes up with what looks like the following example from the handbook >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: from my reading this is a boot2 stage booting from cd and going into Fixit it fdisk shows partition 1, 2, and 3 unused, and Freebsd is on partition 4. I thought it should be on partition 1? How did you arrange the file systems when you installed. Did you use the defaults, or your own layout? The defaults would have given you 5 partitions inside of the first slice. For example: ad0s1a - / ad0s1b - swap ad0s1d - /var ad0s1e - /tmp ad0s1f - /usr Did you not use the 'a' partition for your root file system? Second stage boot code only knows how to find third stage on the 'a' partition. More details on your installation would help in trying to figure out what the problem is. -Glenn Note: on install I choose the Standard boot manager. I have tried playing with fdisk and disklabel to try to cure this problem, but continually get the example shown above. With none of the above efforts working I have tried changing the boot manager and no luck, both by reinstalling and just by using sysinstall to modify the boot manager.I did get F1 FreeBSD when trying the FreeBSD boot manager option, but it still did not start the system. Thanks Sean I created the above partitions you listed manually and specified to my choice sizes, and i did choose 'a', or entire disk on creation. No matter how I approach this problem I always wind up in the same place. I am guessing now that the MBR has a problem. Thanks Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem (stage 2 boot?)
At 06:04 AM 8/27/2005, Sean wrote: Just installed on a new system and I am unable to boot. Currently when that system boots it comes up with what looks like the following example from the handbook >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: from my reading this is a boot2 stage booting from cd and going into Fixit it fdisk shows partition 1, 2, and 3 unused, and Freebsd is on partition 4. I thought it should be on partition 1? How did you arrange the file systems when you installed. Did you use the defaults, or your own layout? The defaults would have given you 5 partitions inside of the first slice. For example: ad0s1a - / ad0s1b - swap ad0s1d - /var ad0s1e - /tmp ad0s1f - /usr Did you not use the 'a' partition for your root file system? Second stage boot code only knows how to find third stage on the 'a' partition. More details on your installation would help in trying to figure out what the problem is. -Glenn Note: on install I choose the Standard boot manager. I have tried playing with fdisk and disklabel to try to cure this problem, but continually get the example shown above. With none of the above efforts working I have tried changing the boot manager and no luck, both by reinstalling and just by using sysinstall to modify the boot manager.I did get F1 FreeBSD when trying the FreeBSD boot manager option, but it still did not start the system. Thanks Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot problem
On 7/28/05, asd asd <[EMAIL PROTECTED]> wrote: > Hello! > I have problem with booting FreeBSD 5.4 on my laptop Toshiba Satellite > 2410-304: > sometimes it boots without problem but sometimes it stops at line "uhci0: > 82801CA/CAM (ICH3) USB controller USB-A> port 0xefe0-0xefff irq 11 at device > 29.0 on pci0". Previous line is initialization of the Nvidia Grforce4 420Go > graphic adapter. > Any idea what could be causing this problem? Is there any USB device attached to the laptop? Can you reproduce the problem when nothing is attached to it? -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements "We live less by imagination than despite it" - Rockwell Kent, "N by E" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
Sorry.My linux kernel does support ufs.Anyway for working with ufs on linux see http://ufs-linux.sourceforge.net/ Sorry for the trouble. On Sat, 07 May 2005 18:14:50 +0530, "Koushik Narayanan" <[EMAIL PROTECTED]> said: > Thanks for helping.I couldn't do anything with the fixit disk.Is there > some method or tool using which I can copy all files in the ufs partiton > to some other partition using DOS,Windows,or Linux(my kernel won't > support ufs.) .Something like ltools which allows me to copy,delete > files in ext2 partition using windows. > If I could do so..then I can format those partitions and re-install > FreeBSD.. > THanks. > Koushik Narayanan > On Fri, 6 May 2005 05:49:59 +0200, "Emanuel Strobl" > <[EMAIL PROTECTED]> said: > > Am Freitag, 6. Mai 2005 03:59 schrieb Koushik Narayanan: > > > Hello, > > > I have a PC with Windows XP,FreeBSD-5.3 and Linux(Fedora).I use GRUB as > > > my boot manager and I boot into FreeBSD using chainloader. > > > I have XP and FreeBSD on primary partitions.I had a linux primary > > > partion apart from these.I wanted to convert that to UFS2 as my /usr > > > partition (FreeBSD) was almost full.I did that using bsdlabel and mkfs. > > > After that the fdisk print output in linux showed the recently formated > > > partition as type Linux.So I installed linux-fdisk using the ports > > > collection and try to change the system-id of that partition,but it did > > > not work.I then booted into linux and did the same using fdisk.This time > > > it worked.But after that FreeBSD does not boot.(I don't see the rotating > > > / and the loader.The system freezes and even numlock does not work )Here > > > is the fdisk print output from linux: > > > > > > Disk /dev/hda: 20.0 GB, 20060135424 bytes > > > 255 heads, 63 sectors/track, 2438 cylinders > > > Units = cylinders of 16065 * 512 = 8225280 bytes > > > > > >Device Boot Start End Blocks Id System > > > /dev/hda1 1 523 4200966c W95 FAT32 (LBA) > > > /dev/hda2 524 905 3068415 a5 FreeBSD > > > /*FreeBSD root partition*/ > > > /dev/hda3 * 9061152 1984027+ a5 FreeBSD > > > /*Partition I formated using bsdlabel and mkfs contains ports */ > > > /dev/hda41153243910336536f W95 Ext'd (LBA) > > > /dev/hda511531774 4996183+ 83 Linux > > > /dev/hda624062438 265041 82 Linux swap > > > /dev/hda717752146 2988058+ 7 HPFS/NTFS > > > /dev/hda821472405 2080386b W95 FAT32 > > > > > > Partition table entries are not in disk order > > > > > > When I use GRUB autocomplete feature to check the contents of the > > > FreeBSD partions,It says Error 17: Cannot mount selected partition.(I > > > have done this before when FreeBSD was working fine and I could see the > > > contents of the partion). > > > > > > Perhaps the /boot partion needs to be fsck'ed? And if that is so how can > > > I do it.(I found in the mail archives that fsck'ing UFS2 partitions > > > > Usually you don't have a /boot partition on FreeBSD. I guess you don't > > have > > bootcode in the boot label (ad0s3a). hda3 is in FreeBSD ad0s3. You need > > labels inside partitions (slices). I don't know these linux tools nor am > > I > > familar with Grub but you may want to boot from a fixit disk and post the > > output from bsdlable ad0s3. I guess this doesn't exist, probably > > overwritten by the linux tools. > > > > For more information read boot(8) and boot0cfg(8) to get an idea how > > FreeBSD treats the microsoft adopted partitioning system (which also > > lunix > > uses but is uncommon for UNIX) > > > > -Harry > > > > > using linux is not possible.) > > > > > > Thanks, > > > > > > Koushik Narayanan > > > ___ > > > freebsd-questions@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to > > > "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
Thanks for helping.I couldn't do anything with the fixit disk.Is there some method or tool using which I can copy all files in the ufs partiton to some other partition using DOS,Windows,or Linux(my kernel won't support ufs.) .Something like ltools which allows me to copy,delete files in ext2 partition using windows. If I could do so..then I can format those partitions and re-install FreeBSD.. THanks. Koushik Narayanan On Fri, 6 May 2005 05:49:59 +0200, "Emanuel Strobl" <[EMAIL PROTECTED]> said: > Am Freitag, 6. Mai 2005 03:59 schrieb Koushik Narayanan: > > Hello, > > I have a PC with Windows XP,FreeBSD-5.3 and Linux(Fedora).I use GRUB as > > my boot manager and I boot into FreeBSD using chainloader. > > I have XP and FreeBSD on primary partitions.I had a linux primary > > partion apart from these.I wanted to convert that to UFS2 as my /usr > > partition (FreeBSD) was almost full.I did that using bsdlabel and mkfs. > > After that the fdisk print output in linux showed the recently formated > > partition as type Linux.So I installed linux-fdisk using the ports > > collection and try to change the system-id of that partition,but it did > > not work.I then booted into linux and did the same using fdisk.This time > > it worked.But after that FreeBSD does not boot.(I don't see the rotating > > / and the loader.The system freezes and even numlock does not work )Here > > is the fdisk print output from linux: > > > > Disk /dev/hda: 20.0 GB, 20060135424 bytes > > 255 heads, 63 sectors/track, 2438 cylinders > > Units = cylinders of 16065 * 512 = 8225280 bytes > > > >Device Boot Start End Blocks Id System > > /dev/hda1 1 523 4200966c W95 FAT32 (LBA) > > /dev/hda2 524 905 3068415 a5 FreeBSD > > /*FreeBSD root partition*/ > > /dev/hda3 * 9061152 1984027+ a5 FreeBSD > > /*Partition I formated using bsdlabel and mkfs contains ports */ > > /dev/hda41153243910336536f W95 Ext'd (LBA) > > /dev/hda511531774 4996183+ 83 Linux > > /dev/hda624062438 265041 82 Linux swap > > /dev/hda717752146 2988058+ 7 HPFS/NTFS > > /dev/hda821472405 2080386b W95 FAT32 > > > > Partition table entries are not in disk order > > > > When I use GRUB autocomplete feature to check the contents of the > > FreeBSD partions,It says Error 17: Cannot mount selected partition.(I > > have done this before when FreeBSD was working fine and I could see the > > contents of the partion). > > > > Perhaps the /boot partion needs to be fsck'ed? And if that is so how can > > I do it.(I found in the mail archives that fsck'ing UFS2 partitions > > Usually you don't have a /boot partition on FreeBSD. I guess you don't > have > bootcode in the boot label (ad0s3a). hda3 is in FreeBSD ad0s3. You need > labels inside partitions (slices). I don't know these linux tools nor am > I > familar with Grub but you may want to boot from a fixit disk and post the > output from bsdlable ad0s3. I guess this doesn't exist, probably > overwritten by the linux tools. > > For more information read boot(8) and boot0cfg(8) to get an idea how > FreeBSD treats the microsoft adopted partitioning system (which also > lunix > uses but is uncommon for UNIX) > > -Harry > > > using linux is not possible.) > > > > Thanks, > > > > Koushik Narayanan > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
Am Freitag, 6. Mai 2005 03:59 schrieb Koushik Narayanan: > Hello, > I have a PC with Windows XP,FreeBSD-5.3 and Linux(Fedora).I use GRUB as > my boot manager and I boot into FreeBSD using chainloader. > I have XP and FreeBSD on primary partitions.I had a linux primary > partion apart from these.I wanted to convert that to UFS2 as my /usr > partition (FreeBSD) was almost full.I did that using bsdlabel and mkfs. > After that the fdisk print output in linux showed the recently formated > partition as type Linux.So I installed linux-fdisk using the ports > collection and try to change the system-id of that partition,but it did > not work.I then booted into linux and did the same using fdisk.This time > it worked.But after that FreeBSD does not boot.(I don't see the rotating > / and the loader.The system freezes and even numlock does not work )Here > is the fdisk print output from linux: > > Disk /dev/hda: 20.0 GB, 20060135424 bytes > 255 heads, 63 sectors/track, 2438 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > >Device Boot Start End Blocks Id System > /dev/hda1 1 523 4200966c W95 FAT32 (LBA) > /dev/hda2 524 905 3068415 a5 FreeBSD > /*FreeBSD root partition*/ > /dev/hda3 * 9061152 1984027+ a5 FreeBSD > /*Partition I formated using bsdlabel and mkfs contains ports */ > /dev/hda41153243910336536f W95 Ext'd (LBA) > /dev/hda511531774 4996183+ 83 Linux > /dev/hda624062438 265041 82 Linux swap > /dev/hda717752146 2988058+ 7 HPFS/NTFS > /dev/hda821472405 2080386b W95 FAT32 > > Partition table entries are not in disk order > > When I use GRUB autocomplete feature to check the contents of the > FreeBSD partions,It says Error 17: Cannot mount selected partition.(I > have done this before when FreeBSD was working fine and I could see the > contents of the partion). > > Perhaps the /boot partion needs to be fsck'ed? And if that is so how can > I do it.(I found in the mail archives that fsck'ing UFS2 partitions Usually you don't have a /boot partition on FreeBSD. I guess you don't have bootcode in the boot label (ad0s3a). hda3 is in FreeBSD ad0s3. You need labels inside partitions (slices). I don't know these linux tools nor am I familar with Grub but you may want to boot from a fixit disk and post the output from bsdlable ad0s3. I guess this doesn't exist, probably overwritten by the linux tools. For more information read boot(8) and boot0cfg(8) to get an idea how FreeBSD treats the microsoft adopted partitioning system (which also lunix uses but is uncommon for UNIX) -Harry > using linux is not possible.) > > Thanks, > > Koushik Narayanan > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" pgpvlDQICKgiE.pgp Description: PGP signature
Re: Boot problem with freebsd 5.3
On 03/14/05 16:15:14, cell wrote: hello , i have problem when i boot with freebsd 5.3 since i have had a power cut .The message of the error is : error 16 Iba 191 No /boot/loader FreeBSD/i386 boot Default: 0:ad(0,a)/kernel boot: error 16 Iba 191 No /kernel I don't know if the hard disk is endommaged but i don't think.How do for boot in freebsd ? ___ boot /boot/kernel.old or use a install disc? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem with SATA
> I've problem with booting my PC. The hardward is (something like) > > AMD FX 55 > Two SATA disk with Nvidia NForce 3 for raid > One disk IDE. > > The Two SATA disk is for WinXP > > I want install some real OS in the IDE disk, but the problem is I don't > know how I can choose boot device. When I proceed normaly (like the 100 > times I've to do) I boot on IDE disk (via the BIOS) I've F1..F5 and when I > press F1 everthing work fine I boot my FreeBSD, but when I press F5i > boot my FreeBSD too. > > Anyone have some solution ? > I recommend using the GAG boot loader. It knows about BSDs/Windows. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
Okay I've checked my BIOS. I'm using Phoenix BIOS Setup version 4.0 with the bwlo versions BIOS Version: R216B1 EC BIOS Version: R216B1 Video BIOS Version: BOAM7_12 I can't seem to find the option specified below or something similar. Hidetoshi Shimokawa wrote: It seems that fwohci registers are not mapped correctly. If your BIOS has a option for `PnP OS', try to set it to 'no'. /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 16:32:30 +0100, Kris Davidson wrote: I'm trying to install 5.1 release and am in the process of downloading version 4.8 Hidetoshi Shimokawa wrote: Which version of FreeBSD are you trying to install? /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 15:19:56 +0100, Kris Davidson wrote: This may be a complete newbie question, or it may have been answered before but I would appreciate any help or input that can be provided. I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install FreeBSD on. I boot from the CD and then try selecting each one of the 7 boot options however each option I pick returns the below and then the system reboots, as such I can not start the installation. -- fwohci0: Link S100, max_rec 2 bytes fwohci0: max_rec2 -> 512 fwohci0: bus_OPT 0x0 -> 0xf8008000 fwohci0: fwohci_set_intr: 1 firewire : on fwohci0 fatal trap 12: page fault while in Kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8 :0xc02e5a50 Stack pointer = 0x10 :0xc0b2e8c4 frame pointer = 0x10 :0xc0b2e8c8 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupte enabled, resume, IOPL=0 current process = 0 (swapper) trap number = 12 Panic: Page fault -- I would appreciate it if anyone could help me with this or provide advice. Cheers. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
It seems that fwohci registers are not mapped correctly. If your BIOS has a option for `PnP OS', try to set it to 'no'. /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 16:32:30 +0100, Kris Davidson wrote: > > I'm trying to install 5.1 release and am in the process of downloading > version 4.8 > > Hidetoshi Shimokawa wrote: > > Which version of FreeBSD are you trying to install? > > > > /\ Hidetoshi Shimokawa > > \/ [EMAIL PROTECTED] > > PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html > > > > At Sat, 25 Oct 2003 15:19:56 +0100, > > Kris Davidson wrote: > > > >>This may be a complete newbie question, or it may have been answered > >>before but I would appreciate any help or input that can be provided. > >> > >>I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install > >>FreeBSD on. I boot from the CD and then try selecting each one of the 7 > >>boot options however each option I pick returns the below and then the > >>system reboots, as such I can not start the installation. > >> > >>-- > >>fwohci0: Link S100, max_rec 2 bytes > >>fwohci0: max_rec2 -> 512 > >>fwohci0: bus_OPT 0x0 -> 0xf8008000 > >>fwohci0: fwohci_set_intr: 1 > >> > >>firewire : on fwohci0 > >>fatal trap 12: page fault while in Kernel mode > >> > >>fault virtual address = 0x2c > >>fault code = supervisor read, page not present > >>instruction pointer = 0x8 :0xc02e5a50 > >>Stack pointer = 0x10 :0xc0b2e8c4 > >>frame pointer = 0x10 :0xc0b2e8c8 > >>code segment = base 0x0, limit 0xf, type 0x1b > >> = DPL0, pres 1, def32 1, gran 1 > >>processor eflags = interrupte enabled, resume, IOPL=0 > >>current process = 0 (swapper) > >>trap number = 12 > >> > >>Panic: Page fault > >>-- > >> > >>I would appreciate it if anyone could help me with this or provide advice. > >> > >>Cheers. > >> > >>___ > >>[EMAIL PROTECTED] mailing list > >>http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > >>To unsubscribe, send any mail to "[EMAIL PROTECTED]" > >> > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
I'm trying to install 5.1 release and am in the process of downloading version 4.8 Hidetoshi Shimokawa wrote: Which version of FreeBSD are you trying to install? /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 15:19:56 +0100, Kris Davidson wrote: This may be a complete newbie question, or it may have been answered before but I would appreciate any help or input that can be provided. I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install FreeBSD on. I boot from the CD and then try selecting each one of the 7 boot options however each option I pick returns the below and then the system reboots, as such I can not start the installation. -- fwohci0: Link S100, max_rec 2 bytes fwohci0: max_rec2 -> 512 fwohci0: bus_OPT 0x0 -> 0xf8008000 fwohci0: fwohci_set_intr: 1 firewire : on fwohci0 fatal trap 12: page fault while in Kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8 :0xc02e5a50 Stack pointer = 0x10 :0xc0b2e8c4 frame pointer = 0x10 :0xc0b2e8c8 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupte enabled, resume, IOPL=0 current process = 0 (swapper) trap number = 12 Panic: Page fault -- I would appreciate it if anyone could help me with this or provide advice. Cheers. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-firewire To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
Which version of FreeBSD are you trying to install? /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 15:19:56 +0100, Kris Davidson wrote: > > This may be a complete newbie question, or it may have been answered > before but I would appreciate any help or input that can be provided. > > I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install > FreeBSD on. I boot from the CD and then try selecting each one of the 7 > boot options however each option I pick returns the below and then the > system reboots, as such I can not start the installation. > > -- > fwohci0: Link S100, max_rec 2 bytes > fwohci0: max_rec2 -> 512 > fwohci0: bus_OPT 0x0 -> 0xf8008000 > fwohci0: fwohci_set_intr: 1 > > firewire : on fwohci0 > fatal trap 12: page fault while in Kernel mode > > fault virtual address = 0x2c > fault code = supervisor read, page not present > instruction pointer = 0x8 :0xc02e5a50 > Stack pointer = 0x10 :0xc0b2e8c4 > frame pointer = 0x10 :0xc0b2e8c8 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL0, pres 1, def32 1, gran 1 > processor eflags = interrupte enabled, resume, IOPL=0 > current process = 0 (swapper) > trap number = 12 > > Panic: Page fault > -- > > I would appreciate it if anyone could help me with this or provide advice. > > Cheers. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
At 10:52 AM -0700 5/30/03, Kent Stewart wrote: My definition of speed is a concept based on how long it takes for the prompt to return after I press the enter key. A fast HD helps. ... The 300 MHz PII I've been running has been totally satisfactory, in terms of speed, except that I have a Perl/Tk app that is quite demanding. My entire motivation for upgrading is to get this app to run faster. The current setup (PIO) is still faster than the old machine, but I suspect strongly that getting DMA online would be a win... -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com/rdm- my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
On Friday 30 May 2003 10:25 am, Rich Morin wrote:
> At 10:04 AM -0700 5/30/03, Kent Stewart wrote:
> >No, you didn't understand. The ATA cards appear like a scsi to the bios.
> >To boot from an add in ATA card, you have to choose scsi boot.
>
> I'll look into this. However, I haven't seen any way to request this
> in the SETUP screens. Anything I should look for?
No, idea. The older machines could all boot from scsi but my in memory boot
experience is only with P-II or IIIs and AMD Athlon's or better. These
systems have scsi as a defined boot parameter.
I had something like a KT7A that was part of the flawed Southbridge set and I
had it using an ATA addin card. The mobo eventually died. My systems
typically have one HD per controller. They have 2 hooked up to the mobo and 2
to an addin. My buildworld speeds vary as much as 50% or more depending on
the setup.
>
> >You lose a lot of speed. My new ATA cards are all UDMA-133. Dma transfers
> > are always faster. PIO is set at something like 16MB/s. You only get so
> > many milliseconds of time for a each transfer block and dma is always
> > faster.
>
> So, it's definitely worth pursuing.
>
My definition of speed is a concept based on how long it takes for the prompt
to return after I press the enter key. A fast HD helps. This would be
especially true if you were following something other than a release because
a buildworld can take place much faster. Installing from a UDMA rated CD-ROM
is also much faster but that is also another parameter that you have to add
to /boot/loader.conf.. BNW, the parameter name is the same as the depricated
sysctl variables but the value has to be quoted (").
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: Boot problem: "ata0: resetting devices"
At 10:04 AM -0700 5/30/03, Kent Stewart wrote: No, you didn't understand. The ATA cards appear like a scsi to the bios. To boot from an add in ATA card, you have to choose scsi boot. I'll look into this. However, I haven't seen any way to request this in the SETUP screens. Anything I should look for? You lose a lot of speed. My new ATA cards are all UDMA-133. Dma transfers are always faster. PIO is set at something like 16MB/s. You only get so many milliseconds of time for a each transfer block and dma is always faster. So, it's definitely worth pursuing. -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com/rdm- my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
On Friday 30 May 2003 09:50 am, Rich Morin wrote: > At 7:29 AM -0700 5/30/03, Kent Stewart wrote: > >I use the Promise TX2 and Maxtor pci cards in several systems. I > >just dropped them in and they worked. You would have to boot scsi. > > > > So, you're saying that I can't boot from an ATA drive on a PCI-based > controller card? What is the background for this limitation? No, you didn't understand. The ATA cards appear like a scsi to the bios. To boot from an add in ATA card, you have to choose scsi boot. > > Also, I'm curious about the effects of turning off hw.ata.ata_dma; > outside of using some CPU time, what are the likely effects of this. > For instance, is this likely to slow down disk transfers, assuming > that the system is mostly idle? You lose a lot of speed. My new ATA cards are all UDMA-133. Dma transfers are always faster. PIO is set at something like 16MB/s. You only get so many milliseconds of time for a each transfer block and dma is always faster. 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: Boot problem: "ata0: resetting devices"
At 7:29 AM -0700 5/30/03, Kent Stewart wrote: I use the Promise TX2 and Maxtor pci cards in several systems. I just dropped them in and they worked. You would have to boot scsi. So, you're saying that I can't boot from an ATA drive on a PCI-based controller card? What is the background for this limitation? Also, I'm curious about the effects of turning off hw.ata.ata_dma; outside of using some CPU time, what are the likely effects of this. For instance, is this likely to slow down disk transfers, assuming that the system is mostly idle? -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com/rdm- my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
On Friday 30 May 2003 02:45 am, Rich Morin wrote: > At 2:05 AM -0700 5/30/03, Kent Stewart wrote: > >Did you try doing it in /boot/loader.conf. > > The man page indicates that I can set assorted variables in this file, > so perhaps I could put in a line such as: > >hw.ata.ata_dma=0 > > If so, the sysctl.conf(5) man page should be amended to indicate the > fact. Nonetheless, as I already have a kernel which has the variable > turned off, this wouldn't buy me anything. > > What I'm really looking for is a way to use a different ATA controller. I use the Promise TX2 and Maxtor pci cards in several systems. I just dropped them in and they worked. You would have to boot scsi. 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: Boot problem: "ata0: resetting devices"
At 2:05 AM -0700 5/30/03, Kent Stewart wrote: Did you try doing it in /boot/loader.conf. The man page indicates that I can set assorted variables in this file, so perhaps I could put in a line such as: hw.ata.ata_dma=0 If so, the sysctl.conf(5) man page should be amended to indicate the fact. Nonetheless, as I already have a kernel which has the variable turned off, this wouldn't buy me anything. What I'm really looking for is a way to use a different ATA controller. -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com/rdm- my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
On Friday 30 May 2003 01:54 am, Rich Morin wrote: > At 9:40 PM -0400 5/29/03, Jud wrote: > >This was a common problem along about 4.5-4.6. Upgrade to at least > >4.7, see if it helps; the cause of the common problem was fixed in > >4.7- prerelease. > > I've been running "FreeBSD 4.7-RELEASE" on my production system, so I > tried moving the disks over and booting. Same problem. > > One message I found on eht web indicated that I might be able to get > past the problem by disabling UltraDMA. Unfortunately: > >* There isn't any obvious way to do this in the AMIBIOS. > >* Setting hw.ata.ata_dma to 0 in /etc/sysctl.conf won't help, > because (from sysctl.conf(5)): > > The /etc/sysctl.conf file is read in when the system goes > into multi-user mode ... > > and the problem asserts itself while the system is still in > single-user mode. > > So, I decided to change line 90 of /usr/src/sys/dev/ataata-disk.c to: > > static int ata_dma = 0; > > This allowed the system to boot without (apparent) error, but I'd > still like to boot off a PCI-based ATA card, instead. > Did you try doing it in /boot/loader.conf. 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: Boot problem: "ata0: resetting devices"
At 9:40 PM -0400 5/29/03, Jud wrote: This was a common problem along about 4.5-4.6. Upgrade to at least 4.7, see if it helps; the cause of the common problem was fixed in 4.7- prerelease. I've been running "FreeBSD 4.7-RELEASE" on my production system, so I tried moving the disks over and booting. Same problem. One message I found on eht web indicated that I might be able to get past the problem by disabling UltraDMA. Unfortunately: * There isn't any obvious way to do this in the AMIBIOS. * Setting hw.ata.ata_dma to 0 in /etc/sysctl.conf won't help, because (from sysctl.conf(5)): The /etc/sysctl.conf file is read in when the system goes into multi-user mode ... and the problem asserts itself while the system is still in single-user mode. So, I decided to change line 90 of /usr/src/sys/dev/ataata-disk.c to: static int ata_dma = 0; This allowed the system to boot without (apparent) error, but I'd still like to boot off a PCI-based ATA card, instead. -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com/rdm- my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
On Thu, 29 May 2003 01:35:37 -0700, Rich Morin <[EMAIL PROTECTED]> wrote: Here's a bit more information on the configuration: OS: FreeBSD 4.5 Disk: Seagate Barracuda ATA II (ST320420A; 20 GB) Chips: 478 pin Celeron; 2.1 GHz 512 MB DDR DIMM (2 ea.) SiS645DX Northbridge _or_ SiS962(L) Southbridge The manual indicates that the motherboard could have either a Northbridge or Southbridge chipset, but I don't know an easy way to tell which one this board has. Suggestions? This was a common problem along about 4.5-4.6. Upgrade to at least 4.7, see if it helps; the cause of the common problem was fixed in 4.7- prerelease. Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
I have tried a couple of PCI-based IDE cards. I see messages that
indicate that the motherboard is seeing the card and that the card
is seeing the disk. Unfortunately, the system is not willing to
boot off the disk (sigh). I have tried changing several settings,
including:
* Setting {Pri,Sec}{Master,Slave} to "Not Installed"
* Setting the {1st,2nd,3rd} Boot Device to IDE-[123]
* Turning off "Plug and PLay Aware O/S"
* Turning off Onboard PCI IDE
No luck. Suggestions, anyone?
-r
--
email: [EMAIL PROTECTED]; phone: +1 650-873-7841
http://www.cfcl.com/rdm- my home page, resume, etc.
http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc.
http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series
http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
Here's a bit more information on the configuration: OS: FreeBSD 4.5 Disk: Seagate Barracuda ATA II (ST320420A; 20 GB) Chips: 478 pin Celeron; 2.1 GHz 512 MB DDR DIMM (2 ea.) SiS645DX Northbridge _or_ SiS962(L) Southbridge The manual indicates that the motherboard could have either a Northbridge or Southbridge chipset, but I don't know an easy way to tell which one this board has. Suggestions? Anyway, assuming that it's the latter, here's a note that seems relevant, if not real encouraging: http://www.geocrawler.com/archives/3/160/2002/11/0/10219234/ "the controller is technically unsupported" The note does NOT say whether I can simply plug in a PCI-based controller card (which seems like the obvious workaround). Is this likely to work? -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com/rdm- my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot problem: "ata0: resetting devices"
Le Jeudi 29 Mai 2003 07:05, Rich Morin a écrit : > I recently purchased a new motherboard (ECS EliteGroup Mainboard P4S5A/DX+; > AMI BIOS) and a matching CPU (Celeron, 478 pin, 2.1 GHz) from outpost.com. > I stuffed these into an old chassis, adding a 500 W power supply and a pair > of 512 MB DDR DIMMs. > > After walking through the configuration (accepting "Optimal Settings" for > everything), I tried booting up the machine on an IDE drive that was loaded > with FreeBSD and had been used most recently with a 200 MHz Pentium II. > > The boot sequence proceeded without problems for quite a while, checking > devices, etc. Then, however, it halted with a pair of nastygrams: > >ad0: READ command timeout tag=0 serv=0 resetting >ata0: resetting devices > > I tried putting the ATA drive and the CDROM on separate cables, but that > didn't seem to help. My suspicion is that the drive is too slow for the > ATA controller, but I don't see any way to compensate for this. Help? Hello, Deactivate the DMA mode in the BIOS, and it it should boot. Which version of FreeBSD do you use ? What is the chipset used by the motherboard ? If you're on 4.8, with a SiS 651, here is a possible fix to use the DMA modes : http://minilien.com/?BNI4EdKfXa " >Fix: Here is the patch to /sys/dev/ata/ata-dma.c *** ata-dma.c.orig Wed Oct 2 23:13:38 2002 --- ata-dma.c Tue Feb 25 10:20:08 2003 *** *** 504,509 --- 504,510 ata_find_dev(parent, 0x06401039, 0) || /* SiS 640 */ ata_find_dev(parent, 0x06451039, 0) || /* SiS 645 */ ata_find_dev(parent, 0x06501039, 0) || /* SiS 650 */ + ata_find_dev(parent, 0x06511039, 0) || /* SiS 651 */ ata_find_dev(parent, 0x07301039, 0) || /* SiS 730 */ ata_find_dev(parent, 0x07331039, 0) || /* SiS 733 */ ata_find_dev(parent, 0x07351039, 0) || /* SiS 735 */ It worked fine for this 3 monthes on my machine. I'm afraid the same problem may occur on SiS 648, 655, 746 and 755-based machines... " Florent ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
