Re: A tool for remapping bad sectors in CURRENT?
On Mon, 8 Mar 2010, Miroslav Lachman wrote: Eugeny N Dzhurinsky wrote: Hello, all! Recently I've started to see the following logs in messages: Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Currently unreadable (pending) sectors Mar 8 12:00:24 localhost smartd[795]: Device: /dev/ad4, 2 Offline uncorrectable sectors smartctl did really show that something is wrong with my HDD, but still no remaps - just read errors. SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted: read failure 60% 1198 222342559 # 2 Extended offlineCompleted: read failure 60% 1187 222342557 # 3 Extended offlineCompleted: read failure 60% 1180 222342559 # 4 Short offline Completed without error 00% 1178 - # 5 Extended offlineAborted by host 90% 1178 - and ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE ... Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 0 ... Now can I find out which file owns the LBAs 222342557 and 222342559 ? How do I force remapping of these sectors? I assume that I have to write something directly to the sectors? We have this problem from time to time on bunch of machines. As we are using gmirror, the easiest way is to force re-synchronization (rewrite) of the whole drive. The problem is when there are Pending unreadable sectors on both drives - it ends up with read error and some file(s) are corrupted, but there is no easy way (on FreeBSD) to find what file. *cough* zfs *cough* I believe this kind of silent corruption is precisely what zfs was designed to prevent. Even though you do have a mirror, how do you know which copy is the correct one? If one drive re-allocates the sector silently, what is the recovery method? If gmirror synchronizes, how do you make sure that the *good* copy is the one synchronized? You'll notice it eventually if you see it in a garbled file, but how does the filesystem handle it? I tried it in the past with fsdb / findblk, but it does not work as I expect or I do not fully understand the needed calculations with slices + partitions offsets / LBAs and right meaning of the term block. It seems there are several meaning in different contexts. It would be nice if somebody with enough FS / GEOM knowledge can write some HowTo or shell script to do the calculations and operations to find file containing bad sector(s) and put it in FAQ, Handbook, or Wiki. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: GENERIC from today does not detect system console on my box
On Sat, 17 Jun 2000, Donn Miller wrote: On Sat, 17 Jun 2000, Matthew Dillon wrote: My test box, with a pristine 5.x kernel, crashes on boot... it only gets a few lines in, prints the amount of memory the machine has, and BEWM. Low memory page fault. I saw the same thing myself. It turns out, though, that I was using COPTFLAGS= -march=pentium -Os -pipe to compile my kernel. When I used the stock opt flags of COPTFLAGS= -O -pipe to compile my kernel, my machine booted OK. It appears as though some changes were put in the tree that are sensitive to optimizations above -O -pipe. My machine never behaved this way before with high optimizations until the new changes were put into -current about 1 or 2 days ago. Well -pipe isn't technically an optimization... But I was using -O2 and couldn't boot... A kernel with -O will boot. One thing I noticed when changing the flags was that the modules built along with your kernel don't use the compiler flags set in my kernel config file. Has anyone considered addressing this by moving the module objects etc into the kernel build directory? Seems to me it would make maintaining multiple kernels on a single machine even easier. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current kernel broken?
As of about 7pm EDT I can't boot a -current kernel. I _can_ boot a kernel from the 13th I snagged from a snapshot kernel disk, and I can boot the snapshot from the 15th (but since userconfig does not work the lnc device spams so many error messages the system never reaches a prompt). Already did the make clean depend all install for /sys/boot/i386 and that was no help. The kernel just freezes _right_ after trying to boot... I'm not sure how far its getting, I'll have to play around with a debug kernel and see what I can get from it (if anything). Cheers, WM -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with PCM and ESS 1868
I was about to post something like this myself. I've got an SBLive and I hear the same pops and clicks during any audio playback (mp3/wav/whatever). It all worked great up until a couple days ago. On Sun, 11 Jun 2000, Donn Miller wrote: The recent commits to PCM, as of a few days back, have given me problems with my ESS 1868. When I play MP3's with mpg123, I get a lot of loud pops and clicks during playback. Otherwise, the MP3s DO play all the way through. However, when I try to play MP3s with Real Player 7, it just hangs at the beginning, and doesn't play the MP3. Before the commits to PCM, I was able to play MP3s OK with Real Player 7. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LINT broken. (in_cksum changes)
I sent a note to the committer on these last night. LINT must need some modification, because the error is also present in netinet6/ipsec.c. There are some ifdef's around it that point to LINT needing some extra options. On Sun, 7 May 2000, Nick Hibma wrote: Is it only me that ever compiles LINT? The checksum changes went in a few days ago. Please, people, when you move code around or change a function that is used in more than a fixed set of files, compile LINT. If unsure, compile LINT. It's an extra five minutes, but well worth it. linking kernel fil.o: In function `fr_tcpsum': fil.o(.text+0xf47): undefined reference to `in_cksum' ip_fil.o: In function `send_reset': ip_fil.o(.text+0xd7d): undefined reference to `in_cksum' ip_fil.o: In function `ipfr_fastroute': ip_fil.o(.text+0x10f1): undefined reference to `in_cksum' ip_fil.o(.text+0x1316): undefined reference to `in_cksum' ip_fil.o(.text+0x1380): undefined reference to `in_cksum' ip_mroute.o(.text+0x19d6): more undefined references to `in_cksum' follow I just couldn't be bothered to fix it. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please test for 8G-OVER-Booting with /boot/loader
Little tip for would-be grub users... I had to play with the compiler flags quite a bit to get a bootable image. I suggest taking the flags used to compile the FreeBSD boot loaders and using them. On Thu, 30 Mar 2000, Vladik wrote: Hi, for now I am doing this every time (but I also do not reboot too often). GRUB has a curses-like based menu thing where you can specify what to boot and how. You have to set the config file during the compilation. And then compile, and then build the floppy with that or install on to the MBR. And I have not done that yet. -- Vladislav Charles Anderson wrote: Do you do this everytime or just to get things started? If it's everytime, man that's a pain, if it's just to get things started it's easier than what I did. (but now I get a list of what I want to boot from the NT bootloader, and I just hit the arrow down to FreeBSD and go.) -Charlie On Wed, Mar 29, 2000 at 03:21:39PM -0500, Vladik wrote: Hello, I am not sure if this exactly on topic, but this is how I boot freeBSD partition that is installed beyond cyl 1024 I use GRUB boot loader that understands LBA (www.gnu.org/grub) Once GRUB boots from a floppy, go to GRUB's command prompt and do the following: root (hd0,3,a) # or whatever your FreeBSD root slice is #after the command above, it mounted the partition kernel /kernel -remount boot When kernel boots to the point where it needs to mount a root partion it will ask you, in there you type ufs:/dev/ad0s4a Vladislav -- Charles Anderson[EMAIL PROTECTED] No quote, no nothin' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ntpd hanging machine
On Wed, 1 Mar 2000, Ollivier Robert wrote: According to Wes Morgan: merge. Until that point I was using the stock ntp4 from udel with no problems. But I tried the one shipping with 4.0 and it locks up completely (looks like a hardware lockup). The ntp4 from udel works completely though. Odd :) Yes, that's odd. I've never seen that... Can you try to compile a kernel with DDB and try to see whether it hits the debugger or not ? Already tried, no go. Its a complete lockup. However, I just updated to 4.0.99g from the udel ftp, and I am seeing the same lockups. Someone suggested trying it w/o the rtprio calls, which I am rebuilding for as I write this. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ntpd hanging machine
On Mon, 28 Feb 2000, Matthew Frost wrote: I'm experiencing some problems with ntpd. It would appear that a few (10-15) minutes after I start it, the machine crashes completely... Feb 28 14:10:02 egrorian ntpd[153]: ntpd 4.0.99b Mon Feb 28 12:12:17 GMT 2000 (1) Feb 28 14:10:02 egrorian ntpd[153]: using kernel phase-lock loop 2040 Feb 28 14:10:02 egrorian ntpd[153]: using kernel phase-lock loop 2041 And then locked solid.. I've been seeing the exact same behavior ever since the big ntp4 merge. Until that point I was using the stock ntp4 from udel with no problems. But I tried the one shipping with 4.0 and it locks up completely (looks like a hardware lockup). The ntp4 from udel works completely though. Odd :) -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATA and DMA
Has there been any resolution to the known-broken-dma drives and the ata driver? I haven't seen any commits or LINT options to this effect, and it seems to me that since it is the new default driver that something should be in place before it goes to -release. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATA and msdosfs problems / corruption
When attempting to copy a large file over to a FAT partition, I had these errors pop up: Nov 27 16:26:59 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:17 volatile /kernel: ata0: resetting devices .. WARNING: WAIT_READY active=ATA_ACTIVE_ATA Nov 27 16:28:17 volatile /kernel: done Nov 27 16:28:18 volatile /kernel: ta0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:18 volatile /kernel: ata0: resetting devices .. done Nov 27 16:28:18 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:18 volatile /kernel: ata0: resetting devices .. done Nov 27 16:28:18 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:19 volatile /kernel: ata0: resetting devices .. done Nov 27 16:28:19 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:19 volatile /kernel: ata0: resetting devices .. done The errors continue until the system either panicked and rebooted or just plain rebooted, I was not at the console. However, the FAT volume was corrupted along with the boot loader (grub) overwritten to some extent. I'm not 100% sure if it was just the partition table or the entire volume. Next, I cvsup'd and built new kernel+modules, and the same error happened, but there was no reboot and a couple new error showed up: Nov 27 18:24:33 volatile /kernel: ad0: HARD WRITE error blk# 1912525 status=51 error=10 This error occurred for several different blocks. The two drives are identified as: ad0: ST32140A/08.08.04 ATA-? disk at ata0 as master ad0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, DMA ad1: WDC AC418000D/J78OA30K ATA-4 disk at ata0 as slave ad1: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 31 depth queue, DMA The motherboard is fairly old and does not support ATA/66 etc, and the drive with the fat fs has been rock solid so I doubt it has suddenly gone bad. I'd like to test this with DMA turned off, what flags will disable that? -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gdb trouble in 4.0-current
Is anyone seeing a problem like the one below? This is happening to me on quite a few binaries that used to be gdb'able before I installed a new world on the 13th... [by-tor@volatile:~/mms-0.90$]: gdb ./mms GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (gdb) b read_key Breakpoint 1 at 0x804a4d7: file mms.c, line 252. (gdb) r Starting program: /usr/home/by-tor/mms-0.90/./mms warning: find_solib: Can't read pathname for load map: Bad address Segmentation fault (core dumped) The libraries involved are ncurses, panels and of course libc. The panels library is NOT the stock lib (it doesnt work for some reason), I gleaned it from the ncurses-5.0 release. All this stuff worked a week ago :). The binaries run fine, I just can't debug 'em... I'm continuing to operate under the assumption that it is my fault, but if anyone has some pointers that would be great! -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libpanel status
Recently, the libncurses source tree was updated to a 5.0 prerelease snapshot, which is great. However, one app that I develop also uses the panels library on top of the regular ncurses lib. As it is, the panel library is incompatible with the ncurses 5.0 library (at least, the 5.0 panel lib) and its a bit of a pain to fix symlinks every time i make world. And FWIW I don't use the ncurses port because (as is the case with some ports) it installs into freakish locations and no sir I just don't like it (plus its only 4.2). So my question would be, how come it isnt updated? WM -- The difference between genius and stupidity is that genius has its limits. Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcm oddity
I noticed a little quirk in the pcm driver -- it is reversing the channels in my sb16! The first couple times I play a certain mp3 that starts out (normally) in the left channel, it plays correctly in the left channel. Then suddenly it will switch, and start out in the right channel. The mixer still works properly, just the DSP (I think anynway) seems to be reversing the channels somewhere internally. It's odd, to say the least. My kernel is -current as of late sept 22. Can anyone else duplicate this? WM -- The difference between genius and stupidity is that genius has its limits. Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Stuttering mtv with newpcm es1370 card
On Thu, 9 Sep 1999, Chris Piazza wrote: Hi, Earlier today I was trying to watch a short mpeg and found out that it's impossible with newpcm. The sound (and picture) stutters constantly. It works with a kernel from August, 31 (oldpcm). Anyone else able to reproduce this or have any ideas? pcm0: AudioPCI ES1370 irq 5 at device 10.0 on pci0 http://www.r33t.org/files/cute.mpg for a laugh. Not just this mpeg has this problem, though. I can't exactly reproduce it, but for the past couple of days with -current, mtvp/mtv just freezes for no apparent reason. This is under both the old snd0 and new pcm driver. Of course NOTHING works with the new pcm driver -- its almost like buffer is filling up and never emptying, I've had it loop through the same small bit of sound continuously until I cat /dev/null /dev/dsp. WM -- The difference between genius and stupidity is that genius has its limits. Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
