April 11, 201412 yr Author razr: First, I would suggest you boot in 'safe' mode because I don't have any knowledge of what your webGui add-on does. Next, Stop the array, unassign disk1, then Start array. unRaid will see disk1 is missing and disable it. Now does the disk still show as unformatted? If not, do you see your files when browsing the disk1 share? (But don't write anything just yet please). I just started the array...normally to run this test -f /boot/unraidsafemode to boot into safe mode. It does not do anything......I do not think it is booting. Also disk 1 now shows blue dot. Is there any other way of booting in safe mode?
April 11, 201412 yr razr: First, I would suggest you boot in 'safe' mode because I don't have any knowledge of what your webGui add-on does. Next, Stop the array, unassign disk1, then Start array. unRaid will see disk1 is missing and disable it. Now does the disk still show as unformatted? If not, do you see your files when browsing the disk1 share? (But don't write anything just yet please). I just started the array...normally to run this test -f /boot/unraidsafemode to boot into safe mode. It does not do anything......I do not think it is booting. Also disk 1 now shows blue dot. Is there any other way of booting in safe mode? You boot into safe mode by selecting it on the Boot menu - when it comes up, hit a key within 3 seconds. Disk1 should not show a blue dot - if there is no disk assigned to it, it should be grey.
April 11, 201412 yr Trying to help ... Earlier I had him disconnect disk1 (physically), reboot, and try to start the array. Here is his post of screenshots after doing so ... http://lime-technology.com/forum/index.php?topic=32849.msg301742#msg301742
April 11, 201412 yr Trying to help ... Earlier I had him disconnect disk1 (physically), reboot, and try to start the array. Here is his post of screenshots after doing so ... http://lime-technology.com/forum/index.php?topic=32849.msg301742#msg301742 Something is wrong about those screen shots given the state - Like I suggested earlier, he needs to boot in safe mode or remove that webGui plugin.
April 11, 201412 yr I did update parity to a 4 tb drive ove two months ago and the old parity became disk1. Okay, this explains exactly what happened -- it also means UnRAID worked exactly as it was supposed to ... it was simply doing that with an old (no longer correct) configuration. This is confirmed by reviewing you older thread (which is now available, thanks to the link provided by trurl). If the new(2 months old) parity disk was not in the equation while everything happened.......how is it not usable now? It would have been -- if you had realized exactly what had happened, and done NOTHING except boot to the correct flash drive with disk1 disconnected (so it was seen as "missing"; then shut down and put a new drive in place of disk1; then booted -- assigned the new drive as disk1; and then started the array. However ... somewhere along the way, the configuration info has been corrupted. The Web GUI picture you posted [ http://lime-technology.com/forum/index.php?topic=32849.msg301742#msg301742 ] shows Disk1 as "Not Installed" -- not "Missing" ... but at the same time it shows it as an "Unformatted" disk. I'm surprised at this display. I get that disk1 is bad but the rest?? The rest should all be fine -- at least the data disks. Question: Did you do a "clean" shutdown the last time you shut down the system with the RIGHT flash drive? [bEFORE you booted with the wrong one] If not, then what MAY have happened is that after you realized you had booted with the incorrect flash drive, you booted with the correct one ... but due to the unclean shutdown it started a parity check and began to update the parity drive. However, these updates would be incorrect -- since the reason for sync errors was the changed data on Disk1 (caused by the incorrect boot to the old flash drive). Thus the new parity info is no longer valid either. If that did NOT happen, then you should indeed be able to install a new disk in the Disk1 slot, and do a reconstruction of the old drive. But if it DID happen, then Disk1 is simply not recoverable (since you've already confirmed that Reiserfsck won't help). Too late now, but for future reference, if you have un-backed-up data on a disk that's giving you issues, the FIRST thing you should do before taking ANY action that may result in writes to that disk is to attach it to another system (a PC with LinuxReader installed is fine) and COPY as much of your data as you can access to a backup location. The #1 rule of data recovery is to NEVER write to the disk you're trying to recover from. Of course an even more fundamental rule is to BACKUP your data
April 11, 201412 yr Author I start the array....get the blue screen with the contdown.. I see only unRAID OS and Memtest 86+ If I hit tab, get the same... command bzimage initrd=bzroot I do not know how to boot in safe mode It does not give me the option for safe mode
April 11, 201412 yr I start the array....get the blue screen with the contdown.. I see only unRAID OS and Memtest 86+ If I hit tab, get the same... command bzimage initrd=bzroot I do not know how to boot in safe mode It does not give me the option for safe mode Are you sure this is a v5.0.5 version of UnRAID? There should be 3 options on the initial boot screen -- normal UnRAID, Safe Mode, and Memtest.
April 11, 201412 yr I start the array....get the blue screen with the contdown.. I see only unRAID OS and Memtest 86+ If I hit tab, get the same... command bzimage initrd=bzroot I do not know how to boot in safe mode You said you're on 5.0.5 right? You have an imcomplete upgrade. Just to get on the same page, please install a fresh version of 5.0.5 as follows: 1. Power down server, remove flash and plug into a PC 2. Drag the 'config' directory to your disktop (to make a backup of it) 3. Reformat the flash 4. Copy all the 5.0.5 files to the flash. 5. Delete the 'config' directory on the flash. 6. Drag the 'config' directory from your desktop to your flash 7. Click on 'make_bootable.bat' 8. Eject flash, plug back into server, power up server. You should now have the 'safe mode' option in the boot menu, but actually it doesn't matter because if you followed the directions exactly as above there should be no plugins on the flash either. Now go to Main page and unassign Disk 1 - it should look something like the attached screenshot (though in this test system we only have 3 drives).
April 11, 201412 yr So I will boot with disk1 physically in the array and then un-assign it? Yes, that's correct. Note, however, that with all disks green and disk1 showing as unformatted, it's not looking very good at the likelihood of being able to recover it. Do you have a saved backup copy of your CORRECT flash drive from before you made the mistake of booting to the wrong drive ?? If so, Tom can hopefully guide you through exactly what to copy off of it to let UnRAID know exactly what the configuration needs to be to allow a successful rebuild of Disk1.
April 11, 201412 yr Ok all done...same screen.....array stopped....unassigned disk1 Disk 1 shows as 'missing' then right? If so go ahead and Start array and let me know how disk 1 shows up afterwards.
April 11, 201412 yr see attachment That's unfortunate. I haven't read through both threads to see the exact sequence taken, but if disk1 device was the only one clobbered, this procedure should have worked. Your next step is to run a file system recovery utility to try and recover as much of the file system as you can. From your screenshot it appears "sdc" is the unassigned device - you can confirm by stopping array and look at the drop down list. Assuming it is, you type this at the console or telnet session: reiserfsck /dev/sdc1 Note that you added a '1' to 'sdc'. The program will ask you to type 'Yes' to continue. If it finds remnants of file system it will ask you to re-run with a specified option. But before you do this, please post what the program outputs.
April 11, 201412 yr Question - do you have a backup of your Config file from a time when the system was configured with the current disks? If so, why not try that?
April 11, 201412 yr Author Question - do you have a backup of your Config file from a time when the system was configured with the current disks? If so, why not try that? I do have it. But when I I did it before.....unraid dissapears....I think the initial problem was in that folder. Should I try???
April 11, 201412 yr Question - do you have a backup of your Config file from a time when the system was configured with the current disks? If so, why not try that? I do have it. But when I I did it before.....unraid dissapears....I think the initial problem was in that folder. Should I try??? Guys - this is not going to make a difference. razr: from your email you say this is your config: Parity WDC_WD40EFRX-68WT0N0_WD-WCC4E0553678 Disk 1 ST3000DM001-9YN166_S1F0PQ9S Disk 2 ST3000DM001-1CH166_Z1F1YREJ Disk 3 WDC_WD20EARX-00PASB0_WD-WCAZAC998124 And a cache drive. This is the config you had before the trouble began, correct?
April 11, 201412 yr I do have it. But when I I did it before.....unraid dissapears....I think the initial problem was in that folder. Should I try??? That's what I asked you earlier ... Do you have a saved backup copy of your CORRECT flash drive from before you made the mistake of booting to the wrong drive ?? If so, Tom can hopefully guide you through exactly what to copy off of it to let UnRAID know exactly what the configuration needs to be to allow a successful rebuild of Disk1. IF it's the correct config, AND IF YOU HAVEN'T done ANYTHING that would have caused parity to be written to [i.e. written any new data to the array; or booted with the correct flash disk after an unclean shutdown]; then restoring to this config should then let the process several of us have outlined work fine -- i.e. Boot; Stop the array; Unassign Disk1; Start the array (it should now show Disk1 as MISSING); Stop the array; assign a new disk to the Disk1 slot; and then Start the array. ... UnRAID would then reconstruct the disk. Note you can tell is this is going to work after you've booted and see a "Missing" Disk1. At that point, go to \\Tower\Disk1 from Windows Explorer and see if you can see the contents of the disk [Even though it's missing, UnRAID will reconstruct the contents from the other drives in the array]. If you can "see" the disk okay at that point, a rebuild will work just fine.
April 11, 201412 yr I start the array....get the blue screen with the contdown.. I see only unRAID OS and Memtest 86+ If I hit tab, get the same... command bzimage initrd=bzroot I do not know how to boot in safe mode It does not give me the option for safe mode I only have two options, version '5.0.5'. Are you sure this is a v5.0.5 version of UnRAID? There should be 3 options on the initial boot screen -- normal UnRAID, Safe Mode, and Memtest. Me neither (I'm 'tracking' this thread, not for any reasons other than it looks interesting (sorry razr37!)).
April 11, 201412 yr Question - do you have a backup of your Config file from a time when the system was configured with the current disks? If so, why not try that? I do have it. But when I I did it before.....unraid dissapears....I think the initial problem was in that folder. Should I try??? If you do try this, just remember to unplug disk1 before booting up, like I said on page 1..
April 11, 201412 yr Author see attachment That's unfortunate. I haven't read through both threads to see the exact sequence taken, but if disk1 device was the only one clobbered, this procedure should have worked. Your next step is to run a file system recovery utility to try and recover as much of the file system as you can. From your screenshot it appears "sdc" is the unassigned device - you can confirm by stopping array and look at the drop down list. Assuming it is, you type this at the console or telnet session: reiserfsck /dev/sdc1 Note that you added a '1' to 'sdc'. The program will ask you to type 'Yes' to continue. If it finds remnants of file system it will ask you to re-run with a specified option. But before you do this, please post what the program outputs. Started the array in Maint mode..ran reiserfsck reiserfs_open: the reiserfs superblock cannot be found on /dev/sdc1. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb.
Archived
This topic is now archived and is closed to further replies.