Are my Data Lost?

[Peter Wagner]

Hi,
I flashed my DNS-323 with ALT-F 0.1RC3. Before I Used Dlink-Firmware 1.10 with 2 Samsung-Disks (HD103UJ) as JBOD.
After flashing ALT-F I create a User and I can access md1 - but there are no folders with my old data inside.
I get this message in the Status-Board:

Checking md1 finished with status code 4: fsck 1.41.14 (22-Dec-2010)
/dev/md1: The filesystem size (according to the superblock) is 487857856 blocks
The physical size of the device is 487857664 blocks
Either the superblock or the partition table is likely to be corrupt!


/dev/md1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
	(i.e., without -a or -p optio
 

I read this forum and I try:
1 - check function in the web interface -> that's fail.

2 - Force Fix function  in the web interface -> that's fail.


What can I Do to get access to my data ? Any help would be appreciated. Thanks.
See attached the system and kernel log.
Peter

[João Cardoso]

On Wednesday, March 5, 2014 3:28:05 PM UTC, Peter Wagner wrote:

Hi,
I flashed my DNS-323 with ALT-F 0.1RC3. Before I Used Dlink-Firmware 1.10 with 2 Samsung-Disks (HD103UJ) as JBOD.
After flashing ALT-F I create a User and I can access md1

You only did that? Nothing more? Can you please be more explicit on what you have done and in what sequence?

 

- but there are no folders with my old data inside.

As seen from a MS-Win computer or using Setup->Folders?

What does the Status page tell about Filesystems and RAID? A screenshot will be helpful

 

I get this message in the Status-Board:

Checking md1 finished with status code 4: fsck 1.41.14 (22-Dec-2010)
/dev/md1: The filesystem size (according to the superblock) is 487857856 blocks
The physical size of the device is 487857664 blocks
Either the superblock or the partition table is likely to be corrupt!

There is already a topic about this [added: but does not apply straight to your JBOD case]

[Peter Wagner]

Am Mittwoch, 5. März 2014 20:46:48 UTC+1 schrieb João Cardoso:

On Wednesday, March 5, 2014 3:28:05 PM UTC, Peter Wagner wrote:

Hi,
I flashed my DNS-323 with ALT-F 0.1RC3. Before I Used Dlink-Firmware 1.10 with 2 Samsung-Disks (HD103UJ) as JBOD.
After flashing ALT-F I create a User and I can access md1

You only did that? Nothing more? Can you please be more explicit on what you have done and in what sequence?

First I flashed my DNS-323 with the same method used to upgrade the vendor's firmware (according to the "How to install").
After that I got access via to the Status Page and I did the First-Time-Setup. I created a User with the same name and password of my WIN7-Laptop.

 

- but there are no folders with my old data inside.

As seen from a MS-Win computer or using Setup->Folders?

As Seen from my WIN7-Laptop. Using Setup-Folders - there are no folders inside.
 

What does the Status page tell about Filesystems and RAID? A screenshot will be helpful

I'll send you the screenshot of the Status page next day, because I'm not home today.

 

I get this message in the Status-Board:

Checking md1 finished with status code 4: fsck 1.41.14 (22-Dec-2010)
/dev/md1: The filesystem size (according to the superblock) is 487857856 blocks
The physical size of the device is 487857664 blocks
Either the superblock or the partition table is likely to be corrupt!

There is already a topic about this [added: but does not apply straight to your JBOD case]

 

/dev/md1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
	(i.e., without -a or -p optio
 

[Peter Wagner]

Here are the screenshots from Status-Bord and Filesystem. I hope, it will be helpful to solve my problem. Thanks.

[João Cardoso]

On Friday, March 7, 2014 11:58:46 AM UTC, Peter Wagner wrote:

Here are the screenshots from Status-Bord and Filesystem. I hope, it will be helpful to solve my problem. Thanks.

There are two problems

1-You don't see your data

2-There is an fsck error message

1-For the first one, the screenshots shows that the RAID is working and its ext2 filesystem is mounted; you have 720GB free space on a total of 1.8TB.

-When a filesystem is discovered it is made available under /mnt/<device name> or /mnt/<Label name>, in your case /mnt/md1; if you use Setup->Folders you should see /mnt/md1 and you can browse through its sub-folders, where you will hopefully found your data.

This done not means that all available folders will be available as network shares, for that you have to define Samba/smb network shares based on existing folders; that is done under Services->Network->smb Configure. There is a top-posted topic that deals with this. Start doing that, but notice that you can't write nothing to these shares until 2 is solved.

-When you create a user using Setup->Users, a folder owned by only that user is created and a network share defined; the first time that an user is created special Public folders are also created and the corresponding folders created.

But as the filesystem is mounted Read-Only (RO) because of 2, that steps failed and you can't see the user and public folders.

2-The "unable to fix md1" error is more serious. It has also appeared on this forum but in the context of RAID1, and I never found it for JBOD (linear "RAID").

I can only assume that something went wrong when using the D-Link firmware and as it never checked filesystems the issue remained hidden. Alt-F always checks filesystems when they are discovered, and it tries to fix any error automatically; when that is not possible the filesystem is made available in Read-Only mode. Alt-F don't plays with your data!

You did the correct thing (Disk->Filesystems)

1 - "check" function in the web interface -> that's fail.

2 - "Force Fix" function  in the web interface -> that's fail.

But this specific kind of error has to be deal with more care.

You can try the following:

1-Stop all services (System->Utilities->Stop all services)

2-Unmount the filesystem (Disk->Filesystem->"unmount" md1 under "FS Operations")

3-issue the following command, after ssh/telnet the box and logging in as the 'root' user, same passwd as the webUI:

resize2fs -fp /dev/md1 487857664

It might happens that the above command fails saying that you have to do a 'fsck' first, which can't be successfully done because of the device/fs size mismatch. If this happens, please post the output of the following commands, to see if we can find another fix: 

sfdisk -luS /dev/sd?

Notice that in the above "md1" is the device name of your RAID (it could also be called md0) and "487857664" is the device space in 4KB blocks, which is smaller than the one the filesystem was created with (487857856).

Also notice that you should backup your data first.

If you don't feel conformable with this, you can always return to the D-Link firmware, use System->Firmware, download a D-Link firmware file, hit the "SpecialReboot" button, then reboot and repeat again from System->Firmware but now hit the FlashIt button

[Peter Wagner]

Am Freitag, 7. März 2014 16:57:57 UTC+1 schrieb João Cardoso:

On Friday, March 7, 2014 11:58:46 AM UTC, Peter Wagner wrote:

Here are the screenshots from Status-Bord and Filesystem. I hope, it will be helpful to solve my problem. Thanks.

There are two problems

1-You don't see your data

2-There is an fsck error message

1-For the first one, the screenshots shows that the RAID is working and its ext2 filesystem is mounted; you have 720GB free space on a total of 1.8TB.

-When a filesystem is discovered it is made available under /mnt/<device name> or /mnt/<Label name>, in your case /mnt/md1; if you use Setup->Folders you should see /mnt/md1 and you can browse through its sub-folders, where you will hopefully found your data.

Okay, but in md1 are no sub-folders (see screenshot) - on my filesystem are a lot of sub-folders (pictures, music, movies). Is the Raid not working?
 

This done not means that all available folders will be available as network shares, for that you have to define Samba/smb network shares based on existing folders; that is done under Services->Network->smb Configure. There is a top-posted topic that deals with this. Start doing that, but notice that you can't write nothing to these shares until 2 is solved.

-When you create a user using Setup->Users, a folder owned by only that user is created and a network share defined; the first time that an user is created special Public folders are also created and the corresponding folders created.

But as the filesystem is mounted Read-Only (RO) because of 2, that steps failed and you can't see the user and public folders.

2-The "unable to fix md1" error is more serious. It has also appeared on this forum but in the context of RAID1, and I never found it for JBOD (linear "RAID").

I can only assume that something went wrong when using the D-Link firmware and as it never checked filesystems the issue remained hidden. Alt-F always checks filesystems when they are discovered, and it tries to fix any error automatically; when that is not possible the filesystem is made available in Read-Only mode. Alt-F don't plays with your data!

You did the correct thing (Disk->Filesystems)

1 - "check" function in the web interface -> that's fail.

2 - "Force Fix" function  in the web interface -> that's fail.

But this specific kind of error has to be deal with more care.

You can try the following:

1-Stop all services (System->Utilities->Stop all services)

2-Unmount the filesystem (Disk->Filesystem->"unmount" md1 under "FS Operations")

3-issue the following command, after ssh/telnet the box and logging in as the 'root' user, same passwd as the webUI:

resize2fs -fp /dev/md1 487857664

It might happens that the above command fails saying that you have to do a 'fsck' first, which can't be successfully done because of the device/fs size mismatch. If this happens, please post the output of the following commands, to see if we can find another fix: 

sfdisk -luS /dev/sd?

Notice that in the above "md1" is the device name of your RAID (it could also be called md0) and "487857664" is the device space in 4KB blocks, which is smaller than the one the filesystem was created with (487857856).

Also notice that you should backup your data first.

Sorry for this question - I'm a total LINUX-newbie: How could I do this backup? (Yes, I know, I should do this backup before testing new firmware - but I haven't....)
 

If you don't feel conformable with this, you can always return to the D-Link firmware, use System->Firmware, download a D-Link firmware file, hit the "SpecialReboot" button, then reboot and repeat again from System->Firmware but now hit the FlashIt button

I will try to solve "2-There is an fsck error message" with your informations above (give me a few days) and I will post the results - thanks a lot for your help.

[Joao Cardoso]

On Mar 8, 2014 8:33 PM, "Peter Wagner" <strandmoe...@googlemail.com> wrote:
>
>
>
> Am Freitag, 7. März 2014 16:57:57 UTC+1 schrieb João Cardoso:
>>
>>
>>
>> On Friday, March 7, 2014 11:58:46 AM UTC, Peter Wagner wrote:
>>>
>>> Here are the screenshots from Status-Bord and Filesystem. I hope, it will be helpful to solve my problem. Thanks.
>>
>>
>> There are two problems
>> 1-You don't see your data
>> 2-There is an fsck error message
>>
>> 1-For the first one, the screenshots shows that the RAID is working and its ext2 filesystem is mounted; you have 720GB free space on a total of 1.8TB.
>>
>> -When a filesystem is discovered it is made available under /mnt/<device name> or /mnt/<Label name>, in your case /mnt/md1; if you use Setup->Folders you should see /mnt/md1 and you can browse through its sub-folders, where you will hopefully found your data.
>
>
> Okay, but in md1 are no sub-folders (see screenshot) - on my filesystem are a lot of sub-folders (pictures, music, movies). Is the Raid not working?

There is something strange. The md1 filesystem, as shown in the status page, has 1.8TB and 720GB free, meaning that there are 1.1TB of data there. But it does not appears in the Folders Browse, and it should. Does your data folders names have "strange" characters?

Go to services->network->smb configure and add a share based on the /mnt/md1 folder. It should appear in MS-Win.
Is the data there?

The .system folder that appears is reminiscent of the D-Link firmware, and proves that Alt-F has not changed the disk and the raid is working.

Puzzled...

>  
>>
>> This done not means that all available folders will be available as network shares, for that you have to define Samba/smb network shares based on existing folders; that is done under Services->Network->smb Configure. There is a top-posted topic that deals with this. Start doing that, but notice that you can't write nothing to these shares until 2 is solved.
>>
>> -When you create a user using Setup->Users, a folder owned by only that user is created and a network share defined; the first time that an user is created special Public folders are also created and the corresponding folders created.
>> But as the filesystem is mounted Read-Only (RO) because of 2, that steps failed and you can't see the user and public folders.
>>
>> 2-The "unable to fix md1" error is more serious. It has also appeared on this forum but in the context of RAID1, and I never found it for JBOD (linear "RAID").
>> I can only assume that something went wrong when using the D-Link firmware and as it never checked filesystems the issue remained hidden. Alt-F always checks filesystems when they are discovered, and it tries to fix any error automatically; when that is not possible the filesystem is made available in Read-Only mode. Alt-F don't plays with your data!
>>
>> You did the correct thing (Disk->Filesystems)
>>>
>>> 1 - "check" function in the web interface -> that's fail.
>>> 2 - "Force Fix" function  in the web interface -> that's fail.
>>
>>
>> But this specific kind of error has to be deal with more care.
>> You can try the following:
>>
>> 1-Stop all services (System->Utilities->Stop all services)
>> 2-Unmount the filesystem (Disk->Filesystem->"unmount" md1 under "FS Operations")
>> 3-issue the following command, after ssh/telnet the box and logging in as the 'root' user, same passwd as the webUI:
>>
>> resize2fs -fp /dev/md1 487857664
>>
>> It might happens that the above command fails saying that you have to do a 'fsck' first, which can't be successfully done because of the device/fs size mismatch. If this happens, please post the output of the following commands, to see if we can find another fix: 
>>
>> sfdisk -luS /dev/sd?
>>
>> Notice that in the above "md1" is the device name of your RAID (it could also be called md0) and "487857664" is the device space in 4KB blocks, which is smaller than the one the filesystem was created with (487857856).
>>
>> Also notice that you should backup your data first.
>
>
> Sorry for this question - I'm a total LINUX-newbie: How could I do this backup? (Yes, I know, I should do this backup before testing new firmware - but I haven't....)
>  
>>
>> If you don't feel conformable with this, you can always return to the D-Link firmware, use System->Firmware, download a D-Link firmware file, hit the "SpecialReboot" button, then reboot and repeat again from System->Firmware but now hit the FlashIt button
>
>
> I will try to solve "2-There is an fsck error message" with your informations above (give me a few days) and I will post the results - thanks a lot for your help.
>

> --
> You received this message because you are subscribed to the Google Groups "Alt-F" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/36cc28c4-d94f-47d8-8cf3-c8824a1e8669%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

[Peter Wagner]

Go to services->network->smb configure and add a share based on the /mnt/md1 folder. It should appear in MS-Win.

Is the data there?

Yesterday I had time to try your instructions. I created a share based on /mnt/md1 folder, can access the share in MS-Win, but there is no data inside.
(Sorry, but I can't send a sreenshot - I'm at work now.)

Before I try your instructions from march 7 (telnet the box, and "resize 2fs...) you advise me to do a backup - How could I do this backup? (Yes, I know, I should do this backup before testing new firmware - but I haven't....

[João Cardoso]

On Monday, March 17, 2014 1:45:03 PM UTC, Peter Wagner wrote:

Go to services->network->smb configure and add a share based on the /mnt/md1 folder. It should appear in MS-Win.

Is the data there?

Yesterday I had time to try your instructions. I created a share based on /mnt/md1 folder, can access the share in MS-Win, but there is no data inside.
(Sorry, but I can't send a sreenshot - I'm at work now.)

You only see the .systemfile (if Win displays dot files), the same as when you used Browse Folders to /mnt/md1. Your data is not there.

I have analysed the logs and screenshots you posted carefully:

-The JBOD RAID is recognized and started as device /mnt/md1

  As a matter of fact the RAID is assembled, disassembled and reassembled

-A filesystem is recognized in the RAID and an attempt is made to file check it, failing

-The filesystem is mounted as /mnt/md1 in RO (Read-Only) mode to prevent damaging its contents

-The filesystem shows 1.8TB capacity and 720GB free space

-Only a file named .systemfile exists (or is viewable) in the filesystem; that file is typically created by the D-Link firmware

So, everything is following the expected pattern.

The only unexpected fact are your missing files. It is possible that the filesystem "catalog" is damaged at its very beginning, and that fixing it using the "resize2efs" command fixes it, but it is very risky to do it without you having a backup (and yes, the backup should have been done before, can't be done after the damage).

There are several attempts we can do, but it requires hands-on on the system, as it is very time-consuming to give an instruction, wait for the result, try another command... commands such as dumpe2fs/debugfs has to be used to diagnose the problem before trying a fix attempt.

The first attempt I would do is to try to mount (read-only!) the filesystem using an alternative superblock, using

   mount -o ro,sb=NNNN /dev/md1 /mnt/md1

where NNN is obtained from

   dumpe2fs /dev/md1 | grep superblock

e.g.

  Primary superblock at 1, Group descriptors at 2-3

  Backup superblock at 8193, Group descriptors at 8194-8195

  Backup superblock at 24577, Group descriptors at 24578-24579

e.g.

  umount /mnt/md1

  mount  -o ro,sb=8193 /dev/md1 /mnt/md1

  ls /mnt/md1 # does your data appears now? and with other superblock? 

-During the first time wizard, at the Disk Wizard, have you checked any checkbox other than "Don't touch my disks in any way"?

  I don't think you have, or the .systemfile file would not appear

-Have you removed and reinserted the disks between using the D-Link firmware and Alt-F?

  I don't think you have, or the .systemfile file would not appear, but please confirm, and if you have, then try swapping the drives (this is a "desperate" try)

There are several unknown (to me) errors in the logs:

  EXT2-fs (md1): error: ext2_lookup: deleted inode referenced: xxxxxx

And some odd ones: 

   enlarging /dev/sda4 succeeded

   enlarging /dev/sdb4 succeeded

have you tried some similar filesystem operations on md1?

Before I try your instructions from march 7 (telnet the box, and "resize 2fs...)

With the extra information I now have I don't recommend doing that.

I would flash the D-Link firmware (same version you had before) and hope that it ignores the errors and makes you data reappears. But I doubt. Sorry