Re: root mount error
Hi! I had thу same problem after upgrading 7.3 to 8.1. And not me only... Solution is here: http://www.b.biz/blog/freebsd/root-mount-error-after-upgrade-to-freebsd-8.b works on 100%!!! details on this bug here: http://lists.freebsd.org/pipermail/freebsd-current/2009-January/001892.html Good luck! -- View this message in context: http://freebsd.1045724.n5.nabble.com/root-mount-error-tp3939891p4652032.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: root mount error
ce 26.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0: on uhci0 ehci0: mem 0xe4621000-0xe46213ff irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci0 pci0: at device 27.0 (no driver attached) pcib1: irq 16 at device 28.0 on pci0 pci8: on pcib1 pcib2: irq 17 at device 28.1 on pci0 pci16: on pcib2 siba_bwn0: mem 0xe400-0xe4003fff irq 17 at device 0.0 on pci16 siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] pcib3: irq 16 at device 28.4 on pci0 pci40: on pcib3 uhci1: port 0x4060-0x407f irq 20 at device 29.0 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x2f00 usbus2: on uhci1 uhci2: port 0x4080-0x409f irq 21 at device 29.1 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x2f00 usbus3: on uhci2 uhci3: port 0x40a0-0x40bf irq 18 at device 29.2 on pci0 uhci3: [ITHREAD] uhci3: LegSup = 0x2f00 usbus4: on uhci3 ehci1: mem 0xe4628000-0xe46283ff irq 20 at device 29.7 on pci0 ehci1: [ITHREAD] usbus5: EHCI version 1.0 usbus5: on ehci1 pcib4: at device 30.0 on pci0 pci2: on pcib4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x40c0-0x40cf irq 17 at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] battery0: on acpi0 acpi_acad0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_tz2: on acpi0 acpi_tz3: on acpi0 acpi_tz3: _CRT value is absurd, ignored (256.0C) acpi_tz4: on acpi0 atrtc0: port 0x70-0x71,0x72-0x73 irq 8 on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ppc0: cannot reserve I/O port range est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 acd0: DVDR at ata0-master PIO4 SMP: AP CPU #1 Launched! Root mount waiting for: usbus5 usbus4 usbus3 usbus2 usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered Root mount waiting for: usbus5 usbus1 uhub1: 4 ports with 4 removable, self powered uhub5: 6 ports with 6 removable, self powered Root mount waiting for: usbus5 Trying to mount root from ufs:/dev/ad4s3a ROOT MOUNT ERROR ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: root mount error
On 2010-Dec-28 23:08:44 +0300, Michael BlackHeart wrote: >I'm jsut trying to say than recent changes in kernel or kernel-modules >broke up my HDD support and I'd like to notice developres to check >where the problem is. It doesn't work that way. The developers don't have a problem or it would have been fixed. You are going to need to provide more details and do some investigations yourself to help identify the problem. >Loader on it's own stage easily detects HDD and root partition so I >can just select old kernel and boot up, but I'm not shure how he gain >access to HDD to mfke any conclusion, probably through BIOS interrupts >but it's out of piont. Yes. Until the kernel starts, all I/O is via BIOS. >And for my pity I don't know how to dump demsg without having any >serial connection or usable disk drive, maybe to flash drive, but I >don't know how. And anyway there's no real kernel painc, it just asks >for root mountpoint. Best suggestion I can offer is to take photographs of the boot messages (you can use scroll-lock to let you scroll back) and post them somewhere. >If you need any aditional info I'll give it all, just ask. What is the SVN revision of a kernel that works? What is the SVN revision of a kernel that fails? Can you please post a verbose dmesg of a successful boot. Can you please post a dmesg of an unsuccessful boot (see above). -- Peter Jeremy pgpHUhVzb3Hvu.pgp Description: PGP signature
Re: root mount error
> Date: Tue, 28 Dec 2010 22:09:15 +0100 > From: Greg Byshenk > Sender: owner-freebsd-sta...@freebsd.org > > On Tue, Dec 28, 2010 at 11:08:44PM +0300, Michael BlackHeart wrote: > > I'm no looking for help neither instructions how to build kernel. I'm > > just installing 8.1 RELEASE and svn it up to last week 8-stable. And > > going step-by-step of handbook installing kernel I'm having a trouble > > - it seems than new kenel doesn't recognize my HDD. I'm not doing > > something special, in that case I'm for shure mentioned it. I'm just > > building GENERIC kernel without any configuration of system after > > installation, to tweaks, no tunes, nothing. It's a new GENERIC kernel > > and it can't find my HDD but 8.1 i386/amd64 releases works well and as > > I remember something about month ago stable too. > > >Now, a likely cause of your problem is the installation of a custom > > >kernel with removed support for whatever your hard disk drive or raid > > >controller is recognized as. > > When it works it's just and ad0 hdd, no raid or special driver > > I'm jsut trying to say than recent changes in kernel or kernel-modules > > broke up my HDD support and I'd like to notice developres to check > > where the problem is. > > And of couse I've tried to switch SATA native mode and it doesn't > > change anything. > > Loader on it's own stage easily detects HDD and root partition so I > > can just select old kernel and boot up, but I'm not shure how he gain > > access to HDD to mfke any conclusion, probably through BIOS interrupts > > but it's out of piont. > > And for my pity I don't know how to dump demsg without having any > > serial connection or usable disk drive, maybe to flash drive, but I > > don't know how. And anyway there's no real kernel painc, it just asks > > for root mountpoint. > > > > And for shure I've got an 2.5" Hitachi HTS542516K9A300 160Gb SATA HDD > > > > If you need any aditional info I'll give it all, just ask. > > If you change to SATA native mode, then your HD may show up at a > different device (mine moved to ad8). If you go to native mode and > issue a '?' when it fails to find the kernel, does it show any HD > devices? I would strongly urge that you start using labels instead of device names for your disks. Labels don't change unless you explicitly change them while drive names do. Labels may be used in the fstab. E.G.: # DeviceMountpoint FStype Options DumpPass# /dev/ufs/root / ufs rw 1 1 /dev/ufs/tmp/tmpufs rw 2 2 /dev/ufs/var/usrufs rw 2 2 /dev/ufs/var/varufs rw 2 2 See 19.6 "Labeling Disk Devices" in the handbook for more information. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: root mount error
On Tue, Dec 28, 2010 at 11:08:44PM +0300, Michael BlackHeart wrote: > I'm no looking for help neither instructions how to build kernel. I'm > just installing 8.1 RELEASE and svn it up to last week 8-stable. And > going step-by-step of handbook installing kernel I'm having a trouble > - it seems than new kenel doesn't recognize my HDD. I'm not doing > something special, in that case I'm for shure mentioned it. I'm just > building GENERIC kernel without any configuration of system after > installation, to tweaks, no tunes, nothing. It's a new GENERIC kernel > and it can't find my HDD but 8.1 i386/amd64 releases works well and as > I remember something about month ago stable too. > >Now, a likely cause of your problem is the installation of a custom > >kernel with removed support for whatever your hard disk drive or raid > >controller is recognized as. > When it works it's just and ad0 hdd, no raid or special driver > I'm jsut trying to say than recent changes in kernel or kernel-modules > broke up my HDD support and I'd like to notice developres to check > where the problem is. > And of couse I've tried to switch SATA native mode and it doesn't > change anything. > Loader on it's own stage easily detects HDD and root partition so I > can just select old kernel and boot up, but I'm not shure how he gain > access to HDD to mfke any conclusion, probably through BIOS interrupts > but it's out of piont. > And for my pity I don't know how to dump demsg without having any > serial connection or usable disk drive, maybe to flash drive, but I > don't know how. And anyway there's no real kernel painc, it just asks > for root mountpoint. > > And for shure I've got an 2.5" Hitachi HTS542516K9A300 160Gb SATA HDD > > If you need any aditional info I'll give it all, just ask. If you change to SATA native mode, then your HD may show up at a different device (mine moved to ad8). If you go to native mode and issue a '?' when it fails to find the kernel, does it show any HD devices? -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: root mount error
I'm no looking for help neither instructions how to build kernel. I'm just installing 8.1 RELEASE and svn it up to last week 8-stable. And going step-by-step of handbook installing kernel I'm having a trouble - it seems than new kenel doesn't recognize my HDD. I'm not doing something special, in that case I'm for shure mentioned it. I'm just building GENERIC kernel without any configuration of system after installation, to tweaks, no tunes, nothing. It's a new GENERIC kernel and it can't find my HDD but 8.1 i386/amd64 releases works well and as I remember something about month ago stable too. >Now, a likely cause of your problem is the installation of a custom >kernel with removed support for whatever your hard disk drive or raid >controller is recognized as. When it works it's just and ad0 hdd, no raid or special driver I'm jsut trying to say than recent changes in kernel or kernel-modules broke up my HDD support and I'd like to notice developres to check where the problem is. And of couse I've tried to switch SATA native mode and it doesn't change anything. Loader on it's own stage easily detects HDD and root partition so I can just select old kernel and boot up, but I'm not shure how he gain access to HDD to mfke any conclusion, probably through BIOS interrupts but it's out of piont. And for my pity I don't know how to dump demsg without having any serial connection or usable disk drive, maybe to flash drive, but I don't know how. And anyway there's no real kernel painc, it just asks for root mountpoint. And for shure I've got an 2.5" Hitachi HTS542516K9A300 160Gb SATA HDD If you need any aditional info I'll give it all, just ask. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: root mount error
On Tue, Dec 28, 2010 at 01:36:01AM +0100, Damien Fleuriot wrote: > On 12/27/10 9:18 PM, Michael BlackHeart wrote: > > I've got trouble with FreeBSD 8 Stable > > First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to > > yesterday revision I don't remember exact number, but I've have this > > problem aobut week or two so it's not so important, also as it doesn't > > work on i386 too. > > > > After installing new kernel I've just build - indeed it always was > > GENERIC for both arch's on clean system - I've got an a kernel painc > > caused by disability to mount root partition because kernel couldn't > > see the drive. By pressing '?' I've sen only acd0 that represents > > CD-ROM. > > > > In debug messages I haven't found anything about ad0 - than hdd was > > identified before new kernel was installed. > > I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is > > working with diabled SATA native mode. > > > > I've not found any info 'bout this error in recent 8.Stable so I don't > > know how to handle this one. > First, I'd advise making use of FreeBSD's nextboot utility to test new > kernels: > http://fuse4bsd.creo.hu/localcgi/man-cgi.cgi?nextboot+8 > > Second, I would suggest reading the handbook's excellent section on > upgrading your machine or rebuilding the kernel: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html > > Now, a likely cause of your problem is the installation of a custom > kernel with removed support for whatever your hard disk drive or raid > controller is recognized as. > > Did you reinstall your old, working kernel, or are you actually asking > for help doing just that ? What kind of laptop? For information, I had a similar problem when I updated my laptop (HP Compaq 6910p) to 8.2-PRERELEASE as of 14 December. For some reason, the system was no longer seeing the main hard drive. I solved the problem by setting 'SATA Native Mode' (or some such) in the BIOS, which then led my (SATA) drive to be seen at '/dev/ad8'. After booting from ad8 and modifying my 'fstab', everything works fine. So you might try the same thing. At least change the setting in your BIOS to see if you can see a drive. -greg -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: root mount error
Hey michael, First, I'd advise making use of FreeBSD's nextboot utility to test new kernels: http://fuse4bsd.creo.hu/localcgi/man-cgi.cgi?nextboot+8 Second, I would suggest reading the handbook's excellent section on upgrading your machine or rebuilding the kernel: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html Now, a likely cause of your problem is the installation of a custom kernel with removed support for whatever your hard disk drive or raid controller is recognized as. Did you reinstall your old, working kernel, or are you actually asking for help doing just that ? On 12/27/10 9:18 PM, Michael BlackHeart wrote: > Hello > > I've got trouble with FreeBSD 8 Stable > First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to > yesterday revision I don't remember exact number, but I've have this > problem aobut week or two so it's not so important, also as it doesn't > work on i386 too. > > After installing new kernel I've just build - indeed it always was > GENERIC for both arch's on clean system - I've got an a kernel painc > caused by disability to mount root partition because kernel couldn't > see the drive. By pressing '?' I've sen only acd0 that represents > CD-ROM. > > In debug messages I haven't found anything about ad0 - than hdd was > identified before new kernel was installed. > I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is > working with diabled SATA native mode. > > I've not found any info 'bout this error in recent 8.Stable so I don't > know how to handle this one. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
root mount error
Hello I've got trouble with FreeBSD 8 Stable First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to yesterday revision I don't remember exact number, but I've have this problem aobut week or two so it's not so important, also as it doesn't work on i386 too. After installing new kernel I've just build - indeed it always was GENERIC for both arch's on clean system - I've got an a kernel painc caused by disability to mount root partition because kernel couldn't see the drive. By pressing '?' I've sen only acd0 that represents CD-ROM. In debug messages I haven't found anything about ad0 - than hdd was identified before new kernel was installed. I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is working with diabled SATA native mode. I've not found any info 'bout this error in recent 8.Stable so I don't know how to handle this one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ROOT MOUNT ERROR when booting from zfs
On 19.08.2010, at 19:50, Andriy Gapon wrote: > on 19/08/2010 20:46 Heinrich Rebehn said the following: >> Now i have another problem: >> >> The root fs on on a 4-disk zfs mirror. I am testing under VMware fusion using >> virtual scsi disks. In order to test redundancy, i removed the first disk and >> booting failed. The loader reports: >> >> error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 >> error >> 1 lba 1 error 1 lba 32 error 1 lba 1 No ZFS pools located, can't boot >> >> If i remove any other of the 3 disks instead, booting works fine. Is the >> pool's >> configuration only stored on the first disk? Do i have to replicate it to the >> other disks by hand? > > Fix for this has been recently MFC-ed to stable/8. > > -- > Andriy Gapon Great! Thanks to all FreeBSD developers! --Heinrich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ROOT MOUNT ERROR when booting from zfs
on 19/08/2010 20:46 Heinrich Rebehn said the following: > Now i have another problem: > > The root fs on on a 4-disk zfs mirror. I am testing under VMware fusion using > virtual scsi disks. In order to test redundancy, i removed the first disk and > booting failed. The loader reports: > > error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error > 1 lba 1 error 1 lba 32 error 1 lba 1 No ZFS pools located, can't boot > > If i remove any other of the 3 disks instead, booting works fine. Is the > pool's > configuration only stored on the first disk? Do i have to replicate it to the > other disks by hand? Fix for this has been recently MFC-ed to stable/8. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ROOT MOUNT ERROR when booting from zfs
On 19.08.2010, at 17:24, Torfinn Ingolfsen wrote: > On Thu, 19 Aug 2010 14:33:11 +0200 > Heinrich Rebehn wrote: > >> Hi all, >> >> i am getting the error message in $subject when trying to boot from zfs. >> I followed the instructions found in: >> >> http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror >> >> Before posting all config details and asking what i might have done wrong: >> Is there any possibility to get a more detailed error message than just ROOT >> MOUNT ERROR? e.g. zpool not found | zpool could not be imported | illegal >> mount options | etc > > You have tried verbose boot? > If not, try it and see if you get more information. > -- > Regards, > Torfinn Ingolfsen Yes, i have tried. I did get a flurry of information, but nothing related to the kernel not being able to mount the root fs. In the meanwhile, i have redone the installation and for some reason it is working now. Probably the pool cache was missing.. :-) Now i have another problem: The root fs on on a 4-disk zfs mirror. I am testing under VMware fusion using virtual scsi disks. In order to test redundancy, i removed the first disk and booting failed. The loader reports: error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 error 1 lba 32 error 1 lba 1 No ZFS pools located, can't boot If i remove any other of the 3 disks instead, booting works fine. Is the pool's configuration only stored on the first disk? Do i have to replicate it to the other disks by hand? -Heinrich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ROOT MOUNT ERROR when booting from zfs
On Thu, 19 Aug 2010 14:33:11 +0200 Heinrich Rebehn wrote: > Hi all, > > i am getting the error message in $subject when trying to boot from zfs. > I followed the instructions found in: > > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror > > Before posting all config details and asking what i might have done wrong: Is > there any possibility to get a more detailed error message than just ROOT > MOUNT ERROR? e.g. zpool not found | zpool could not be imported | illegal > mount options | etc You have tried verbose boot? If not, try it and see if you get more information. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ROOT MOUNT ERROR when booting from zfs
Hi all, i am getting the error message in $subject when trying to boot from zfs. I followed the instructions found in: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror Before posting all config details and asking what i might have done wrong: Is there any possibility to get a more detailed error message than just ROOT MOUNT ERROR? e.g. zpool not found | zpool could not be imported | illegal mount options | etc The kernel reports that it is trying to mount from zfs:zroot, which is correct. The zfs kernel module is being loaded. -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-62394 Fax :-3341 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI and ZFS: root mount error
Quoting Wes Morgan (from Sun, 17 Jan 2010 09:04:16 -0600 (CST)): On Sat, 16 Jan 2010, Volodymyr Kostyrko wrote: On Sat, 16 Jan 2010 00:29:23 +0100 Oliver Brandmueller wrote: > Check with "zpool status" if your zpool refers to diskslices like > "ad0s1". I use gpt have setup the ZFS mirror to refer to gptids: > > pool: silver > state: ONLINE > scrub: none requested > config: > > NAMESTATE READ WRITE CKSUM > silver ONLINE 0 0 0 > mirrorONLINE 0 0 0 > gptid/9e68d234-f306-11de-a0c4-0002b3b6e838 ONLINE 0 0 0 > gptid/a025b88c-f306-11de-a0c4-0002b3b6e838 ONLINE 0 0 0 > > With that kind of configuration I can switch back and forth between > using ATA_CAM or using traditional ATA drivers. Since you're not using > GPT I gues you can use geom labels to do more or less the same thing. > > In short: use labels, nut device names. Saves headaches in many cases. ZFS actually can find disks without any glabel help. I have one server which I have moved recently to ahci and nothing changes for me. ZFS silently accepted new provider names and continue working as usual. Agreed, I experienced the same thing here when I moved to AHCI. I think pjd committed some changes in the last few months that greatly improved the ability of zfs to find devices by uuid. Using glabel or gptid's with zfs is highly overrated IMO! Jumping into the discussion without much knowledge about the initial start... If this is with 8-stable: the stuff is merged and should work. If this is with 7-stable: the stuff is merged (by me) since 1-2 weeks. If this is something else, have a look if the code as displayed at http://svn.freebsd.org/viewvc/base?view=revision&revision=200158 is there (after this commit there is nothing else which affects the ability to find devices). What may work too is to export the zpool before switching and importing it again after switching the storage subsystem. Bye, Alexander. -- Do you mean that you not only want a wrong answer, but a certain wrong answer? -- Tobaben http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI and ZFS: root mount error
On Sat, 16 Jan 2010, Volodymyr Kostyrko wrote: > On Sat, 16 Jan 2010 00:29:23 +0100 > Oliver Brandmueller wrote: > > > Check with "zpool status" if your zpool refers to diskslices like > > "ad0s1". I use gpt have setup the ZFS mirror to refer to gptids: > > > > pool: silver > > state: ONLINE > > scrub: none requested > > config: > > > > NAMESTATE READ > > WRITE CKSUM > > silver ONLINE 0 > > 0 0 > > mirrorONLINE 0 > > 0 0 > > gptid/9e68d234-f306-11de-a0c4-0002b3b6e838 ONLINE 0 > > 0 0 > > gptid/a025b88c-f306-11de-a0c4-0002b3b6e838 ONLINE 0 > > 0 0 > > > > With that kind of configuration I can switch back and forth between > > using ATA_CAM or using traditional ATA drivers. Since you're not using > > GPT I gues you can use geom labels to do more or less the same thing. > > > > In short: use labels, nut device names. Saves headaches in many cases. > > ZFS actually can find disks without any glabel help. I have one server > which I have moved recently to ahci and nothing changes for me. ZFS > silently accepted new provider names and continue working as usual. > Agreed, I experienced the same thing here when I moved to AHCI. I think pjd committed some changes in the last few months that greatly improved the ability of zfs to find devices by uuid. Using glabel or gptid's with zfs is highly overrated IMO! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI and ZFS: root mount error
On Fri, Jan 15, 2010 at 3:55 PM, Volodymyr Kostyrko wrote: > On Fri, 15 Jan 2010 21:13:39 +0100 > Romain Garbage wrote: > >> After setting ahci_load="YES" in /boot/loader.conf, I get a root mount error. >> ahci seems to attach to disk correctly (I get ada0 messages with no error) >> >> Without ahci_load="YES", system boots fine, with ata module attaching to >> disk. >> >> I have a full zfs system, set up following wiki instructions: >> http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition >> (MBR scheme, ZFS in a FreeBSD slice, together with a swap partition) >> >> I'm using a GENERIC kernel, RELENG_8 branch. > > I have faced some problems that looks exactly like you say. I haven't > investigated thoroughly after some quick-hack-repairs machine runs flawlessly. > > 1. I have moved to RELENG_8 from RELENG_8_0. I don't think this is it but > zfsloader support was what I was looking for. > > 2. I reinitialised zfs partitions again with a boot code. But this time I > used bs=512 dd option. > > 3. I recreated zpool.cache and replaced it on my pool. I believe the step 3 has fixed your issue. I believe that the zfs loader on -HEAD is less prone to this type of problems, but I am not entirely sure if it would be helpful for all-disk-name-changed case, though. So, in conclusion, in order to fix the problem, one need: Boot into an environment where you can mount ZFS partition. With a LiveFS boot, one can do this: 0) during boot, load zfs, tmpfs 1) mount a tmpfs on /boot/zfs 2) zpool import -f -R /mnt yourpool 3) set hostid to the one in your zpool, perhaps chroot into the zpool and do hostid start 4) export and re-import zpool 5) overwrite /pool/boot/zfs with /boot/zfs 6) make sure the zfs has been written down to disk 7) reboot (Steps 3-4 may be skipped in theory but I personally recommend one to do that). Cheers, -- Xin LI http://www.delphij.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI and ZFS: root mount error
2010/1/16, Jeremy Chadwick : > > Can you post your entire kernel configuration file? Thanks. Here it its: I just copied the GENERIC conf file, commented out device ataraid and device atadisk, added option ATA_CAM (I forgot to mention all that stuff it in last post), and added device ahci. # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.531.2.7 2010/01/12 06:00:56 brooks Exp $ cpu HAMMER ident ATACAMKERNEL # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. # Use the following to compile in values accessible to the kernel # through getenv() (or kenv(1) in userland). The format of the file # is 'variable=value', see kenv(1) # # env "GENERIC.env" makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD# Network Lock Manager options NFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat (sgtty) options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128# Prevent printf output being interspersed. options KBD_INSTALL_CDEV# install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache #optionsKDTRACE_FRAME # Ensure frames are compiled in #optionsKDTRACE_HOOKS # Kernel DTrace hooks options ATA_CAM # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices device ata #device atadisk # ATA disk drives #device atar
Re: AHCI and ZFS: root mount error
On Sat, Jan 16, 2010 at 01:48:12AM +0100, Romain Garbage wrote: > 2010/1/16, Volodymyr Kostyrko : > > On Fri, 15 Jan 2010 21:13:39 +0100 > > Romain Garbage wrote: > > > >> After setting ahci_load="YES" in /boot/loader.conf, I get a root mount > >> error. > >> ahci seems to attach to disk correctly (I get ada0 messages with no error) > >> > >> Without ahci_load="YES", system boots fine, with ata module attaching to > >> disk. > >> > >> I have a full zfs system, set up following wiki instructions: > >> http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition > >> (MBR scheme, ZFS in a FreeBSD slice, together with a swap partition) > >> > >> I'm using a GENERIC kernel, RELENG_8 branch. > > > > I have faced some problems that looks exactly like you say. I haven't > > investigated thoroughly after some quick-hack-repairs machine runs > > flawlessly. > > > > 1. I have moved to RELENG_8 from RELENG_8_0. I don't think this is it but > > zfsloader support was what I was looking for. > > > > 2. I reinitialised zfs partitions again with a boot code. But this time I > > used bs=512 dd option. > > > > 3. I recreated zpool.cache and replaced it on my pool. > > > > Actually I don't know which one helped me, but my bet is for the third step > > and maybe for second. > > A weird thing: > > I just built and installed a new kernel (RELENG_8, source csuped a few > hours ago), just adding "device ahci" to the config file. I get the > same error, with driver attaching correctly. > > Now, adding ahci_load="NO" to /boot/loader.conf and booting the new > custom kernel, it just boots fine, ahci attaching to the device, and > zfs root gets mounted. > > dmesg | grep ada > > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ATA-8 SATA 2.x device > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes)cd0 > at ahcich1 bus 0 scbus1 target 0 lun 0 > ada0: Command Queueing enabled > ada0: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C) > ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 > ada1: ATA-8 SATA 2.x device > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes) > ada1: Command Queueing enabled > ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ATA-8 SATA 2.x device > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes)cd0 > at ahcich1 bus 0 scbus1 target 0 lun 0 > ada0: Command Queueing enabled > ada0: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C) > ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 > ada1: ATA-8 SATA 2.x device > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes) > ada1: Command Queueing enabled > ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) > > I didn't do anything else, just the line in loader.conf, and the > system just works fine. Can you post your entire kernel configuration file? Thanks. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI and ZFS: root mount error
2010/1/16, Volodymyr Kostyrko : > On Fri, 15 Jan 2010 21:13:39 +0100 > Romain Garbage wrote: > >> After setting ahci_load="YES" in /boot/loader.conf, I get a root mount >> error. >> ahci seems to attach to disk correctly (I get ada0 messages with no error) >> >> Without ahci_load="YES", system boots fine, with ata module attaching to >> disk. >> >> I have a full zfs system, set up following wiki instructions: >> http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition >> (MBR scheme, ZFS in a FreeBSD slice, together with a swap partition) >> >> I'm using a GENERIC kernel, RELENG_8 branch. > > I have faced some problems that looks exactly like you say. I haven't > investigated thoroughly after some quick-hack-repairs machine runs > flawlessly. > > 1. I have moved to RELENG_8 from RELENG_8_0. I don't think this is it but > zfsloader support was what I was looking for. > > 2. I reinitialised zfs partitions again with a boot code. But this time I > used bs=512 dd option. > > 3. I recreated zpool.cache and replaced it on my pool. > > Actually I don't know which one helped me, but my bet is for the third step > and maybe for second. A weird thing: I just built and installed a new kernel (RELENG_8, source csuped a few hours ago), just adding "device ahci" to the config file. I get the same error, with driver attaching correctly. Now, adding ahci_load="NO" to /boot/loader.conf and booting the new custom kernel, it just boots fine, ahci attaching to the device, and zfs root gets mounted. dmesg | grep ada ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes)cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 ada0: Command Queueing enabled ada0: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C) ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes) ada1: Command Queueing enabled ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes)cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 ada0: Command Queueing enabled ada0: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C) ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes) ada1: Command Queueing enabled ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) I didn't do anything else, just the line in loader.conf, and the system just works fine. Romain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI and ZFS: root mount error
On Fri, 15 Jan 2010 21:13:39 +0100 Romain Garbage wrote: > After setting ahci_load="YES" in /boot/loader.conf, I get a root mount error. > ahci seems to attach to disk correctly (I get ada0 messages with no error) > > Without ahci_load="YES", system boots fine, with ata module attaching to disk. > > I have a full zfs system, set up following wiki instructions: > http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition > (MBR scheme, ZFS in a FreeBSD slice, together with a swap partition) > > I'm using a GENERIC kernel, RELENG_8 branch. I have faced some problems that looks exactly like you say. I haven't investigated thoroughly after some quick-hack-repairs machine runs flawlessly. 1. I have moved to RELENG_8 from RELENG_8_0. I don't think this is it but zfsloader support was what I was looking for. 2. I reinitialised zfs partitions again with a boot code. But this time I used bs=512 dd option. 3. I recreated zpool.cache and replaced it on my pool. Actually I don't know which one helped me, but my bet is for the third step and maybe for second. -- Sphinx of black quartz judge my vow. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI and ZFS: root mount error
On Sat, 16 Jan 2010 00:29:23 +0100 Oliver Brandmueller wrote: > Check with "zpool status" if your zpool refers to diskslices like > "ad0s1". I use gpt have setup the ZFS mirror to refer to gptids: > > pool: silver > state: ONLINE > scrub: none requested > config: > > NAMESTATE READ WRITE > CKSUM > silver ONLINE 0 0 >0 > mirrorONLINE 0 0 >0 > gptid/9e68d234-f306-11de-a0c4-0002b3b6e838 ONLINE 0 0 >0 > gptid/a025b88c-f306-11de-a0c4-0002b3b6e838 ONLINE 0 0 >0 > > With that kind of configuration I can switch back and forth between > using ATA_CAM or using traditional ATA drivers. Since you're not using > GPT I gues you can use geom labels to do more or less the same thing. > > In short: use labels, nut device names. Saves headaches in many cases. ZFS actually can find disks without any glabel help. I have one server which I have moved recently to ahci and nothing changes for me. ZFS silently accepted new provider names and continue working as usual. -- Sphinx of black quartz judge my vow. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI and ZFS: root mount error
Hi, On Fri, Jan 15, 2010 at 09:13:39PM +0100, Romain Garbage wrote: > After setting ahci_load="YES" in /boot/loader.conf, I get a root mount error. > ahci seems to attach to disk correctly (I get ada0 messages with no error) > > Without ahci_load="YES", system boots fine, with ata module attaching to disk. > > I have a full zfs system, set up following wiki instructions: > http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition > (MBR scheme, ZFS in a FreeBSD slice, together with a swap partition) > > I'm using a GENERIC kernel, RELENG_8 branch. > > My /boot/loader.conf: > zfs_load="YES" > vfs.root.mountfrom="zfs:zroot" > nvidia_load="YES" > snd_hda_load="YES" > tmpfs_load="YES" > coretemp_load="YES" Check with "zpool status" if your zpool refers to diskslices like "ad0s1". I use gpt have setup the ZFS mirror to refer to gptids: pool: silver state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM silver ONLINE 0 0 0 mirrorONLINE 0 0 0 gptid/9e68d234-f306-11de-a0c4-0002b3b6e838 ONLINE 0 0 0 gptid/a025b88c-f306-11de-a0c4-0002b3b6e838 ONLINE 0 0 0 With that kind of configuration I can switch back and forth between using ATA_CAM or using traditional ATA drivers. Since you're not using GPT I gues you can use geom labels to do more or less the same thing. In short: use labels, nut device names. Saves headaches in many cases. - Olli -- | Oliver Brandmueller http://sysadm.in/ o...@sysadm.in | |Ich bin das Internet. Sowahr ich Gott helfe. | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
AHCI and ZFS: root mount error
Hello, After setting ahci_load="YES" in /boot/loader.conf, I get a root mount error. ahci seems to attach to disk correctly (I get ada0 messages with no error) Without ahci_load="YES", system boots fine, with ata module attaching to disk. I have a full zfs system, set up following wiki instructions: http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition (MBR scheme, ZFS in a FreeBSD slice, together with a swap partition) I'm using a GENERIC kernel, RELENG_8 branch. My /boot/loader.conf: zfs_load="YES" vfs.root.mountfrom="zfs:zroot" nvidia_load="YES" snd_hda_load="YES" tmpfs_load="YES" coretemp_load="YES" Regards, Romain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
