April 26, 200917 yr I had a disk fail causing unraid to not be able to mount any of my disks. Being in a "panic", lack of experience I must have hit the restore button causing me to update my configuration. Old Configuration: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ parity ata-ST31500341AS_9VS03ZG0 1,465,138,552 - - - - disk1 ata-ST31500341AS_9VS076N7 1,465,137,496 - - - - disk2 ata-ST31500341AS_9VS090S3 1,465,138,552 - - - - disk3 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0725685 976,761,496 - - - - disk4 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ1169028 976,762,552 - - - - Current Configuration: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (blue dot) parity ata-ST31500341AS_9VS03ZG0 30°C 1,465,138,552 - - - - (blue dot) disk1 ata-ST31500341AS_9VS076N7 30°C 1,465,137,496 - - - - (blue dot) disk2 ata-ST31500341AS_9VS090S3 29°C 1,465,138,552 - - - - (blue dot) disk3 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0725685 27°C 976,761,496 - - - - Command area Stopped. Initial configuration ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ So I currently stand at having a missing disk, the parity being somewhat recient and trying to minimize my loss of data. Is there a way to tell unraid about my old configuration, use the partiy to pull the data off the missing disk 4? I can get unraid to boot with the old disk in the system (to rewrite the configuration) but unraid then will not be able to mount any drives due to the bad disk and it thinks I need to regenerate parity. What I "think" I need to happen is this: (1) Write the old config. (2) Force the parity & status of the array to be good. (3) Power down and pull out the bad "disk4" (4) Copy data from parity built disk4 to the good disks. (5) Reset the array to only having disks1 - 3 & rebuild parity. Is this possible or is my data on disk4 lost for good? Thanks for any help anyone can offer. Tim
April 26, 200917 yr Yes - there is a way - so long as you have not started the array with the new configuration. You will need a spare disk of 1T or 1.5T. I have to run but will post directions a little later.
April 26, 200917 yr I had a disk fail causing unraid to not be able to mount any of my disks. Being in a "panic", lack of experience I must have hit the restore button causing me to update my configuration. Old Configuration: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ parity ata-ST31500341AS_9VS03ZG0 1,465,138,552 - - - - disk1 ata-ST31500341AS_9VS076N7 1,465,137,496 - - - - disk2 ata-ST31500341AS_9VS090S3 1,465,138,552 - - - - disk3 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0725685 976,761,496 - - - - disk4 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ1169028 976,762,552 - - - - Current Configuration: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (blue dot) parity ata-ST31500341AS_9VS03ZG0 30°C 1,465,138,552 - - - - (blue dot) disk1 ata-ST31500341AS_9VS076N7 30°C 1,465,137,496 - - - - (blue dot) disk2 ata-ST31500341AS_9VS090S3 29°C 1,465,138,552 - - - - (blue dot) disk3 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0725685 27°C 976,761,496 - - - - Command area Stopped. Initial configuration ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ So I currently stand at having a missing disk, the parity being somewhat recient and trying to minimize my loss of data. Is there a way to tell unraid about my old configuration, use the partiy to pull the data off the missing disk 4? I can get unraid to boot with the old disk in the system (to rewrite the configuration) but unraid then will not be able to mount any drives due to the bad disk and it thinks I need to regenerate parity. What I "think" I need to happen is this: (1) Write the old config. (2) Force the parity & status of the array to be good. (3) Power down and pull out the bad "disk4" (4) Copy data from parity built disk4 to the good disks. (5) Reset the array to only having disks1 - 3 & rebuild parity. Is this possible or is my data on disk4 lost for good? Thanks for any help anyone can offer. Tim Do not start the array. If you do, and it starts to re-calculate parity, you will lose the data that was on disk4. First question is "Do you know you have a failed disk? or might it be a loose cable to the drive? If it is really defective, that is OK, but if it is good, it might let you proceed differently than if it is bad. The issue we have is even if we force parity to be good, your current confiiguration does not have a disk4. Therefore, we cannot "force" it to be "missing" The only way I know to proceed is to install and assign a new disk4, then... we can press "Restore" once more, then invoke a special command to make it the invalid disk, and last, after that then start the array. As you suspect, at this point, there is no "disk4" in your disk.cfg file. By any chance, do you have a copy of an older version of disk.cfg? If not, please post the contents of the current config/disk.cfg, we would probably be able to guide you into adding a dummy entry representing the missing disk4. As I said, do NOT press "Start" at this time until you respond with some answers. (You might also think of ordering a new replacement drive as you will probably need it at some point. This whole process will be MUCH easier with a replacement disk4 in place. I really don't know if we can invalidate a disk we "fake" Your plan of copying your data will work, but you will be unable to do that until you get back to where unRAID thinks it has a defective disk4 and that parity is good otherwise. So... to sum up. 1. do NOT press Start, 2. Post the current contents of config/disk.cfg 3. Send a email to Tom at lime-technology... try not to panic. His e-mail is: [email protected] 4. Wait for more advice from Tom.
April 26, 200917 yr Author I have not started the array yet. I got to the point where I knew I was in trouble and stopped . (1) I'm pretty sure the disk is bad. It takes BIOS a long time to post when the disk is connected. Removing the disk and the array boots quickly. After I did some googling, I tried a resierfsck of the disk showed no partition (other disks started a long checking process). I swapped it with a disk3's connections and have the same boot issues. There are also some strange sound comming from the disk during boot. (2) I believe this was my old disk.cfg, disk4 should be missing with the new config as I have only ever had a total of 5 disks in the array. The reason I believe this config is right is that after a long boot process, I was able to assign the bad disk back to disk 4. I removed the parity disk from being assigned and tried to start the array (to avoid parity generation and get my data off of that disk). After a long time, the array will not mount any disk and eventually I'm back to the start array button. root@Tower:~# more /boot/config/disk.cfg spindownDelay=30 queueDepth=1 parity=pci-0000:00:11.0-scsi-2:0:0:0 disk1=pci-0000:00:11.0-scsi-0:0:0:0 disk2=pci-0000:00:11.0-scsi-3:0:0:0 disk3=pci-0000:00:11.0-scsi-1:0:0:0 disk4=pci-0000:00:14.1-ide-1:0 diskSpindownDelay.0=-1 diskSpindownDelay.1=30 diskSpindownDelay.2=30 diskSpindownDelay.3=30 diskSpindownDelay.4=0 Thanks for the quick response, I think I'm OK but a bit over my head in how to recover from this and need an expert . I'll email Tom also! Tim
April 26, 200917 yr I have not started the array yet. I got to the point where I knew I was in trouble and stopped . (1) I'm pretty sure the disk is bad. It takes BIOS a long time to post when the disk is connected. Removing the disk and the array boots quickly. After I did some googling, I tried a resierfsck of the disk showed no partition (other disks started a long checking process). I swapped it with a disk3's connections and have the same boot issues. There are also some strange sound comming from the disk during boot. Strange sounds coming from a disk are a pretty good clue it has crashed. (2) I believe this was my old disk.cfg, disk4 should be missing with the new config as I have only ever had a total of 5 disks in the array. The reason I believe this config is right is that after a long boot process, I was able to assign the bad disk back to disk 4. I removed the parity disk from being assigned and tried to start the array (to avoid parity generation and get my data off of that disk). After a long time, the array will not mount any disk and eventually I'm back to the start array button. Good that you un-assigned parity... That made it far less likely to be written to. It appears from your disk.cfg that disk4 is on a different disk controller than your other disks... The "ide" entry is a bit of a surprise, since I did not think that 1TB drives were ever made as IDE. It must be a disk controller masquerading as an IDE controller. Thanks for the quick response, I think I'm OK but a bit over my head in how to recover from this and need an expert . I'll email Tom also! Tim I also know when I'm over my head, that's why I said send Tom an e-mail. As I said, recovery is much easier if you have a working replacement drive in place. You situation is different than many we've helped in the past. Joe L.
April 27, 200917 yr You can not simulate a drive being present without the parity disk. If you can't read the bad drive 4 then unRAID likely got confused and gave up starting. I will ask. Do you want to install a new drive and are you willing to get a new 1T or 1,5T drive before trying to fix this? If so, then order the drive and unplug the box and wait for it to arrive. It should be an easy fix once you get the new drive. If not, I still think you might be able to fix it. You posted you can eventually get the computer to boot and that the drive is recognized. So, I believe you should do the following... but wait until another forum member confirms. 1. Boot the computer and assign the drives like they origionally were. 2. Press the restore button. 3. Login and type the command - mdcmd set invalidslot 99 4. Start the array The array will start with a parity check but that should quickly flag the drive #4 as being bad and take it offline. Een still, stop the parity check ASAP. If the array doesn't look like it is ready to start after using the restore than don't continue. If you see something like unformatted drives then you've got bigger problems. The way to fix it with a new drive is the same steps but use mdcmd set invalidslot 4. That will tell unRAId that disk 4 is bad and it will try to rebuild disk 4 instead or rebuilding parity. In retrospect, this may be the way to do it with the bad disk too. unRAID will attempt to write to disk 4 and fail immediately, dropping back into "simulate" mode for disk4. Once again, wait for a second response confirming this is OK to try before losing data. Peter
April 27, 200917 yr You can not simulate a drive being present without the parity disk. If you can't read the bad drive 4 then unRAID likely got confused and gave up starting. I will ask. Do you want to install a new drive and are you willing to get a new 1T or 1,5T drive before trying to fix this? If so, then order the drive and unplug the box and wait for it to arrive. It should be an easy fix once you get the new drive. If not, I still think you might be able to fix it. You posted you can eventually get the computer to boot and that the drive is recognized. So, I believe you should do the following... but wait until another forum member confirms. 1. Boot the computer and assign the drives like they origionally were. 2. Press the restore button. 3. Login and type the command - mdcmd set invalidslot 99 4. Start the array The array will start with a parity check but that should quickly flag the drive #4 as being bad and take it offline. Een still, stop the parity check ASAP. If the array doesn't look like it is ready to start after using the restore than don't continue. If you see something like unformatted drives then you've got bigger problems. The way to fix it with a new drive is the same steps but use mdcmd set invalidslot 4. That will tell unRAId that disk 4 is bad and it will try to rebuild disk 4 instead or rebuilding parity. In retrospect, this may be the way to do it with the bad disk too. unRAID will attempt to write to disk 4 and fail immediately, dropping back into "simulate" mode for disk4. Once again, wait for a second response confirming this is OK to try before losing data. Peter DO NOT DO THIS! You will lose the ability to recover your data.
April 27, 200917 yr Here is what I recommend. (You'll need a replacement disk >=1T, <= 1.5T) 1. I am unsure if unRAID will start the array automatically after a reboot. In order to ensure that it does not start, I'd recommend replacing your disk.cfg file with a default (empty) disk.cfg file from the unRAID distribution .zip file. 2. Power down and remove the damaged disk and install the new replaceement disk (make sure cabling is secure) 3. Power up the server, the array will not start (if it does, stop it immediatelly) 4. Go to the devices page and reassign all of your disks. You can assign the replacement disk to any slot you like. For purposes of these instructons, I'm assuming it will assigned as disk4. 5. Return to the main page 6. Press the restore button (usually a bad idea, but necessary in your case) Do not start the array. (If your disks all have blue dots, you can skip this step - but wouldn't hurt either way) 7. Open a telnet session, and enter the command ... mdcmd set invalidslot 4 (this tells unRAID that when the array is started, to rebuild disk4 instead of rebuilding parity, which is the default) 8. Go back to the unRAID Web GUI / main tab, and start the array. 9. You should see the write count on disk4 growing, and the read counts on the other disks growing (if you refresh the page a few times) 10. Let it complete. If disk4 does not appear fully recovered, post back for further directions. Good luck!
April 27, 200917 yr One quick question. You said you pressed "Restore" to get yourself into this situation. Since doing so, have you pressed it a second time? If not, then here's something to look for. It might help. When the "restore" button is pressed, the "config/super.dat" file is copied to config/super.old" and a new superblock file created based on the then configured and working drives. If you only pressed the "Restore" button once, then the super.old file might be useful in getting things back the way they were before you pressed "Restore" If you pressed it a second time, then your original contents were again overwritten, and the copy there is not going to help much. You can verify (I think) that disk4 is in the super.old file by typing strings /boot/config/super.old If you see the model and serial number of the defective disk4, odds are it was the file that existed from before you pressed "Restore" To try... With the defective drive installed as disk4. If the config/super.old file exists, and you only pressed "Restore" once, you can probably copy it FIRST to super.ORIG (any name so it does not get overwritten) cp /boot/config/super.old /boot/config/super.ORIG then copy the old super.old file to the current superblock. cp /boot/config/super.dat /boot/config/super.NEW cp /boot/config/super.old /boot/config/super.dat reboot Make sure the config/disk.cfg you showed is in place, with the disk4 entry in place. Then reboot the server. If it comes up with disk4 as defective, you are well on the way to recovery. If it starts a parity check, immediately stop it. (Odds of this are slim... it would only occur if disk4 was working) Again, wait for concurrence from others before actually doing the copy of the old and reboot, but you can report back if the super.old still has the model/serial of your prior configuration. Joe L.
April 27, 200917 yr Author I did press it a second time after I realized the mistake I had caused (I did this after I took my parity disk offline). The current state of the array is: root@Tower:~# ls /boot/config/ Pro.key* go* ident.cfg* passwd* shares/ super.old* disk.cfg* go.bak* network.cfg* share.cfg* smbpasswd* root@Tower:~# root@Tower:~# strings /boot/config/super.old X9TWST31500341AS 9VS076N7 x=TWST31500341AS 9VS090S3? 28:WDC WD10EACS-00ZJB0 WD-WCASJ07256854 root@Tower:~# I can reinstall the disk, after some time (well atleast after my last try), it should boot and I can assign it. I will not be able to mount the array, unraid will spin its wheels at the mounting stage for awhile and then say no drives arre mounted. So, if I out your response together with bjp999's, would this a step towards a solution? (1) reinstall the bad disk, hope it boots, reassign it to disk4. (My origional config) (2) mdcmd set invalidslot 4 (3) powerdown the array (4) remove disk4 and reboot Would unraid then trust my parity disk and assume disk4 was bad? I have no problem ordering a new disk from newegg tomorrow morning, that would be money well spent to get my data back! Tim
April 27, 200917 yr I did press it a second time after I realized the mistake I had caused (I did this after I took my parity disk offline). The current state of the array is: root@Tower:~# ls /boot/config/ Pro.key* go* ident.cfg* passwd* shares/ super.old* disk.cfg* go.bak* network.cfg* share.cfg* smbpasswd* root@Tower:~# root@Tower:~# strings /boot/config/super.old X9TWST31500341AS 9VS076N7 x=TWST31500341AS 9VS090S3? 28:WDC WD10EACS-00ZJB0 WD-WCASJ07256854 root@Tower:~# I can reinstall the disk, after some time (well atleast after my last try), it should boot and I can assign it. I will not be able to mount the array, unraid will spin its wheels at the mounting stage for awhile and then say no drives arre mounted. So, if I out your response together with bjp999's, would this a step towards a solution? (1) reinstall the bad disk, hope it boots, reassign it to disk4. (My origional config) (2) mdcmd set invalidslot 4 (3) powerdown the array (4) remove disk4 and reboot Would unraid then trust my parity disk and assume disk4 was bad? I have no problem ordering a new disk from newegg tomorrow morning, that would be money well spent to get my data back! Tim I would purchase/order the new drive and wait for it to arrive before going forward. Since you do not have a prior super.dat that had your original configuration before all this started, my approach will not work. Best is as bjp999 recommended. Get the new disk, install it as disk4 and proceed as he described. Make sure when re-assigning the disks on the Devices page that you assign the parity drive to the parity slot. The others are not as critical, other than if you assign disk2 to disk3's slot, the data will now be on disk3 instead of disk2. I've had very good luck with both newegg.com and frys.com for disk drives. They both ship very quickly, and prices are competitive. Joe L.
April 27, 200917 yr I would like to add this for other users to prevent those complicated steps in the future : Always make a copy of your usb key. I have one in my PC in a folder called UNRAID. Every time I add something to the key (like packages, unmenu, etc...), I do a copy. Adding a disk (or changing one for onther) also make me do a copy.
April 27, 200917 yr You can not simulate a drive being present without the parity disk. If you can't read the bad drive 4 then unRAID likely got confused and gave up starting. I will ask. Do you want to install a new drive and are you willing to get a new 1T or 1,5T drive before trying to fix this? If so, then order the drive and unplug the box and wait for it to arrive. It should be an easy fix once you get the new drive. If not, I still think you might be able to fix it. You posted you can eventually get the computer to boot and that the drive is recognized. So, I believe you should do the following... but wait until another forum member confirms. 1. Boot the computer and assign the drives like they origionally were. 2. Press the restore button. 3. Login and type the command - mdcmd set invalidslot 99 4. Start the array The array will start with a parity check but that should quickly flag the drive #4 as being bad and take it offline. Een still, stop the parity check ASAP. If the array doesn't look like it is ready to start after using the restore than don't continue. If you see something like unformatted drives then you've got bigger problems. The way to fix it with a new drive is the same steps but use mdcmd set invalidslot 4. That will tell unRAId that disk 4 is bad and it will try to rebuild disk 4 instead or rebuilding parity. In retrospect, this may be the way to do it with the bad disk too. unRAID will attempt to write to disk 4 and fail immediately, dropping back into "simulate" mode for disk4. Once again, wait for a second response confirming this is OK to try before losing data. Peter DO NOT DO THIS! You will lose the ability to recover your data. Why? I can understand that using mdcmd set invalidslot 99 might not work but using mdcmd set invalidslot 4 on the bad drive should not result in data loss. If anything, it should just result in the rebuild failing and unRAID still not running. In the end, a new drive is the safest way to go. Peter
April 27, 200917 yr After you press the "restore" button there is no way to tell unRAID that there should be a disabled disk in the array. If he did the invalidslot 99 procedure without the failed disk in place, a parity check would immediately start and it would update parity like crazy, and in the process the ability to recover the failed disk would be lost. If he were to get the old drive working again and able to assign it to the array, the invalidslot 99 procedure might work. But if the drive is bad, I just wouldn't trust it. Best is to get the new drive and NOT start the array until it is in place.
April 27, 200917 yr I was thinking that unRAID can't actually read the drive so the parity update would fail. But now that I think more, this doesn't seem to be safe to try. I'd think using mdcmd set invalidslot 4 with the bad drive would result in drive 4 being flagged as bad again and then simulated. The command will basically put unRAID into the mode that it is ready to re-build the data onto a new drive to replace a failed drive, except that the replacement drive will be bad when the array is started and a write is attempted. So, if a replacement drive goes bad during a rebuild unRAID should recover from that failure and fall-back to simulating the failed drive again. This is also assuming the drive can be recognized as good long enough to be assigned and long enough to attempt to start the array and attempt to start the rebuild onto the drive. If he did the invalidslot 99 procedure without the failed disk in place, a parity check would immediately start and it would update parity like crazy, and in the process the ability to recover the failed disk would be lost. I never intended the post to mean trying to start without the failed drive. I posted to boot the computer and assign the drives like they origionally were assigned. This means ALL drives. It'd really be nice if there was a command to force the array as good with a drive missing and bad. That would make this problem an easy fix. I guess you could manually edit the config files and put a drive into it. Peter
April 27, 200917 yr I'd think using mdcmd set invalidslot 4 with the bad drive would result in drive 4 being flagged as bad again and then simulated. I'm not so sure drive4 would be flagged as "bad," but instead, flagged as "good" but not valid (requiring rebuild) I'm not comfortable doing this without having a working drive as disk4. Then, we know there is someplace to write the re-constructed data. It is prudent to wait till the new drive arrives in the mail before doing any attempt at restoration. Have I ever mentioned how much I dislike the "Restore" button name or affiliated dangers? (yeah, probably, but not in this thread) Joe L.
April 27, 200917 yr Yes, all drives would be flagged as good and drive 4 also flagged as needing rebuilding. Once the Start button is pressed and unRAID fails to write to drive 4, when it starts the rebuilding attempt, it will then flag drive4 as bad. Yes, it would be an interesting attempt and likely work. I doubt anyone has tried this before. Tom might know... The safe way is to install a good working drive. Where's that dead horse beating icon for the restore button? Peter
April 27, 200917 yr Yes, all drives would be flagged as good and drive 4 also flagged as needing rebuilding. Once the Start button is pressed and unRAID fails to write to drive 4, when it starts the rebuilding attempt, it will then flag drive4 as bad. Yes, it would be an interesting attempt and likely work. I doubt anyone has tried this before. Tom might know... The safe way is to install a good working drive. Where's that dead horse beating icon for the restore button? Peter I really don't know, but I don't want to risk the data. Restore Button reference needed: http://www.nevtron.si/borderline/deadhors.gif
April 27, 200917 yr I'd think using mdcmd set invalidslot 4 with the bad drive would result in drive 4 being flagged as bad again and then simulated. I prefer options that I KNOW will work vs options that I think SHOULD work. If I were a betting man, I'd likely bet this would work as you logicially think it would. But I would not recommend doing it to a person on the verge of losing 1T of data.
April 27, 200917 yr I'd think using mdcmd set invalidslot 4 with the bad drive would result in drive 4 being flagged as bad again and then simulated. I prefer options that I KNOW will work vs options that I think SHOULD work. If I were a betting man, I'd likely bet this would work as you logicially think it would. But I would not recommend doing it to a person on the verge of losing 1T of data. My feelings exactly.
April 28, 200917 yr Author I ordered a 1.5tb drive from newegg, it should arrive sometime tomorrow. Here will be my order of operations: (1) Since the array is powered off, I'll replace disc4 (previously 1tb) with the new 1.5tb (2) At my last powerdown, the array was stopped, so it should not start. I'll go to the disks page and assign the new disk to disk4 (verifying serial numbers of all the drives). (3) Press restore (this time I am sure ) (4) Telnet to "tower" and type "mdcmd set invalidslot 4" (5) Say a quick prayer... (6) Start the array, verifying that disk4 is being written to, if not, stop the process. (7) Verify the restored data ( Post back the results! The most useful feature of this forum is learning from others (mistakes and all)! Thanks for all of your help! You have really reminded me how there are some really great people out there willing to spend some time teaching others with nothing to gain for themselves! Tim
April 28, 200917 yr I'm a little nervous that the array WILL start when you power up. The fact that it was stopped when you power down does not mean that the array will not start on reboot. Go back to my prior post - and follow the instructions to copy a blank disk.cfg to the flash drive (you can put the flash drive in your workstation to do that). It should stop the array from starting by accident. If the array were to start it would IMMEDIATELY start to build parity and make rebuilding your broken disk problematic. Joe L. may have another idea or may be able to say with confidence that the array won't start.
April 29, 200917 yr Author I think things went well. I followed the instructions exactly, including using an empty disk.cfg. After a long rebuild, the new disk is not mounted and shows up as unformatted. I was tempted to reboot but thought I would ask and see if that is a good idea (even then, I have no powerdown button). What would a good next "safe" thing to do? Thanks, Tim ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ parity ata-ST31500341AS_9VS03ZG0 * 1,465,138,552 - 3,827,004 16 0 disk1 ata-ST31500341AS_9VS076N7 * 1,465,137,496 214,392,004 3,824,515 7 0 disk2 ata-ST31500341AS_9VS090S3 * 1,465,138,552 192,363,112 3,824,219 6 0 disk3 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0725685 * 976,761,496 28,920,976 2,563,065 6 0 disk4 ata-ST31500341AS_9VS1G8N7 * 1,465,138,552 Unformatted 44 4,150,754 0 Command area Started Stop will take the array off-line. Unformatted disk(s) present Format will create a file system in all unformatted disks. Parity is valid. Check will start a Parity-Check. (Last checked on 4/29/2009 4:38:13 AM, finding 0 errors.) Spin Up will immediately spin up all disks. Spin Down will immediately spin down all disks. Clear Statistics will immediately clear all disk statistics. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
April 29, 200917 yr Did you verify that it was disk4 that was being written to, and all the other disks that were being read? A screen shot would be in order about now... I would have expected the new disk to now have a file-system and be mounted. Have you tried the "Refresh" button to get an updated status? As an alternative, at the telnet prompt type: mount to get a list of the mounted drives.
April 29, 200917 yr Author Joe L, This is my first time I have ever posted on a forum so hopefully the screenshot is attached . If not, it looks like it read all disks and wrote to disk 4. In summary Disk Size Free Reads Writes Errors parity 1,465,138,552 - 3,827,004 16 0 disk1 1,465,137,496 214,392,004 3,824,515 7 0 disk2 1,465,138,552 192,363,112 3,824,219 6 0 disk3 976,761,496 28,920,976 2,563,065 6 0 disk4 1,465,138,552 Unformatted 44 4,150,754 0 root@Tower:~# mount fusectl on /sys/fs/fuse/connections type fusectl (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sda1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr) shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,allow_other) nfsd on /proc/fs/nfs type nfsd (rw) root@Tower:~#
Archived
This topic is now archived and is closed to further replies.