Urgent! the volume may be crashed

Questions pertaining to Power settings, Auto Block, Permissions, User Quotas and Email alerts may be posted here.
Forum rules
1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:

https://account.synology.com/support/su ... p?lang=enu



2) To avoid putting users' DiskStation at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them. Our Support team will provide the correct patch for your DiskStation model.
Newbie999
Trainee
Trainee
Posts: 13
Joined: Fri Jun 25, 2010 9:46 pm

Urgent! the volume may be crashed

Unread post by Newbie999 » Fri Jan 07, 2011 11:09 pm

Hi

I really need your advise here.

I logged in with putty. I saw /dev/md2
I entered: umount -f /volume1
And then e2fsck -v -n -f /dev/md2

When I now log in to my server I get this:

"Unable to use this volume. The data in the volume may be crashed.
Please try to backup the data before removing the volume.
When you remove hard disks, please note that at least on system
disk [Disk1, Disk2] should be kept for the system to function normally"

This happend instantly. How do I save my data, and get back to normal?
What did I do wrong?
How do I backup data as the error message suggests?

I have two hard drives using RAID 1. Are both gone?

Please, please advise.


EDIT: When I look in File Browser i see "There is no shared folder available". All files are gone.
EDIT: SMART status is ok, and Disk info under HDD Management still says the correct size

EDIT AGAIN


Argh.... The volume is unmounted. Thats why. I rebooted and my files are back again.
This is the tutorial I read: http://forum.synology.com/wiki/index.ph ... sic_faults

Can someone just confirm that this is normal. PLEASE. I mean the error messages are expected when unmounting.

User avatar
maxxfi
Compiler
Compiler
Posts: 6794
Joined: Sun Dec 27, 2009 12:13 pm
Location: Espoo, Finland

Re: Urgent! the volume may be crashed

Unread post by maxxfi » Sat Jan 08, 2011 9:42 am

Newbie999 wrote:Hi

I really need your advise here.

I logged in with putty. I saw /dev/md2
I entered: umount -f /volume1
And then e2fsck -v -n -f /dev/md2
After what you written above have you e.g. rebooted your NAS?
Because with umount you removed /volume1 from the active filesystems
(so DSM thinks *both disks* are crashed/disappeared)
and with the e2fsck, the option -n means 'don't fix it for real', so issue
is still there, if you wanted to correct something.
What have you done after those three steps?
No longer using Synology NAS, moved to more open source solutions.
DS-106j > DS-210j > DS-411

Newbie999
Trainee
Trainee
Posts: 13
Joined: Fri Jun 25, 2010 9:46 pm

Re: Urgent! the volume may be crashed

Unread post by Newbie999 » Sat Jan 08, 2011 12:18 pm

Hi

I ran the commands as described earlier, and the server started beeping immediately.
I logged in to see if I could turn off the beeping, which I now that can.
Thats when I saw the unpleasent error message and that all files were gone.

I let the process continue to Pass 5 and then rebooted. Everything went back to normal.
After this I have done nothing. That is I have not run 'do fix it for real'.

You are saying that the issue is still there. So, is something wrong or does it seem as expected?
Thanks /

User avatar
maxxfi
Compiler
Compiler
Posts: 6794
Joined: Sun Dec 27, 2009 12:13 pm
Location: Espoo, Finland

Re: Urgent! the volume may be crashed

Unread post by maxxfi » Sat Jan 08, 2011 12:31 pm

If it has been able to mount /volume1 in read-write mode, than it should be ok.
If there was some minor issue, I think it should have been ironed out at reboot
(I'm not 100% positive, but it should run a e2fsck in that phase).
You can also have a look in the logs (primarily /var/log/messages, but also
the others you can access from DSM) if after last reboot some corrective action
have been taken or some warning has been issued.
No longer using Synology NAS, moved to more open source solutions.
DS-106j > DS-210j > DS-411

Newbie999
Trainee
Trainee
Posts: 13
Joined: Fri Jun 25, 2010 9:46 pm

Re: Urgent! the volume may be crashed

Unread post by Newbie999 » Sat Jan 08, 2011 1:14 pm

Hi again

In the DSM i cant see anything interesting after the log "Volume [1] was crashed".
I got permisson denied when trying /var/log/messages, so I ran this instead: tail -n25 /var/log/messages

Please note "correction with 0x03" and "printer_device_open.c:16 bad parameter" and "Failed to upgrade EA".

Here we go:

DiskStation> tail -n25 /var/log/messages
Jan 8 01:03:01 kernel: [ 37.330000] mvCesaInit: sessions=10240, queue=64, pSr am=f0000000
Jan 8 01:03:01 kernel: [ 37.560000] encryptfs using the OCF package.
Jan 8 01:03:01 kernel: [ 38.450000] correction with 0x03
Jan 8 01:03:01 kernel: [ 38.550000] Brand: Synology
Jan 8 01:03:01 kernel: [ 38.550000] Model: DS-210j
Jan 8 01:03:02 kernel: [ 41.610000] md: md2: set sda3 to auto_remap [0]
Jan 8 01:03:02 kernel: [ 41.620000] md: md2: set sdb3 to auto_remap [0]
Jan 8 01:03:11 scemd: scemd.c:119 fan_type=7, raid_type=1, led_type=1, thermal_ type=1, fanctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=1, fan_number=1, ebox_type=1, pis_type=1, rtc_type=2
Jan 8 01:03:11 scemd: modules/fan_speed_adjust_common.c:161 Type: INTERNAL Fan Mode: HIGH (suitable for 3.5'' HD)
Jan 8 01:03:12 scemd: modules/raid_sys_volume_check.c:160 MD0 active disks 2, d esigned disks 2
Jan 8 01:03:12 scemd: modules/raid_sys_volume_check.c:160 MD1 active disks 2, d esigned disks 2
Jan 8 01:03:12 scemd: modules/disk_hibernation.c:94 Force hibernation enable, i dle minutes 20
Jan 8 01:03:13 synoprint: printer_device_open.c:16 bad parameter.
Jan 8 01:03:21 kernel: [ 61.000000] Got empty serial number. Generate serial number from product.
Jan 8 01:03:22 syno_hdd_util: Model:[HD203WI], Firmware:[1AN10003], S/N:[S1UYJ1 RZ501933] in [/dev/sdb] is not ssd
Jan 8 01:03:23 syno_hdd_util: Model:[HD203WI], Firmware:[1AN10003], S/N:[S1UYJ1 RZ501943] in [/dev/sda] is not ssd
Jan 8 01:03:23 synousbdisk: RCClean succeeded
Jan 8 01:03:24 ddnsd: main(ddnsd.c:2692): not enable DDNS, shutdown daemon
Jan 8 01:03:38 synoeaupgrade: synoeaupgrade.c:241 Fail to upgrade EA. No such f ile or directory
Jan 8 01:04:14 afpd[3008]: [afp_config.c:318] DiskStation:AFPServer@* started o n 65280.129:128 (2.0.1)
Jan 8 01:05:20 scemd: scemd.c:307 stop manutild.
Jan 8 11:07:44 scemd: SCEMD: disk 1 wake up from hibernation
Jan 8 11:07:51 scemd: SCEMD: disk 2 wake up from hibernation
Jan 8 12:45:32 scemd: SCEMD: disk 1 wake up from hibernation
Jan 8 12:45:44 scemd: SCEMD: disk 2 wake up from hibernation
DiskStation> tail -n25 /var/log/messages
Jan 8 01:03:01 kernel: [ 37.330000] mvCesaInit: sessions=10240, queue=64, pSram=f0000000
Jan 8 01:03:01 kernel: [ 37.560000] encryptfs using the OCF package.
Jan 8 01:03:01 kernel: [ 38.450000] correction with 0x03
Jan 8 01:03:01 kernel: [ 38.550000] Brand: Synology
Jan 8 01:03:01 kernel: [ 38.550000] Model: DS-210j
Jan 8 01:03:02 kernel: [ 41.610000] md: md2: set sda3 to auto_remap [0]
Jan 8 01:03:02 kernel: [ 41.620000] md: md2: set sdb3 to auto_remap [0]
Jan 8 01:03:11 scemd: scemd.c:119 fan_type=7, raid_type=1, led_type=1, thermal_type=1, fanctrl_type=1, auto_pow eron_type=1, dual_power_type=1, usbcopy_type=1, fan_number=1, ebox_type=1, pis_type=1, rtc_type=2
Jan 8 01:03:11 scemd: modules/fan_speed_adjust_common.c:161 Type: INTERNAL Fan Mode: HIGH (suitable for 3.5'' H D)
Jan 8 01:03:12 scemd: modules/raid_sys_volume_check.c:160 MD0 active disks 2, designed disks 2
Jan 8 01:03:12 scemd: modules/raid_sys_volume_check.c:160 MD1 active disks 2, designed disks 2
Jan 8 01:03:12 scemd: modules/disk_hibernation.c:94 Force hibernation enable, idle minutes 20
Jan 8 01:03:13 synoprint: printer_device_open.c:16 bad parameter.
Jan 8 01:03:21 kernel: [ 61.000000] Got empty serial number. Generate serial number from product.
Jan 8 01:03:22 syno_hdd_util: Model:[HD203WI], Firmware:[1AN10003], S/N:[XXXXXXXXXXXXXX] in [/dev/sdb] is not s sd
Jan 8 01:03:23 syno_hdd_util: Model:[HD203WI], Firmware:[1AN10003], S/N:[YYYYYYYYYYYYYY] in [/dev/sda] is not s sd
Jan 8 01:03:23 synousbdisk: RCClean succeeded
Jan 8 01:03:24 ddnsd: main(ddnsd.c:2692): not enable DDNS, shutdown daemon
Jan 8 01:03:38 synoeaupgrade: synoeaupgrade.c:241 Fail to upgrade EA. No such file or directory
Jan 8 01:04:14 afpd[3008]: [afp_config.c:318] DiskStation:AFPServer@* started on 65280.129:128 (2.0.1)
Jan 8 01:05:20 scemd: scemd.c:307 stop manutild.

Thanks /

User avatar
maxxfi
Compiler
Compiler
Posts: 6794
Joined: Sun Dec 27, 2009 12:13 pm
Location: Espoo, Finland

Re: Urgent! the volume may be crashed

Unread post by maxxfi » Sat Jan 08, 2011 5:03 pm

When you login for this kind of maintenance work, use 'root' account.
That should solve file access problems.
About those 3 messages you reported, they are... kind of ok: I also have the first two,
and the third one maybe it's because the rc script is not correct, but doesn't seem
anything serious to me.

If you don't see any big, loud complains in the logs, it should be all right.
No longer using Synology NAS, moved to more open source solutions.
DS-106j > DS-210j > DS-411

Newbie999
Trainee
Trainee
Posts: 13
Joined: Fri Jun 25, 2010 9:46 pm

Re: Urgent! the volume may be crashed

Unread post by Newbie999 » Sat Jan 08, 2011 9:26 pm

You mean putty? Yes, I do login as root.
Let me ask you, have you run this procedure? Did you get the same error message?
Will this happen every time I run the procedure?
If so, I hope the author of the tutorial updates with information to turn off the beeping and not to worry to much about error logs when the procedure is running.

A lot of questions, but I would like to have control over my systems health.


Thank you very much, I appreciate your help.

User avatar
maxxfi
Compiler
Compiler
Posts: 6794
Joined: Sun Dec 27, 2009 12:13 pm
Location: Espoo, Finland

Re: Urgent! the volume may be crashed

Unread post by maxxfi » Sat Jan 08, 2011 11:46 pm

I may have run that procedure, or a similar sequence of steps in the past,
but I can't remember all the details of what happened.
Having worked as sysadmin I tend to forget how many filesystems I have repaired :lol:

I would say, should that issue re-appear in the future, first, start consulting the logs,
then give it a look as you have done this time, with the 'fake' version of e2fsck just to get
an idea of if/how many errors does it find, then try to the reboot, and see if Synology
system can repair it, and if things don't get solved, then it's time to gets your hand dirty
(or call Synology support :wink: )
No longer using Synology NAS, moved to more open source solutions.
DS-106j > DS-210j > DS-411

Newbie999
Trainee
Trainee
Posts: 13
Joined: Fri Jun 25, 2010 9:46 pm

Re: Urgent! the volume may be crashed

Unread post by Newbie999 » Sun Jan 09, 2011 12:16 am

Hi

I will try the same procedure soon. But this time with proper backup first :D
Yeah, Im gonna ask Synology if they know about this. If I learn something new, I will try to remember to update this thread. Hopefully it will help others.

Thanks for your input.


/

Update as promised:

Synology: "What you have mentioned is normal. When you umount the volume, the UI will stated it as crashed as it can not detect the mount volume1 anymore so assume it is crashed. And then when you do an reboot, the volume was being mount back hence it is back to normal."

I sent my kernel log.

Synology: "The log seems fine, most of the error we normally look for isn't in the log, and although there seems to be some error message, but it is often being ignored, as some are just warning for developer to see and some are just bug message which aren't really an error. If you are concerned, you may do an SMART Extended test once a while.
About the FSCK tutorial, we only wrote this to share with the expert user, and we don't recommend user who may not familiar with the fsck, Raid and Linux to try these with their own, as once if this had damaged the data, we are unable to assist."


Now you know what I know. Non-experienced users should stick to windows :D

Post Reply

Return to “System Management”