Hi, I own F4-210 with latest SW update TOS 4.2.28-2201201720 with 4 hddseach formatted as ext4 single volume (8tb,8tb, 4tb, and 2tb).
I'd like to check and repair the Filesystem and Im refearing to procedure addressed by viewtopic.php?f=79&t=2575&hilit=conventional+repair.
I noticed that after the last update telnet user is not "root" anymore but "admin" so the latest is the telnet I'm using.
I' ve stopped all file services first and then tried to unmount my volume with:
umount /mnt/md0 but i got the following reply: "umount failed: Invalid argument"
Same thing with md1, md2 and md3.
Please advice on how to proceed. Below my blkid output:
/dev/sda1: LABEL="UTOSBOOT-X86-S64" UUID="3a4f3362-b26e-4661-9a77-9185f193e480" TYPE="ext4" PARTLABEL="primary" PARTUUID="43f846d7-a7a5-42d1-b609-cf763d791d00"
/dev/sdb1: LABEL="UTOSDISK-X86-S64" UUID="b0579d70-089d-4773-910d-f0361f9e6e25" TYPE="ext4" PARTLABEL="primary" PARTUUID="0b1f8e79-0cc0-429f-8990-a030fd0db859"
/dev/sdb2: UUID="bfa942a5-71fa-b070-6db2-cb989c0d3127" UUID_SUB="e154a692-99b4-b3e3-eeda-8a22fb115f9e" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="5e6ddd65-5749-44e8-a8c6-da0917278549"
/dev/sdb3: UUID="c79b3fc3-5a24-7cee-08a5-f8cd347b820c" UUID_SUB="413490b2-9d6a-2dfb-de5a-0e76c50ca718" LABEL="TNAS-01573E:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="304e51c8-212d-480b-a055-d2e7d01e354b"
/dev/sdb4: UUID="84818ed6-8897-40bd-a915-cf593fdea79a" UUID_SUB="08f21b1e-3409-c784-b368-e3f376b41924" LABEL="TNAS-01573E:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="f2c68b2f-e565-4550-9984-c40f3065ed49"
/dev/sdc1: LABEL="UTOSDISK-X86-S64" UUID="f6cc8829-75f0-43a0-8e61-9718158afabe" TYPE="ext4" PARTLABEL="primary" PARTUUID="4a06b3db-0647-461f-860d-7b1a0346c79c"
/dev/sdc2: UUID="bfa942a5-71fa-b070-6db2-cb989c0d3127" UUID_SUB="47c83d84-6460-d8ad-d515-446925b514f0" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="3c8ca338-016a-4246-8e8d-92d66ec88433"
/dev/sdc3: UUID="c79b3fc3-5a24-7cee-08a5-f8cd347b820c" UUID_SUB="6a09fe97-a943-ed23-d5c5-3ead89c6de15" LABEL="TNAS-01573E:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="60bcae6c-de37-4eaf-b6f7-732599d3f762"
/dev/sdc4: UUID="caa9236a-2d0b-e1c4-8445-dd112f5e1554" UUID_SUB="2a538783-bd1a-c37e-f212-970ae13191b5" LABEL="TNAS-01573E:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="5996a654-06fb-48cb-937f-986446df6109"
/dev/sdd1: LABEL="UTOSDISK-X86-S64" UUID="46eb79f6-1e53-4f9d-a651-984567638bc1" TYPE="ext4" PARTLABEL="primary" PARTUUID="a1df81e5-5d4f-4d10-8cbf-4c74e61a7bba"
/dev/sdd2: UUID="bfa942a5-71fa-b070-6db2-cb989c0d3127" UUID_SUB="6dc9184d-62d9-1693-fcc2-f42815cdb83e" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="7d6b51f8-2782-4655-a0f9-61a98a1ab2a0"
/dev/sdd3: UUID="c79b3fc3-5a24-7cee-08a5-f8cd347b820c" UUID_SUB="4b879635-0169-a82b-0ce1-6d9846e81da9" LABEL="TNAS-01573E:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="a6476351-e53c-4822-a2d6-cc2ede66fd0a"
/dev/sdd4: UUID="b7c0adf6-330a-0115-8281-381e8af11508" UUID_SUB="110d6512-cddf-20f8-7958-8f57ca81d814" LABEL="TNAS-01573E:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="6317ea16-54ed-4a36-95a2-b0025ec9dbcd"
/dev/sde1: LABEL="appoggio filmtemp" UUID="01D694D7FA88D800" TYPE="ntfs" PARTLABEL="primary" PARTUUID="4071e8ee-b53a-4352-ba5d-a3eec916805b"
/dev/sde2: UUID="bfa942a5-71fa-b070-6db2-cb989c0d3127" UUID_SUB="f0af0758-4a0b-bcd7-0f8a-226b3b23fde5" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="3cc86adc-f095-42e2-b6bf-feb64826ed1b"
/dev/sde3: UUID="c79b3fc3-5a24-7cee-08a5-f8cd347b820c" UUID_SUB="e85886d1-2b7f-2989-470f-9fd55fced620" LABEL="TNAS-01573E:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="9e36a98f-d6b9-4fd1-94a0-81d9abaae018"
/dev/sde4: UUID="df3d9e91-51b3-b845-b614-e2e715c84201" UUID_SUB="451c6b33-6460-c268-f7fc-6ff9d04515f7" LABEL="TNAS-01573E:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="8fe16646-7828-4cab-9549-9ad406b0c368"
/dev/md9: UUID="6affff87-a1ac-4f86-a979-3dd8b1ca0d59" TYPE="ext4"
/dev/md0: UUID="IvZD1h-teQj-8QrG-op30-bmFh-uKaN-L9GPEA" TYPE="LVM2_member"
/dev/md1: UUID="w38S8k-MbeZ-dQc7-WVJX-m5Rz-eI60-66uE1G" TYPE="LVM2_member"
/dev/md2: UUID="fYCoZj-KDgt-zVYH-g29s-VrV1-4127-naRCWn" TYPE="LVM2_member"
/dev/md3: UUID="bZ2BpK-b0o1-jV4C-ggmV-zU9Q-cRay-xAXBDW" TYPE="LVM2_member"
/dev/vg0/lv0: UUID="dbf950ba-f4fc-47de-b816-8939679227c0" TYPE="ext4"
/dev/vg1/lv1: UUID="340a3030-ce87-456e-b7c8-6855b22ddf5e" TYPE="ext4"
/dev/vg2/lv2: UUID="df06fb5d-e6ca-481e-b963-f87d885f6870" TYPE="ext4"
/dev/vg3/lv3: UUID="1c8fd628-c479-4135-acc7-33170de4036f" TYPE="ext4"
/dev/md8: TYPE="swap"
/dev/mapper/vg0-lv0: UUID="dbf950ba-f4fc-47de-b816-8939679227c0" TYPE="ext4"
/dev/mapper/vg2-lv2: UUID="df06fb5d-e6ca-481e-b963-f87d885f6870" TYPE="ext4"
/dev/mapper/vg1-lv1: UUID="340a3030-ce87-456e-b7c8-6855b22ddf5e" TYPE="ext4"
/dev/mapper/vg3-lv3: UUID="1c8fd628-c479-4135-acc7-33170de4036f" TYPE="ext4"
admin@TNAS-01573E:~$
Regards
Issue repairing File system
Re: Issue repairing File system
Hi, my issue was related to the fact that I had to switch to root user with "sudo su".
By doing that I was able to check 3 of the 4 HDD I have.
I sill have isse with one of them the "md1" that i was not able to check. I switched to root didectory with "cd /" and below is what happened:
1) umount /mnt/md1 -> seems ok, no complain.
2) umount /home - > got : "umount: /home: target is busy (In some cases useful info about processes thatuse the device is found by lsof(8) or fuser(1).)"
3) fuser -mk /mnt/md1 -> cick me out of telnet (connection to host lost)
4) fuser -mk /home -> cick me out of telnet (connection to host lost)
5) e2fsck -p /dev/mapper/vg1-lv1 -> I got: "/dev/mapper/vg1-lv1 is mounted. e2fsck: Cannot continue, aborting."
Please advice on how to solve this issue
Thanks
By doing that I was able to check 3 of the 4 HDD I have.
I sill have isse with one of them the "md1" that i was not able to check. I switched to root didectory with "cd /" and below is what happened:
1) umount /mnt/md1 -> seems ok, no complain.
2) umount /home - > got : "umount: /home: target is busy (In some cases useful info about processes thatuse the device is found by lsof(8) or fuser(1).)"
3) fuser -mk /mnt/md1 -> cick me out of telnet (connection to host lost)
4) fuser -mk /home -> cick me out of telnet (connection to host lost)
5) e2fsck -p /dev/mapper/vg1-lv1 -> I got: "/dev/mapper/vg1-lv1 is mounted. e2fsck: Cannot continue, aborting."
Please advice on how to solve this issue
Thanks
Re: Issue repairing File system
Hi! You need to login to the terminal and unmout md1 again.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Issue repairing File system
I have tried that already but I do have always the sama issue.
Logging into the NAs again after I'm kicked off does not help. The described steps results are always the same.
Logging into the NAs again after I'm kicked off does not help. The described steps results are always the same.
Re: Issue repairing File system
Please contact our technical team to solve your problem