Re: HEADSUP! GEOM as default in 5 days...
Attempting to mount my Win2K NTFS partition on my laptop after the introduction of GEOM results in immediate 100% reproduceable panics. I built GEOM into my kernel the day after it was introduced into CVS, and none of the commits made since seem to have fixed it. I apologize for not posting my panic messages earlier, but the machine ends up in a state where it can't save a core and I haven't got a null-modem cable for a serial console handy. I decided to go ahead and transcribe this by hand, so there will likely be typos. fstab info: /dev/ad0s1 /win2k ntfsro,noauto 0 0 /dev/ad0s2bnoneswapsw 0 0 Trying mount /win2k with kern.sync_on_panic and debug.trace_on_panic = 0, dumpon /dev/ad0s2b: panic: bundirty: buffer 0xcdbb9a24 still on queue 2 Uptime: 41m37s Dumping 255MB ata0: resetting devices .. [indefinite hang] --- Trying mount /win2k and transcribing ddb trace output: panic: bundirty: buffer 0xcdb93c24 still on queue 2 Debugger(panic) Stopped atDebugger0x54: xchgl %ebx,in_Debugger.0 db trace Debugger(c02ad0a7,c02fb520,c02b31b3,d36fe3fc,1) at Debugger+0x54 panic(c02b31b3,cdb93c24,2,cdb93c24,d36fe444) at panic+0xab bundirty(cdb93c24,1,c02b3051,471,0) at bundirty+0x31 brelse(cdb93c24,1,c02b3051,34a,cdb93c24) at brelse+0x77d bwrite(cdb93c24,12,c02b3051,902,0) at bwrite+0x327 getblk(c8be5940,218fdd,0,400,0) at getblk+0x203 breadn(c8be5940,218fdd,0,400,0) at breadn+0x4a bread(c8be5940,218fdd,0,400,0) at bread+0x4c ntfs_readntvattr_plain(c8be7100,c8c48900,c8c47800,1e0,0) at ntfs_readntvattr_plain+0x330 ntfs_readattr_plain(c8be7100,c8c48900,80,0,1e0) at ntfs_readattr_plain+0x1fb ntfs_readattr(c8be7100,c8c48900,80,0,1e0) at ntfs_readattr+0x490 ntfs_mountfs(c8be5940,c8c47200,d36fe8d8,c0f07680,b) at ntfs_mountfs+0x4a5 ntfs_mount(c8c47200,c8be9480,bfbffa88,d36febec,c0f07680) at ntfs_mount+0x1ce vfs_mount(c0f07680,c8a389f0,c8be9480,1,bfbffa88) at vfs_mount+0x82d mount(c0f07680,d36fed10,c02c7dfe,42d,4) at mount+0xb8 syscall(2f,2f,2f,bfbffd08,bfbffe29) at syscall+0x32e Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (21, FreeBSD ELF32, mount), eip = 0x8049897, esp = 0xbfbff5fc, ebp = 0xbfbffd20 --- sysctl kern.geom.confxml: http://power.doogles.com/~jyoung/confxml sysctl kern.geom.confdot: http://power.doogles.com/~jyoung/confdot dmesg: http://power.doogles.com/~jyoung/dmesg Again, this is 100% reproduceable, so I'd be happy to gather any other information that would help. -- Jason Young, CCIE #8607, MCSE Sr. Network Technician, WAN Technologies (314)817-0131 http://www.wantec.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
÷ Mon, 30.09.2002, × 23:09, Poul-Henning Kamp ÎÁÐÉÓÁÌ: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. Ok, diskcheckd (old binary) no isn't work :( New binary not builds from fresh ports: vbook#/usr/ports/sysutils/diskcheckd 132_ cvs -Rq upd -dP U Makefile vbook#/usr/ports/sysutils/diskcheckd 133_ make === Extracting for diskcheckd-20010823_3 No MD5 checksum file. === Patching for diskcheckd-20010823_3 === Configuring for diskcheckd-20010823_3 === Building for diskcheckd-20010823_3 Warning: Object directory not changed from original /usr/local/ports/sysutils/diskcheckd/work cc -O -pipe -mcpu=pentiumpro -D_PATH_CONF='/usr/local/etc/diskcheckd.conf' -mc pu=pentiumpro-c diskcheckd.c diskcheckd.c: In function `fstypename': diskcheckd.c:251: `FSMAXTYPES' undeclared (first use in this function) diskcheckd.c:251: (Each undeclared identifier is reported only once diskcheckd.c:251: for each function it appears in.) diskcheckd.c:252: `fstypenames' undeclared (first use in this function) diskcheckd.c: In function `logreaderror': diskcheckd.c:298: `DOSPARTOFF' undeclared (first use in this function) diskcheckd.c:299: `NDOSPART' undeclared (first use in this function) diskcheckd.c:300: invalid use of undefined type `struct dos_partition' diskcheckd.c:300: dereferencing pointer to incomplete type diskcheckd.c:301: invalid use of undefined type `struct dos_partition' diskcheckd.c:301: dereferencing pointer to incomplete type diskcheckd.c:301: invalid use of undefined type `struct dos_partition' diskcheckd.c:301: dereferencing pointer to incomplete type diskcheckd.c:312: invalid use of undefined type `struct dos_partition' diskcheckd.c:312: dereferencing pointer to incomplete type diskcheckd.c:318: invalid use of undefined type `struct dos_partition' diskcheckd.c:318: dereferencing pointer to incomplete type diskcheckd.c:318: `DOSPTYP_386BSD' undeclared (first use in this function) diskcheckd.c:322: invalid use of undefined type `struct dos_partition' diskcheckd.c:322: dereferencing pointer to incomplete type *** Error code 1 Stop in /usr/local/ports/sysutils/diskcheckd/work. *** Error code 1 Stop in /usr/local/ports/sysutils/diskcheckd. vbook#/usr/ports/sysutils/diskcheckd 134_ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. -- Vladimir B. Grebenschikov [EMAIL PROTECTED], SWsoft, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days... GEOM does not find da0a; goes to rootmount
In message [EMAIL PROTECTED], Daniel Flickinger writes: Do you have a complete live tree somewhere I could 'fetch' or ftp? Since the errors have been continuing for a week, it looks like I either walk forward from 17 Sep again, or It would help here if you told us what the error you get is. I could suspect that you got cought by the sort + thing. If date | sort +0 gives you an error message, try this: cd /usr/src make installincludes cd usr.bin/sort make obj make depend make all install and see if buildworld works then... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days... GEOM does not find da0a; goes to rootmount
In message [EMAIL PROTECTED], Daniel Flickinger writes: I will note that my loader is dated 27 Sep since there has not been an even close to complete buildworld since then; Something in your tree is not OK then, because I have compiled buildworld many times since the 27th, last time just a few hours ago: cd /bang/src make buildworld TARGET_ARCH=i386 __MAKE_CONF=/dev/null \ _.i386.buildworld 21 i386 buildworld ended on Sat Oct 5 07:31:09 GMT 2002 The problem with the floppy drive is interesting, I guess it means that the SCSI da driver return EBUSY to mean no media rather than ENXIO as it should. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days... GEOM does not find da0a;goes to rootmount
On Sat, 5 Oct 2002, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Daniel Flickinger writes:
I will note that my loader is dated 27 Sep since there
has not been an even close to complete buildworld since
then;
Something in your tree is not OK then, because I have compiled
buildworld many times since the 27th, last time just a few
hours ago:
cd /bang/src make buildworld TARGET_ARCH=i386 __MAKE_CONF=/dev/null \
_.i386.buildworld 21
i386 buildworld ended on Sat Oct 5 07:31:09 GMT 2002
The problem with the floppy drive is interesting, I guess it means
that the SCSI da driver return EBUSY to mean no media rather
than ENXIO as it should.
No, it returns ENXIO. For a details, see sys/cam/scsi/scsi_all.c:
/* DTL WRSOM*/{SST(0x3A, 0x00, SS_FATAL|ENXIO,
Medium not present) },
/* DT WR OM*/{SST(0x3A, 0x01, SS_FATAL|ENXIO,
Medium not present - tray closed) },
/* DT WR OM*/{SST(0x3A, 0x02, SS_FATAL|ENXIO,
Medium not present - tray open) },
Does your system work without the Zip drive plugged in?
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED], Eric Hodel writes: the bit that I cant figure out is that my CD-ROM won't mount the CD I've got in it now, (an 80 minute CDR) but it has pre-geom. Yes, there is a problem with SCSI-CD devices. Can you please try this patch: http://phk.freebsd.dk/patch/scsi_cd.c.patch That patch does not work, sources from Oct 3 -- Eric Hodel - [EMAIL PROTECTED] - http://segment7.net All messages signed with fingerprint: FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04 msg43987/pgp0.pgp Description: PGP signature
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Eric Hodel writes: --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED], Eric Hodel writes: =20 the bit that I cant figure out is that my CD-ROM won't mount the CD I've got in it now, (an 80 minute CDR) but it has pre-geom. =20 Yes, there is a problem with SCSI-CD devices. =20 Can you please try this patch: http://phk.freebsd.dk/patch/scsi_cd.c.patch That patch does not work, sources from Oct 3 I committed a slightly updated version since my last email. Please try a plain -current with/without GEOM now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Thu, Oct 03, 2002 at 07:20:38AM +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Eric Hodel writes: the bit that I cant figure out is that my CD-ROM won't mount the CD I've got in it now, (an 80 minute CDR) but it has pre-geom. Yes, there is a problem with SCSI-CD devices. Can you please try this patch: http://phk.freebsd.dk/patch/scsi_cd.c.patch If this is the same patch you sent me, it is bad now. Using Sept 29th sources + your patch I was able to boot and have SCSI cd devices. When I cvsup'ed to Oct 2nd sources + your patch I lost my SCSI cd devices. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On (2002/10/02 16:27), Bruce Evans wrote: It is a devfs issue that devfs moves things into the kernel where they harder to control and more fatal if they are got wrong. If it's just ownerships and permissions you're worried about, I think the issue could be made moot by some /etc support for devfs(1). In fact, as the loudest supporter of MAKEDEV, you might be the best person to drive its transcription into /etc/defaults/devfs.conf. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Sheldon Hearn writes: On (2002/10/02 16:27), Bruce Evans wrote: It is a devfs issue that devfs moves things into the kernel where they harder to control and more fatal if they are got wrong. If it's just ownerships and permissions you're worried about, I think the issue could be made moot by some /etc support for devfs(1). In fact, as the loudest supporter of MAKEDEV, you might be the best person to drive its transcription into /etc/defaults/devfs.conf. :-) And with devfs(8), you can enact your personal policy just the way you like :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Wed, 2 Oct 2002, Sheldon Hearn wrote: On (2002/10/02 16:27), Bruce Evans wrote: It is a devfs issue that devfs moves things into the kernel where they harder to control and more fatal if they are got wrong. If it's just ownerships and permissions you're worried about, I think the issue could be made moot by some /etc support for devfs(1). In fact, as the loudest supporter of MAKEDEV, you might be the best person to drive its transcription into /etc/defaults/devfs.conf. :-) I don't really like MAKEDEV. It is creating work and bugs by moving problems around that I object to. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Wed, 2 Oct 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Sheldon Hearn writes: ... In fact, as the loudest supporter of MAKEDEV, you might be the best person to drive its transcription into /etc/defaults/devfs.conf. :-) And with devfs(8), you can enact your personal policy just the way you like :-) Not so. I like to use simple utilitities like mknod/chown/chown. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Bruce Evans writes: On Wed, 2 Oct 2002, Sheldon Hearn wrote: On (2002/10/02 16:27), Bruce Evans wrote: It is a devfs issue that devfs moves things into the kernel where they harder to control and more fatal if they are got wrong. If it's just ownerships and permissions you're worried about, I think the issue could be made moot by some /etc support for devfs(1). In fact, as the loudest supporter of MAKEDEV, you might be the best person to drive its transcription into /etc/defaults/devfs.conf. :-) I don't really like MAKEDEV. It is creating work and bugs by moving problems around that I object to. So you don't like DEVFS and you don't like MAKEDEV. Say, how _do_ you access your devices Bruce ? :-) As various people have heard me whine about at conferences for some years now, devices were the first thing that broke the UNIX filesystem model. Manually hacking a numeric index from a kernel table into filesystem nodes is just plain wrong, it is however better than what they did before where they hardwired inode numbers to devices. The next big mistake was networking. The unix filesystem model would have me open(/net/tcp/www.freebsd.org/80, r), not socket(...), bind(...), connect(...). I'll just silently (well, not quite) pass on the sysV IPC fiasco. As long as we operate under the It must be bug-compatible with everything in the world, we will never be able to properly fix these issues which is too bad, but that's life for us. In the meantime, DEVFS is the best I could come up with which makes life simpler for users, developers and administrators, and still retains as many of the flaws as we want to keep. Like it or not, unless you have a better alternative you'll be stuck with it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Wed, 2 Oct 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: I don't really like MAKEDEV. It is creating work and bugs by moving problems around that I object to. So you don't like DEVFS and you don't like MAKEDEV. Say, how _do_ you access your devices Bruce ? :-) Mostly using read() and write() :-). To create them I normally use tar or cp -pR to copy them from another machine (nfs mounted for cp). Yes, major/minor numbers have their weakest points near tar and nfs, but this causes few problems in practice. To create the original versions I must have used mknod(8) or MAKEDEV some time, but I only use these about once a month. Preserving timestamps has given some amazingly old files (much older than the disk they are on :-): $ ls -ltr /dev total 44 crw--- 1 root wheel 7, 0 Sep 14 1991 klog crw-rw 2 root operator 14, 2 May 5 1993 esa0.0 ... crw-rw-rw- 1 root wheel 6, 10 Jun 11 1994 ptypa ... crw-rw-rw- 1 root wheel 5, 10 Jun 11 1994 ttypa klog is so old that it must have have a corrupt time stamp or have been copied from a 386BSD distribution -- 386BSD wasn't released until early 1992 IIRC and I didn't get it until a few months later. Apparently, Julian's scsi drivers were committed by May 5 1993. ttypa may be the worlds oldest pty. I think it actually hasn't been touched since then. Some of the other devices (not shown) are old because modtime timestamps don't work right on them. Ob devfs complaint: timestamps don't work right on devfs either. After booting, ls -lt /dev and some periodic scripts report timestamps in the future because devfs doesn't understand changing the time as specified by /etc/wall_cmos_clock. This bug is more apparent to users in timezones ahead of GMT. As various people have heard me whine about at conferences for some years now, devices were the first thing that broke the UNIX filesystem model. Manually hacking a numeric index from a kernel table into filesystem nodes is just plain wrong, it is however better than what they did before where they hardwired inode numbers to devices. This could have been done without devfs by mapping names of special files to numeric indexes in the kernel. Putting the index in the inode is mainly an efficiency hack. Numeric indexes work quite well in the kernel (better than pointers in the current implementation, since most drivers prefer to work with numbers and call the inefficient replacements of the major() and minor macros a lot). The next big mistake was networking. The unix filesystem model would have me open(/net/tcp/www.freebsd.org/80, r), not socket(...), bind(...), connect(...). I could agree with that. I'll just silently (well, not quite) pass on the sysV IPC fiasco. The next+N mistake was sysctl, which started with numeric indexes and which you improved to support strings. The indexes are worse than for device nodes because they are layered. Supporting and using both of these gave a fine unfinished mess, with complications for both and efficiency for neither. In the meantime, DEVFS is the best I could come up with which makes life simpler for users, developers and administrators, and still retains as many of the flaws as we want to keep. For me, it has saved about 10 minutes of admin time and cost a few working weeks of development time so far. Like it or not, unless you have a better alternative you'll be stuck with it. If it were the only alternative, then I would move somewhere that doesn't have it :-). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Bruce Evans writes: This could have been done without devfs by mapping names of special files to numeric indexes in the kernel. Putting the index in the inode is mainly an efficiency hack. Numeric indexes work quite well in the kernel (better than pointers in the current implementation, since most drivers prefer to work with numbers and call the inefficient replacements of the major() and minor macros a lot). This is actually not true any more. An increasing number of drivers derive their softc pointer directly from the dev_t without the detour over compile-time-fixed-sized arrays of possible unit numbers. In the meantime, DEVFS is the best I could come up with which makes life simpler for users, developers and administrators, and still retains as many of the flaws as we want to keep. For me, it has saved about 10 minutes of admin time and cost a few working weeks of development time so far. I don't think you are anywhere near the mean, or the median for that matter, of FreeBSD users. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
Poul-Henning Kamp writes: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. What, exactly, would you like tested? options GEOM on a random alpha I have laying around seems to cause no harm. I can still boot, and disklabel seems to work (only tried reading labels). Anything else you'd like tested? Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Andrew Gallatin w rites: Poul-Henning Kamp writes: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. What, exactly, would you like tested? options GEOM on a random alpha I have laying around seems to cause no harm. I can still boot, and disklabel seems to work (only tried reading labels). That is already a big help for me to know, thanks a lot! Anything else you'd like tested? Well, anything you can think of which I might have forgotten :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. When I enable geom, vinum won't start claiming it can't find its drives. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: HEADSUP! GEOM as default in 5 days...
Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. A few of my slices got shuffled about, but that was an easy fix, the bit that I cant figure out is that my CD-ROM won't mount the CD I've got in it now, (an 80 minute CDR) but it has pre-geom. # ls /dev/cd* /dev/cd0 I had a cd0 and a cd0c device earlier # cat /etc/fstab | grep cd0 /dev/cd0/disks/cd0 cd9660 ro,noauto 0 0 # mount /disks/cd0 sits with I as its process state. # mount_cd9660 /dev/cd0 /disks/cd0 sits with D as its process state, drive door is locked: root14438 0.0 0.1 204 104 p1 D+4:33PM 0:00.12 mount_cd9660 /de I'll reboot verbosely and see if its the same with other CDs, but until then here are some dmesg snippits: atapci0: Intel PIIX4 ATA33 controller port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter port 0xb000-0xb0ff mem 0xdd00-0xdd000fff irq 7 at device 6.0 on pci0 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs ... Initializing GEOMetry subsystem IPsec: Initialized Security Association Processing. ad0: 1033MB Maxtor 81080 A3 [2100/16/63] at ata0-master WDMA2 ad2: 2014MB QUANTUM BIGFOOT_CY2160A [4092/16/63] at ata1-master WDMA2 Waiting 2 seconds for SCSI devices to settle cd0 at ahc0 bus 0 target 6 lun 0 cd0: TEAC CD-ROM CD-532S 3.0A Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: cd present [355664 x 2048 byte records] da0 at ahc0 bus 0 target 0 lun 0 da0: QUANTUM VIKING II 4.5WLS 4110 Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ahc0 bus 0 target 1 lun 0 da1: FUJITSU M2915S-512 0180 Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2075MB (4250695 512 byte sectors: 255H 63S/T 264C) Mounting root from ufs:/dev/ad0s1a g_pc98_taste: error 0 guessing 17 sectors g_pc98_taste: error 0 guessing 8 heads -- Eric Hodel - [EMAIL PROTECTED] - http://segment7.net All messages signed with fingerprint: FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04 msg43784/pgp0.pgp Description: PGP signature
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Takahashi Yoshihiro writes: In article [EMAIL PROTECTED] Takahashi Yoshihiro [EMAIL PROTECTED] writes: In article [EMAIL PROTECTED] Poul-Henning Kamp [EMAIL PROTECTED] writes: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. It fails to compile a GENERIC kernel for pc98 with GEOM option. Ok, I'll deal with that... And also recent kernel for pc98 without GEOM option cannot mount root filesystem. I got the following error messages. - Mounting root from ufs:/dev/wd0s1a wd0s1: mid 0x94, start 0, end = 4294967295, size 0: OK wd0c: cannot find label (I/O error) wd0s1: cannnot find label (I/O error) Root mount failed: 22 - I have no idea what to do there, and no hardware to debug on :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On (2002/09/30 21:09), Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. There are problems in -CURRENT that have held me back from upgrading for two weeks. These include X crashes and kernel panics. Maybe you'd get more testers if you wait until the latest serious problems are resolved before going ahead. Maybe you wouldn't, though. So I wouldn't be annoyed if you responded with Worth considering, but I don't think waiting would make a difference. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Sheldon Hearn writes: On (2002/09/30 21:09), Poul-Henning Kamp wrote: Maybe you'd get more testers if you wait until the latest serious problems are resolved before going ahead. Maybe you wouldn't, though. So I wouldn't be annoyed if you responded with Worth considering, but I don't think waiting would make a difference. :-) Well, it's more a question of delta-T to Nov1st, if we want to give GEOM good beating, time's up... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Mon, 30 Sep 2002, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. It failed to understandard the partitions on a normal (sliced) boot drive when I tested it a year ago, but I considered this a feature since I don't plan to use it. It somehow worked on an (unsliced) zip drive on the same machine. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Bruce Evans writes: On Mon, 30 Sep 2002, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. It failed to understandard the partitions on a normal (sliced) boot drive when I tested it a year ago, but I considered this a feature since I don't plan to use it. It somehow worked on an (unsliced) zip drive on the same machine. Thank you for the historical perspective :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Mon, 30 Sep 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], David O'Brien writes: On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. What are the exact steps you will take to make it the default; that we should test now? for i in src/sys/*/conf/GENERIC do echo options GEOM $i done cvs commit src/sys/*/conf/GENERIC I hope this is inexact, since it would add 2 style bugs per file. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Bruce Evans writes: On Mon, 30 Sep 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], David O'Brien writes: On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. What are the exact steps you will take to make it the default; that we should test now? for i in src/sys/*/conf/GENERIC do echo options GEOM $i done cvs commit src/sys/*/conf/GENERIC I hope this is inexact, since it would add 2 style bugs per file. It is indeed, I used it only for its paedagogical value :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Tue, 1 Oct 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: On Mon, 30 Sep 2002, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. It failed to understandard the partitions on a normal (sliced) boot drive when I tested it a year ago, but I considered this a feature since I don't plan to use it. It somehow worked on an (unsliced) zip drive on the same machine. Thank you for the historical perspective :-) Oops, it was only a while ago (a month or less). GEOM had not been committed a year ago. The IIRC, I was able to mount the root partition using some magic like mounting it as ad0s2 instead of the correct device ad0a. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Tue, 1 Oct 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: On Mon, 30 Sep 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], David O'Brien writes: What are the exact steps you will take to make it the default; that we should test now? for i in src/sys/*/conf/GENERIC do echo options GEOM $i done cvs commit src/sys/*/conf/GENERIC I hope this is inexact, since it would add 2 style bugs per file. It is indeed, I used it only for its paedagogical value :-) Some of us like exact answers, especially when explicitly asked for. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
Sheldon Hearn wrote: There are problems in -CURRENT that have held me back from upgrading for two weeks. These include X crashes and kernel panics. FWIW, I haven't seen an X crash since removing the TypeI directory from my fontpath. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Bruce Evans writes: On Tue, 1 Oct 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: On Mon, 30 Sep 2002, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. It failed to understandard the partitions on a normal (sliced) boot drive when I tested it a year ago, but I considered this a feature since I don't plan to use it. It somehow worked on an (unsliced) zip drive on the same machine. Thank you for the historical perspective :-) Oops, it was only a while ago (a month or less). GEOM had not been committed a year ago. The IIRC, I was able to mount the root partition using some magic like mounting it as ad0s2 instead of the correct device ad0a. Can you send me the output from dd if=/dev/ad0 count=32 from this disk ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. I am unable to boot a GEOM kernel. What information would you like to help debug this? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. I just added options GEOM on a kernel from yesterday and noticed today that Amanda failed to dump my disks overnight. The problem is that the entries in /dev have the wrong permissions. They should be readable by group operator, but here's what I have: [12:03pm] brooks@minya (/usr/src): ll /dev/ad* crw--- 1 root wheel4, 0 Sep 30 16:10 /dev/ad0 crw--- 1 root wheel4, 1 Sep 30 16:10 /dev/ad0s1 crw--- 1 root wheel4, 2 Sep 30 16:10 /dev/ad0s2 crw--- 1 root wheel4, 3 Sep 30 16:10 /dev/ad0s2a crw--- 1 root wheel4, 4 Sep 30 16:10 /dev/ad0s2b crw--- 1 root wheel4, 5 Sep 30 16:10 /dev/ad0s2c crw--- 1 root wheel4, 6 Sep 30 16:10 /dev/ad0s2e crw--- 1 root wheel4, 7 Sep 30 16:10 /dev/ad0s2f -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg43686/pgp0.pgp Description: PGP signature
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Takahashi Yoshihiro writes: In article [EMAIL PROTECTED] Poul-Henning Kamp [EMAIL PROTECTED] writes: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. It fails to compile a GENERIC kernel for pc98 with GEOM option. Ok, my last commit: phk 2002/10/01 12:29:19 PDT Modified files: sys/sys disklabel.h diskmbr.h diskpc98.h Log: Divorce bsd disklabels, IBM PC MBR's and whatever the things are called on NEC PC98 machines. Sponsored by: DARPA NAI Labs. Revision ChangesPath 1.92 +0 -57 src/sys/sys/disklabel.h 1.92 +3 -354src/sys/sys/diskmbr.h 1.92 +3 -358src/sys/sys/diskpc98.h Should have fixed this issue, please try again. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Brooks Davis writes: I just added options GEOM on a kernel from yesterday and noticed today that Amanda failed to dump my disks overnight. The problem is that the entries in /dev have the wrong permissions. They should be readable by group operator, but here's what I have: [12:03pm] brooks@minya (/usr/src): ll /dev/ad* crw--- 1 root wheel4, 0 Sep 30 16:10 /dev/ad0 Fixed, thanks! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
OK; after building today's -CURRENt on my build machine, I had time to try building the kernel again, but with GEOM. 3 observations so far: * Nearly everything still works. :-) * A verbose boot (my default on the machine in question, since I often need to check things or quote boot messages) with GEOM is *very* verbose. Just thought it might be of interest to mention this. * The ability to use boot0cfg to change the default boot slice seems broken: freebeast(5.0-C)[4] sudo boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5260:254:63 63 4192902 2 0x00261: 0: 1 0xa5521:254:63 4192965 4192965 3 0x00522: 0: 1 0xa5782:254:63 8385930 4192965 4 0x80783: 0: 1 0xa5 1023:254:63 12578895 67697910 version=1.0 drive=0x80 mask=0xf ticks=182 options=nopacket,update,nosetdrv default_selection=F4 (Slice 4) freebeast(5.0-C)[5] sudo boot0cfg -s 1 ad0 sudo halt -p boot0cfg: /dev/ad0: Operation not permitted freebeast(5.0-C)[6] Is this intentional? (I run the box headless, and boot different vesions of FreeBSD on different slices. Generally, I use slice 1 for today's -STABLE and slice 4 for today's -CURRENT; the other slices get clones of these, then get various forms of customization (hacks) that I test.) Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] To paraphrase David Hilbert, there can be no conflicts between the discipline of systems administration and Microsoft, since they have nothing in common. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Tuesday, 1 October 2002 at 9:48:59 +0200, Sheldon Hearn wrote: On (2002/09/30 21:09), Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. There are problems in -CURRENT that have held me back from upgrading for two weeks. These include X crashes and kernel panics. Maybe you'd get more testers if you wait until the latest serious problems are resolved before going ahead. Maybe you wouldn't, though. So I wouldn't be annoyed if you responded with Worth considering, but I don't think waiting would make a difference. :-) Given the number of problems that people have reported in pretty short order after this message, I'd suggest that you fix them first before making it the default. Otherwise people won't even bother trying to test them, and the intention will fail. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Tue, 1 Oct 2002, Brooks Davis wrote: I just added options GEOM on a kernel from yesterday and noticed today that Amanda failed to dump my disks overnight. The problem is that the entries in /dev have the wrong permissions. They should be readable by group operator, but here's what I have: [12:03pm] brooks@minya (/usr/src): ll /dev/ad* crw--- 1 root wheel4, 0 Sep 30 16:10 /dev/ad0 crw--- 1 root wheel4, 1 Sep 30 16:10 /dev/ad0s1 crw--- 1 root wheel4, 2 Sep 30 16:10 /dev/ad0s2 crw--- 1 root wheel4, 3 Sep 30 16:10 /dev/ad0s2a crw--- 1 root wheel4, 4 Sep 30 16:10 /dev/ad0s2b crw--- 1 root wheel4, 5 Sep 30 16:10 /dev/ad0s2c crw--- 1 root wheel4, 6 Sep 30 16:10 /dev/ad0s2e crw--- 1 root wheel4, 7 Sep 30 16:10 /dev/ad0s2f One reason I have no confidence in devfs is that its quality is such as to get things like this wrong. There are magic ownerships and permissions in the source code for N drivers where they are hard to audit. The acd driver still uses the insecure mode 0644 despite this being reported a few years ago. World readability is especially insecure for acd since it gives some write access via some ioctls. E.g., everyone has permission to erase writable media. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], Bruce Evans writes: On Tue, 1 Oct 2002, Brooks Davis wrote: I just added options GEOM on a kernel from yesterday and noticed today that Amanda failed to dump my disks overnight. The problem is that the entries in /dev have the wrong permissions. They should be readable by group operator, but here's what I have: [12:03pm] brooks@minya (/usr/src): ll /dev/ad* crw--- 1 root wheel4, 0 Sep 30 16:10 /dev/ad0 One reason I have no confidence in devfs is that its quality is such as to get things like this wrong. There are magic ownerships and permissions in the source code for N drivers where they are hard to audit. The acd driver still uses the insecure mode 0644 despite this being reported a few years ago. World readability is especially insecure for acd since it gives some write access via some ioctls. E.g., everyone has permission to erase writable media. This is _not_ a DEVFS issue, this is a device driver issue. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Wed, 2 Oct 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: One reason I have no confidence in devfs is that its quality is such as to get things like this wrong. There are magic ownerships and permissions in the source code for N drivers where they are hard to audit. The acd driver still uses the insecure mode 0644 despite this being reported a few years ago. World readability is especially insecure for acd since it gives some write access via some ioctls. E.g., everyone has permission to erase writable media. This is _not_ a DEVFS issue, this is a device driver issue. It is a devfs issue that devfs moves things into the kernel where they harder to control and more fatal if they are got wrong. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADSUP! GEOM as default in 5 days...
Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. There is one known issue on sparc64 which is being worked: On sparc64 nexus_dmamap_create() calls malloc with M_WAITOK which it shouldn't. Change it to M_NOWAIT if you run into this problem before it gets officially fixed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. What are the exact steps you will take to make it the default; that we should test now? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In message [EMAIL PROTECTED], David O'Brien writes: On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. What are the exact steps you will take to make it the default; that we should test now? for i in src/sys/*/conf/GENERIC do echo options GEOM $i done cvs commit src/sys/*/conf/GENERIC -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP! GEOM as default in 5 days...
In article [EMAIL PROTECTED] Takahashi Yoshihiro [EMAIL PROTECTED] writes: In article [EMAIL PROTECTED] Poul-Henning Kamp [EMAIL PROTECTED] writes: Provided nothing terminal pops up in the next 5 days, GEOM will become default in -current on Saturday 5th of october. Please test it now on _your_ configuration and tell me if it fails to work. It fails to compile a GENERIC kernel for pc98 with GEOM option. And also recent kernel for pc98 without GEOM option cannot mount root filesystem. I got the following error messages. - Mounting root from ufs:/dev/wd0s1a wd0s1: mid 0x94, start 0, end = 4294967295, size 0: OK wd0c: cannot find label (I/O error) wd0s1: cannnot find label (I/O error) Root mount failed: 22 - - Mounting root from ufs:/dev/da0s1a da0c: cannot find label (I/O error) da0s1: cannot find label (I/O error) Root mount failed: 22 - --- TAKAHASHI Yoshihiro [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
