Hallo,
ich habe eine DS918+ mit 4x10TB im SHR
jetzt ist das einzige Volume 1 abgestürzt, alle Platten sind aber OK laut SMART und Iron Wolf
Ticket habe ich erstellt und in der Zwischenzeit das gefunden:
--------------------------------------------------------------------------------------------------------------------------------
Re: Filesystem check with DSM5
Quote
Unread post by gonzalu » Sat Jan 06, 2018 3:33 pm
mipial wrote:
DuncanDonovan wrote:
Just for people who cannot complete
CODE: SELECT ALL
syno_poweroff_task -d
because they get a TERMINATED message:
Perhaps you could not log in directly to FTP with root and you tried to login with admin first and then sudo sh to become root. If you do that, you have to to a...
CODE: SELECT ALL
cd /
...first before you do:
CODE: SELECT ALL
sudo sh
Otherwise your home directory of the user admin is on /volume_1 and this prevents syno_poweroff_task -d from successfully finishing. If you first change to / syno_poweroff_task -d will complete successfully.
THIS! I have been struggling with /dev/vg1000/lv "in use" for hours, till I started away from it.
Then it was only a matter of:
CODE: SELECT ALL
login as: admin
admin@servidor's password:
admin@Servidor:~$ cd /
admin@Servidor:/$ sudo sh
Password:
sh-4.3# syno_poweroff_task -d
sh-4.3# vgchange -ay
1 logical volume(s) in volume group "vg1000" now active
sh-4.3# fsck.ext4 -pvf -C 0 /dev/vg1000/lv
And it has just finished running fsck, after 15-20 minutes, and repaired the errors.
Just wanted to say thanks to this post and to everyone for contributing to the cause. FSCK finally running on fix mode for me...
Synology tech support actually said for me to offload my 40TB to some other place, wipe clean and start fresh... If they had a LOANER program I would LOVE to do that but I am limited by the minimum $2500 expense of buying another array just to back it up. I realize this is the RIGHT way to do it but today it is still prohibitively expensive to do so.
-------------------------------------------------------------------------------------------------------------------------------------------------------
leider kommt bei mir folgende Fehlermeldung:
1 logical volume(s) in volume group "vg1000" now active
sh-4.3# fsck.ext4 -pvf -C 0 /dev/vg1000/lv
fsck.ext4: Bad magic number in super-block while trying to open /dev/vg1000/lv
/dev/vg1000/lv:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Jemand ne Idee?
ich habe eine DS918+ mit 4x10TB im SHR
jetzt ist das einzige Volume 1 abgestürzt, alle Platten sind aber OK laut SMART und Iron Wolf
Ticket habe ich erstellt und in der Zwischenzeit das gefunden:
--------------------------------------------------------------------------------------------------------------------------------
Re: Filesystem check with DSM5
Quote
Unread post by gonzalu » Sat Jan 06, 2018 3:33 pm
mipial wrote:
DuncanDonovan wrote:
Just for people who cannot complete
CODE: SELECT ALL
syno_poweroff_task -d
because they get a TERMINATED message:
Perhaps you could not log in directly to FTP with root and you tried to login with admin first and then sudo sh to become root. If you do that, you have to to a...
CODE: SELECT ALL
cd /
...first before you do:
CODE: SELECT ALL
sudo sh
Otherwise your home directory of the user admin is on /volume_1 and this prevents syno_poweroff_task -d from successfully finishing. If you first change to / syno_poweroff_task -d will complete successfully.
THIS! I have been struggling with /dev/vg1000/lv "in use" for hours, till I started away from it.
Then it was only a matter of:
CODE: SELECT ALL
login as: admin
admin@servidor's password:
admin@Servidor:~$ cd /
admin@Servidor:/$ sudo sh
Password:
sh-4.3# syno_poweroff_task -d
sh-4.3# vgchange -ay
1 logical volume(s) in volume group "vg1000" now active
sh-4.3# fsck.ext4 -pvf -C 0 /dev/vg1000/lv
And it has just finished running fsck, after 15-20 minutes, and repaired the errors.
Just wanted to say thanks to this post and to everyone for contributing to the cause. FSCK finally running on fix mode for me...
Synology tech support actually said for me to offload my 40TB to some other place, wipe clean and start fresh... If they had a LOANER program I would LOVE to do that but I am limited by the minimum $2500 expense of buying another array just to back it up. I realize this is the RIGHT way to do it but today it is still prohibitively expensive to do so.
-------------------------------------------------------------------------------------------------------------------------------------------------------
leider kommt bei mir folgende Fehlermeldung:
1 logical volume(s) in volume group "vg1000" now active
sh-4.3# fsck.ext4 -pvf -C 0 /dev/vg1000/lv
fsck.ext4: Bad magic number in super-block while trying to open /dev/vg1000/lv
/dev/vg1000/lv:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Jemand ne Idee?
