unRAID Server Release 5.0-beta8d Available

[ix400]

Hi all,

 

I have a severe problem. I switched a 2TB with a 3TB drive, but the rebuild doesn't work properly. I also can't put back the old drive because then unRaid tells me it is not big enough.

 

The 3TB disc has been pre cleared with the script in version 1.12.

 

Rebuild stops somewhere around 2.3 - 2.4TB (estimated).

 

Error log is attached.

 

Please help!!

 

Best wishes,

 

 

Chris

 

Fixed this in -beta9

 

Thank you very much, Tom.

 

I just installed the 9 and started the rebuild. Should be finished in about 14 hours from now.

 

Thanks again, GREAT SUPPORT!!

 

Chris

[aht961]

Upgraded to 5.0b8d. Everything went fine. Today, I stopped the array, after which I could not see the identification data for the disks any more (see image 1_2). Started the array (without knowing the identification of the disks), the array went on-line and I could access my shares. However, could not see the identification data any more (ref. image 1). Through the unMenu, I could see the necessary info, though (image2).

 

How could I get back this info displayed in the GUI?

ps: syslog as well attached.

syslog-2011-07-14.txt

[Joe L.]

Upgraded to 5.0b8d. Everything went fine. Today, I stopped the array, after which I could not see the identification data for the disks any more (see image 1_2). Started the array (without knowing the identification of the disks), the array went on-line and I could access my shares. However, could not see the identification data any more (ref. image 1). Through the unMenu, I could see the necessary info, though (image2).

 

How could I get back this info displayed in the GUI?

ps: syslog as well attached.

easy... do not use the plugin to change the appearance until AFTER it is modified to catch up with the latest beta.

[aht961]

Thank you Joe. Unfortunately, I cannot work it out, however. I used to install the new GUI by using this statement (/boot/webGui/install.sh) in my go script. I removed it, rebooted, still have the new GUI and the mentioned problem. Even removed the webGui folder in my boot disk. Still boots to the new GUI and no identication data for my disks. When I try to check the identification data for each disk from the drop-down menu, I have only two options: the first one is an empty item, the second being: "no disk". The empty item is ticked, so I don't change any thing and start the array and it goes online. But I have got no chances to check whether the correct disks are assigned to correct slots.

 

What's next?

[gerhard911]

unRAID newbie so please be patient. Built my server on 5.0beta7 because I was starting with some Hitachi 3TB drives (1 parity + 1 data + 1 WD2TB data). I have since updated to 5.0beta8d but have had problems expanding the array on both versions.

 

After successful testing and data population in the 3 drive configuration I am now trying to add two more 3TB drives to my server (unRAID Pro license). Both drives were factory fresh and are physically installed (/dev/hde and /dev/hdf). I ran preclear_disk on hdf (took 52 hours).

 

On the Main tab of the WebGUI both drives show up and selecting hde it shows as unformatted while the precleared hdf shows GPT: 4K-aligned. Both have file system type = unknown.

 

Selecting just the "raw" hde drive and checking the "Yes I want to do this" box then pressing "Start" does not start the array. The disk status indicator for the new drive remains blue (the original 3 disks are green) and the Array status is red and "Stopped found 1 new disk". Looking at the disk settings it still shows Partition format and File system type as "unknown". The server's disk activity light does not indicate any disk activity. Running preclear_disk.sh -l at the server console does not show any of the 4 disks now supposedly assigned to the array as available, only hdf.

 

If I attempt to add the precleared hdf instead, the Firefox WebGUI session hangs with "Transferring data from Tower..." Attempts to start a new session with //tower also hang (Firefox or IE) Running preclear_disk.sh -l at the server console now shows both hde & hdf as available.

 

Is my expansion procedure correct or am I missing something ?

 

Just a comment, but I would not be surprised if IDE support (including pseudo-IDE support) is not being well maintained in current Linux kernels, in particular, keeping up with features needed for the larger-than-2GB drives.  The fact that your drives are assigned hde and hdf instead of sde and sdf (or the appropriate sd? symbols) tells me that you are using pseudo-IDE support.  Enter your BIOS settings and change the SATA drive support to be a native SATA support choice, such as AHCI.

 

Just a reminder, including a syslog is very important for troubleshooting.

 

Good call ! The default BIOS setting on those two disks was PATA to support booting from CD. I switched to AHCI and tried adding the precleared disk (now sde). The WebGUI session still hung like before but the disk activity light indicated something was going on. Looking at the syslog I found a message that clearing had started on the disk. Since I had used 1.11 of preclear instead of 1.12 my 3TB disk was not properly identified as cleared and ready.

 

Thanks for the help !

[prostuff1]

Thank you Joe. Unfortunately, I cannot work it out, however. I used to install the new GUI by using this statement (/boot/webGui/install.sh) in my go script. I removed it, rebooted, still have the new GUI and the mentioned problem. Even removed the webGui folder in my boot disk. Still boots to the new GUI and no identication data for my disks. When I try to check the identification data for each disk from the drop-down menu, I have only two options: the first one is an empty item, the second being: "no disk". The empty item is ticked, so I don't change any thing and start the array and it goes online. But I have got no chances to check whether the correct disks are assigned to correct slots.

 

What's next?

 

Your web browser is caching the page.  hold SHIFT and hit the refresh button in your browser a couple of times.

[aht961]

prostuff1: I did clear the cache & history, cookies etc. (Safari and Firefox) - did not help. Is this new GUI implemented as a default in the new version? I just cannot get rid of it so I could try with the default Limetech web page.

[Joe L.]

prostuff1: I did clear the cache & history, cookies etc. (Safari and Firefox) - did not help. Is this new GUI implemented as a default in the new version? I just cannot get rid of it so I could try with the default Limetech web page.

no, it is not.

[optim]

During data rebuild system is using on-the-fly parity reconstruct to provide data for missing disk.  In your system log, mount is complaining it can't find the superblock for disk13 (or that it's invalid), so that leads me to think parity was not correct before starting this.

 

Well, the data rebuild finished this morning.  The Unformatted status remained and the disk13 was not available for mounting  as it said it was missing the superblock.  I only have options in the GUI to format the drive at this point.

 

But here is the strange thing.  I took down the server and pulled the rebuilt disk13.  Now I am running PhotoRec on the drive to recover any readable data that might be found.  This drive had a number of TV episodes on it in mkv format, and the funny thing is that so far I have been able to recover a number of these episodes from the rebuilt drive.  It is still progressing.

 

So my point is, while the drive is somehow flagged as unformatted/unusable, the data rebuild is restoring data from the parity calcs.

 

I still have my original disk13, and I will probably re-add it and redo the parity drive, but I'm just trying to document whats going on here in case anyone else sees something similar.

 

BTW, I went back and checked my emails (I had unMenu emails enabled), and the parity check had finished around 4:00 AM on the 11th.  Again, that check was done in beta7 and came back with no errors.  I started the drive swap (under beta 8d) around 8:30 AM on the 11th, so it wasn't few days like I said in an earlier email, but actually a few hours.

 

[PeterB]

So my point is, while the drive is somehow flagged as unformatted/unusable, the data rebuild is restoring data from the parity calcs.

 

No, it's not!

 

It's not rebuilding .... unRAID is doing what it's supposed to do - if a single disk is unavailable, then data will be reconstructed, on the fly, from the contents of the parity and all other data drives.  This is fine, but there will be significant reduction in transfer rates while this is happening.  Also, be aware that, in this condition, the array has no further protection available - if a second drive fails, you will lose the data from both your disk13, and any other drive which fails.

[optim]

No, it's not!

 

Actually, I think it is.  Sorry, I prbably didn't explain it well enough.

 

To be clear, I pulled the reconstructed disk13 and examined it on another Windows 7 system using a USB dock.

 

So this is a drive that was originally dd'ed with zeroes, placed into the UnRAID to replace a missing drive, rebuilt, pulled from the system to be placed in another box, and then scanned for data.  There is no parity-on-the-fly recalcs here, as it is outside of the UnRAID environment.  The Windows version of PhotoRec I'm using has pulled a bunch of playable mkv's and jpg coverart.  From a drive that was originally dd'ed!

 

That is my point.  The drive is not mountable, says it needs to be formatted, but somehow parity combined with all the other disks were able to reconstitute at least some of the data.

 

Once again, I understand I'm off the beaten path here, and I'm not looking for any resolution, just observing what I see.  I think it is a good thing that at least the data is getting reconstructed, but I am questioning why the disk is flagged as requiring formatting.  It's likely Tom is correct in that maybe parity was somehow faulty, but I find it curious as the beta7 scan done hours earlier passed with no errors.

 

[limetech]

To be clear, I pulled the reconstructed disk13 and examined it on another Windows 7 system using a USB dock.

 

What did you use to read the contents of the drive under Win7?

[optim]

TestDisk & PhotoRec.

 

Both are free and open source utils.  The Windows version include a minimal (Cygwin?) Linux environment and they can read a bunch of partition types, including volumes spread across RAID stripes.  See the wiki for the full details:  http://www.cgsecurity.org/wiki/TestDisk

 

PhotoRec is bundled in the TestDisk download.  I told it not to look for a specific partition type and it picked out the corrupt ReiserFS partition.

 

So far PhotoRec has picked up 325 mkv's off the volume, and they are are playable.  Unfortunately the names are all generic.  It's just over half way through scanning the volume.

[Superorb]

Will there ever be a way to tell which exact file generates a sync error? This way we can just compare the file on the data disk with the source file. Sometimes it's hard to know if the data on a data disk is bad or if data on the parity disk is bad.

 

The md5deep package can help with this.

 

I remember looking at that, but it is all command line, and I was looking for a GUI solution.

[PeterB]

... it is all command line, and I was looking for a GUI solution.

 

Once upon a time, command line was all we had!

[Superorb]

... it is all command line, and I was looking for a GUI solution.

 

Once upon a time, command line was all we had!

 

Yup, and I do use the CMI for a of stuff, but I was just looking for an easy way out.

[c234rmf]

I had to replace a disk and rebuild.  I am concerned about the 11,985 writes to the parity drive.

Did I hit the rebuild corner case problem?

Shares are disabled and no addon software is in my go file.

unRAID Server Pro version: 4.5.6

Here is the status I am rebuilding drive 3

 

Disk        Size               Free          Reads    Writes      Errors

parity   1,953,514,552          -       61,148  11,985    0

disk1     293,057,320    25,772,184  44,662            6    0

disk2        293,057,320      27,900,564  41,128            9    0

disk3   1,953,514,552 1,587,699,220        79  77,507    0

disk4        488,386,552      28,495,472  51,659            8    0

disk5        732,574,552    183,051,596  52,937            7    0

disk6        732,574,552    291,158,308  53,310            8    0

disk7        976,762,552    753,073,116  54,583            7    0

 

Thanks

 

[stealth82]

I've upgraded from 5.0b7 to 5.0b8, and I can't get to the web interface.  I logged on to the server, and ran the emhttp command by hand and get a segmentation fault.

 

It is on the network, as I can telnet to it.

 

here's what's in the syslog for that

 

Jul  7 19:20:32 Tower emhttp: unRAID System Management Utility version 5.0-beta8
Jul  7 19:20:32 Tower emhttp: Copyright (C) 2005-2011, Lime Technology, LLC
Jul  7 19:20:32 Tower emhttp: Plus key detected, GUID: 0781-5406-0000-060512030038
Jul  7 19:20:32 Tower emhttp: rdevName.22 not found
Jul  7 19:20:33 Tower emhttp: diskFsStatus.1 not found
Jul  7 19:20:33 Tower kernel: emhttp[5598]: segfault at 0 ip b75ac760 sp bfc50c80 error 4 in libc-2.11.1.so[b7533000+15c000]

 

Looks to be a problem with 'Plus' key - I'll fix it ASAP and post -beta8a.

I have the same problem with beta10...

[mav3r1ck]

I've upgraded from 5.0b7 to 5.0b8, and I can't get to the web interface.  I logged on to the server, and ran the emhttp command by hand and get a segmentation fault.

 

It is on the network, as I can telnet to it.

 

here's what's in the syslog for that

 

Jul  7 19:20:32 Tower emhttp: unRAID System Management Utility version 5.0-beta8
Jul  7 19:20:32 Tower emhttp: Copyright (C) 2005-2011, Lime Technology, LLC
Jul  7 19:20:32 Tower emhttp: Plus key detected, GUID: 0781-5406-0000-060512030038
Jul  7 19:20:32 Tower emhttp: rdevName.22 not found
Jul  7 19:20:33 Tower emhttp: diskFsStatus.1 not found
Jul  7 19:20:33 Tower kernel: emhttp[5598]: segfault at 0 ip b75ac760 sp bfc50c80 error 4 in libc-2.11.1.so[b7533000+15c000]

 

Looks to be a problem with 'Plus' key - I'll fix it ASAP and post -beta8a.

 

Hello Tom,

 

I have the same issue running b12a for my PRO key...

 

Sep 11 21:03:19 Goliath emhttp: Copyright © 2005-2011, Lime Technology, LLC

Sep 11 21:03:19 Goliath emhttp: Pro key detected, GUID: 13FE-XXXX-XXXX-XXXXXXXXXXXX

Sep 11 21:03:19 Goliath emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults

Sep 11 21:03:19 Goliath emhttp: rdevName.22 not found

Sep 11 21:03:20 Goliath emhttp: diskFsStatus.1 not found

Sep 11 21:03:20 Goliath kernel: emhttp[13311]: segfault at 0 ip b74a6760 sp bf8961b0 error 4 in libc-2.11.1.so[b742d000+15c000]

 

As you say above  'looks like a problem with the PLUS key'

 

Thanks for your quick response