February 15, 201214 yr Author Parity check complete with 0 errors. I've also looked at the files on Disk1 and everything seems OK! Thanks a lot everyone! Especially you Peter, you rock!
February 15, 201214 yr Wow, I was about 50/50 that it would just work, but it went great for you considering where you were sitting when this started. You might find a few files corrupted. I really can't say for sure but you were having write issues to 2 drives (not writing is the reason for the red ball) so the failure to write something to disk2 means something might have been corrupted on disk2 and then when the disk2 data was used to rebuild disk1 the corruption would follow over to disk1. If you know what you wrote last then take a look at those files and see how good they are. It also wouldn't be a bad idea to run reiserfsck on both disk1 and disk2 to be sure there aren't any lingering file system errors. Peter
February 16, 201214 yr Author Well that's the thing, it had been a few days I hadn't written anything. If anything was written, it may be winamp writing out some meta data which I don't give a rats ass about. I'll run reiserfsck on both disk and a full smart scan on disk 2.. see if anything's wrong.
February 16, 201214 yr Well that's the thing, it had been a few days I hadn't written anything. If anything was written, it may be winamp writing out some meta data which I don't give a rats ass about. I'll run reiserfsck on both disk and a full smart scan on disk 2.. see if anything's wrong. What's critical is any changes in the superblock, Just by mounting the filesystem, the superblock is updated.
February 16, 201214 yr Author Humm... so I ran smartctl long test on disk 2 and it didn't report any errors, I ran reiserfsck on all disks and it didn't find any error with the exception of disk 2 which it just won't run on... it gives me: "bread: End of file, cannot read the block (488378373)." What does that mean? when mounted I can access files on the drive np..
February 16, 201214 yr Humm... so I ran smartctl long test on disk 2 and it didn't report any errors, I ran reiserfsck on all disks and it didn't find any error with the exception of disk 2 which it just won't run on... it gives me: "bread: End of file, cannot read the block (488378373)." What does that mean? when mounted I can access files on the drive np.. That's not good. Either a pointer in the superblock is wrong or there's a bad spot on the disk. You can try and run badblocks in non destructive read mode to see what it finds. if smartctl long test and badblocks non destructive read mode are good, then the drive may have high level format issues and I might attempt to get my data onto a different drive, then reformat it.
February 17, 201214 yr Author Wow... badblocks takes SOOO much time to run its insane! It only did 1/8 of the drive and it's been more than 12hrs.. so far it found the same error that was stopping reiserfsck: bread: End of file, cannot read the block (488378373). Whenever it's gonna be done checking the disk (4 days maybe?), if there's nothing else than that, is there any way to fix it?
February 17, 201214 yr Wow... badblocks takes SOOO much time to run its insane! It only did 1/8 of the drive and it's been more than 12hrs.. so far it found the same error that was stopping reiserfsck: bread: End of file, cannot read the block (488378373). Whenever it's gonna be done checking the disk (4 days maybe?), if there's nothing else than that, is there any way to fix it? bad blocks in read non destructive mode shouldn't take all that long unless the drive has issues with reading the data. in nondestrutive read/write mode it will take a week. in destructive write mode it takes about 2-4 days. Check your smart report after the badblocks non destructive read mode is finished. See if you have pending sectors or reallocated sectors has increased. I personally would try to move as much data via the OS as I could to another disk with rsync. I might do a md5deep down the whole disk first to get a base reference on hashes. move the files with rsync. Then check them Another choice is a disk to disk copy using dd_rescue via rip linux or something like that. I was able to save a disk that had a bad spot. Do a search on ddrescue there are a few stories about it here.
Archived
This topic is now archived and is closed to further replies.