January 15, 201115 yr I removed a drive from my array after doing a parity check to make sure all the drives were OK. After removing the drive, obviously I needed to do an "initconfig" which invalidates parity. I then started the parity build, but there was a problem I hadn't noticed -- unRAID had mounted two drives, but it could not write to them and they were showing at a temperature of "0". There were a ton of errors on the unRAID main page. So, I stopped the parity build, then attempted to stop the array. It wouldn't stop. I waited for a while, then got impatient and powered down. Which may have been a mistake... On powering up, unRAID found all the drives correctly, but now is showing one as unformatted! Disaster! Should I do a reiserfsck? Help, please! Syslog attached. EDIT: These lines in the syslog look bad: Jan 15 18:31:00 Tower kernel: REISERFS warning (device md2): sh-2006 read_super_block: bread failed (dev md2, block 16, size 4096) Jan 15 18:31:00 Tower kernel: REISERFS warning (device md2): sh-2021 reiserfs_fill_super: can not find reiserfs on md2 syslog-15-01-11a.zip
January 15, 201115 yr Author Thanks Joe. Here's the result: root@Tower:~# umount /dev/md2 umount: /dev/md2: not mounted root@Tower:~# reiserfsck --check /dev/md2 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error).
Archived
This topic is now archived and is closed to further replies.