Re: Slow link/Capacity changed + Kernel OOPS... possible hardware issues, ideas?
On Fri, Oct 8, 2010 at 11:00 PM, Evert Vorster evors...@gmail.com wrote: Hi there... I'm not an expert. however, since you don't care about the data on the SSD anymore, reformat it, and fill it up, then verify what you have written. However, if the capacity has changed, would that not be enough reason to have ASUS replace it? yeah, i suppose i could :-) so i tried throwing ubuntu 10.10 on it (had archlinux previously), as i made a live USB disk so my fiancé could use it to write a paper today/tomorrow, and sure enough it worked, no problems whatsoever. been running several hours now after install... so i'm fairly convinced the SSD is still good enough, and i have no idea at this point what went wrong. oh well. C Anthony -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Slow link/Capacity changed + Kernel OOPS... possible hardware issues, ideas?
On Thu, Oct 07, 2010 at 10:07:47PM -0500, C Anthony Risinger wrote: well after recently talking about how i haven't had any problems with btrfs on several machines for ~1.5yrs... it happens :-( ) 2.6.35 kernel ) btrfs on partition 2 of sda ) no special mkfs or mount options used (except ssd) my fiancé's EEE S101 netbook, w/SSD, is failing hard. when booting normally (subvol=__active), no special boot options, it hangs at udev... it all started today, when it suddenly froze during normal use, and i was forced to hard power off. it hasn't started up correctly since. using an Archlinux rescue usb disk (archboot), i tried to tar + ssh backup the system to another machine (i can still mount the btrfs disk); i tried a couple times, and it always transfers ~1.3MB then pukes. the last time i managed to get the kernel log somehow, as it didn't lockup... can anyone point me in the right direction? it looks like maybe the SSD is failing to me (all the slow link and capacity changed to 0 stuff), but i really don't know. i knew there was a reason they were selling these things cheap on Newegg!!! i have backups of important data, but i'd rather not have to set the damn thing up again; you know how it is :-), should have backed up the whole system, whoopsie, next time. the mayhem starts with: Oct 8 02:38:26 (none) kernel: btrfs bad tree block start 24630358016 24630292480 Ok, so the drive has decided to jumble up our blocks a little bit. This message means we're finding the wrong data at a given offset. I can help you copy things off but I don't think this FS is going to be good any longer. Are you interested in copying the latest bits off or do you just want to cut your losses? -chris -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Slow link/Capacity changed + Kernel OOPS... possible hardware issues, ideas?
Hi, can anyone point me in the right direction? it looks like maybe the SSD is failing to me (all the slow link and capacity changed to 0 stuff), but i really don't know. i knew there was a reason they were selling these things cheap on Newegg!!! Yes, the read errors are coming all the way up from the hardware; I don't think this is a btrfs problem. There's not much btrfs could do to help, except (over time) grow to handle I/O errors without BUG()ing out. -- Chris Ball c...@laptop.org One Laptop Per Child -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Slow link/Capacity changed + Kernel OOPS... possible hardware issues, ideas?
On Thu, Oct 7, 2010 at 10:20 PM, Chris Ball c...@laptop.org wrote: Hi, can anyone point me in the right direction? it looks like maybe the SSD is failing to me (all the slow link and capacity changed to 0 stuff), but i really don't know. i knew there was a reason they were selling these things cheap on Newegg!!! Yes, the read errors are coming all the way up from the hardware; I don't think this is a btrfs problem. There's not much btrfs could do to help, except (over time) grow to handle I/O errors without BUG()ing out. hmm, i'll have to keep playing with it i guess. /dev/sda1 is a ext2 boot partition; i tar + ssh'ed that several times to my other machine without problems... i thought it would trip an issue if it really was hardware, but it didn't, even after 30+ times. i'll try to reinstall i guess, unless anyone has other input. i'll probably just have to ask ASUS to replace it, because i don't think i've even had it 6mo yet... :-O thanks, C Anthony -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
