October 8, 200916 yr Hey all, Before I was going to install a new HD and begin pushing 1.5TB of data to my unRAID I noticed the following error: Oct 8 03:10:16 Tower kernel: end_request: I/O error, dev sdb, sector 77 sbd is my flash drive! What do I do to protect my array and flash drive data? Full log attached!
October 8, 200916 yr Hey all, Before I was going to install a new HD and begin pushing 1.5TB of data to my unRAID I noticed the following error: Oct 8 03:10:16 Tower kernel: end_request: I/O error, dev sdb, sector 77 sbd is my flash drive! What do I do to protect my array and flash drive data? Full log attached! I would copy the /boot/config folder to a folder on your PC. (over the LAN it would be \\tower\flash\config Then, stop the array, and then power down, and then move the flash drive to your PC so you can run chkdisk or scandisk on it. Odds are it is fine, but who knows. Then, right-click on the drive and safely eject it from the PC, put it back in the unRAID server and reboot. It almost looks like it lost connection and then re-established connection. Did it get bumped perhaps? Joe L.
October 8, 200916 yr Author Joe, Seriously you are the man... and before I proceed I just want to thank you again as you have helped me out many times over the years! I was about to run a parity check on my unRAID server as I was getting ready to add a new HD and it became unresponsive. I rebooted the unRAID server from the //tower menu (not unMenu) After about 5 minutes I tried to load //tower from my web browser and it wouldn't load so I knew something was up I went down to check on the tower and noticed that both of my PATA drive lights were pinged. I switched off the array from the P/S I removed the two PATA drive (only ones left in the system) from their Icydock cages and plugged them directing into the IDE cables into the MOBO I turned the array back on and it began to do a parity check I started unMenu (still haven't figured out how to make it boot automatically) and checked the log and noticed the red. I copied everything from the Flash drive to my PC over the network I will stop parity check, shut down server and bring up the flash drive and run some tests as you suggested.
October 8, 200916 yr Author The type of the file system is FAT. Volume UNRAID created 7/12/2008 12:52 AM Volume Serial Number is 746D-E660 Windows is verifying files and folders... File and folder verification is complete. Windows has checked the file system and found no problems. 1,024,655,360 bytes total disk space. 16,384 bytes in 1 hidden files. 65,536 bytes in 4 folders. 32,145,408 bytes in 57 files. 992,428,032 bytes available on disk. 16,384 bytes in each allocation unit. 62,540 total allocation units on disk. 60,573 allocation units available on disk.
October 8, 200916 yr Author Well... Ran a parity check and got 129 errors!!!! check log.. just want to make sure the correct thing to do here is replace the parity?
October 8, 200916 yr The parity drive has one or more bad sectors (Media error, UNC), roughly around the 60% point of the drive. When the bad sectors could not be read, it reported parity errors. Obtaining a SMART report is imperative, as the first step, and then probably a SMART long test. Then we need to force the drive to remap the sector(s), and then you can run another parity check to correct them. I don't actually know myself, but I think that Joe's Preclear can zero out a range of sectors, or he can construct a dd command for it. Since it is the parity drive, we aren't zeroing out data, just parity info, which will be corrected on the next parity check. I *think* there may be only one bad sector, at LBA 1719763023. Running a SMART long test should clarify exactly which one (or more). One way to proceed would be to read (dd) ranges of sectors around the known bad, and by narrowing the range down on successive runs, isolate what is bad. Then write zeroes to that same range, then start the array and run a parity check.
October 8, 200916 yr Since it appears you used unMENU to grab the syslog, you can use its disk management page to request a "Long SMART Test" on the parity drive. It will take a few hours to run... After it completes you can use the "Smart Status Report" button to get the results. (You use the same "Smart Status Report" button to see its on-going status too) It might be a few sectors, or it might be more... no way to tell just yet. The long test should attempt to read every sector on the disk. Hopefully, it will make some for re-allocation on the next parity check where it will fix them.
October 8, 200916 yr Author Thank you Rob and Joe. I am running a Long Smart Test.... unMenu is sooo nice. Thank you for developing that for us!
October 8, 200916 yr Author Joe, I can't believe I'm going to ask this... where the is 'SMART Status Report' Button? I've looked through all the different pages in unMENU and can't seem to find a button titled that!
October 8, 200916 yr Joe, I can't believe I'm going to ask this... where the is 'SMART Status Report' Button? I've looked through all the different pages in unMENU and can't seem to find a button titled that! What version of unMENU are you running? On earlier versions it was labeled "Smart Statistics" It is the same thing, I just made the button label a bit more descriptive) You can get updated unMENU version 1.2 files including updated package .conf files from this link at google code http://code.google.com/p/unraid-unmenu/downloads/list
October 9, 200916 yr Author Well it looks like running that Long test did the trick. I'm just about through running a parity check and I don't see any errors to report back! Thank you Rob and Joe!
October 14, 200916 yr Author Well my flash drive is officially dead! What are next steps? I have a replacement SanDisk here... and I did backup my Flash a week ago when things started happening... but I don't have a current updated backup of the flash drive. I will begin searching the wiki to see if it tells me what to do!
October 14, 200916 yr If you haven't found it already, see this: "If my flash drive dies or is lost, will I lose my license?" I would also add a reference to this thread, in your email to Tom.
October 14, 200916 yr Author If you haven't found it already, see this: "If my flash drive dies or is lost, will I lose my license?" I would also add a reference to this thread, in your email to Tom. Rob, I appreciate it! Just to confirm.... after I receive the license from Tom I can simply prepare the USB drive as required and then copy my week old backup of my flash drive to the new flash drive including the new Pro license and boot the server, correct? Will a parity sync be required?
October 15, 200916 yr Author So I got the new license from Tom, but I'm having a problem. As I stated I backed up my flash drive a week ago and since added a new hard drive. When I reboot the server it started a parity sync and didn't have my Disk 8 present. When I stopped the parity sync and went to devices to add the disk I am now faced with the two options in unRAID Start will record the new disk information and bring the expanded array on-line. All new disks which have not been factory-erased will be cleared first; and, the array will be available after the clear completes. This process takes time, but the array remains protected at all times. Caution: any data on the new disk(s) will be erased! If you want to preserve the data on the new disk(s), reset the array configuration and rebuild parity instead. I'm sure I want to do this Restore will initialize the stored array configuration; all drives will appear as New, but data disk contents are not affected. I'm sure I want to do this What do I do? Disk 8 has data on it that I do not want to loose.... I should add it is treating Disk 8 as a new disk, which is expected since I'm using a backup of my flash...
October 15, 200916 yr So I got the new license from Tom, but I'm having a problem. As I stated I backed up my flash drive a week ago and since added a new hard drive. When I reboot the server it started a parity sync and didn't have my Disk 8 present. When I stopped the parity sync and went to devices to add the disk I am now faced with the two options in unRAID Start will record the new disk information and bring the expanded array on-line. All new disks which have not been factory-erased will be cleared first; and, the array will be available after the clear completes. This process takes time, but the array remains protected at all times. Caution: any data on the new disk(s) will be erased! If you want to preserve the data on the new disk(s), reset the array configuration and rebuild parity instead. I'm sure I want to do this Restore will initialize the stored array configuration; all drives will appear as New, but data disk contents are not affected. I'm sure I want to do this What do I do? Disk 8 has data on it that I do not want to loose.... I should add it is treating Disk 8 as a new disk, which is expected since I'm using a backup of my flash... You should assign disk8 (which you probably already did) press the "Restore" button.... and use the "Trust-my-parity" process as described in the wiki before subsequently pressing "Start" Joe L.
Archived
This topic is now archived and is closed to further replies.