QNAP NAS Community Forum

Thisisnotmyname wrote: ↑Fri Jan 11, 2019 12:14 am I don't know what all specifically you previously did, I guess it's possible you don't have a filesystem anymore. What does...

blkid /dev/md0

give you? is there an ext[2|3|4] type on that device? If there's an ext filesystem there then I guess I'd fsck it...

fsck /dev/md0

Hi Thisisnotmyname,

If I enter/run:

blkid /dev/md0

The result is... nothing / nada / zilch... ? All it does is send me back to the beginning: " [~] # "

Was I supposed to run something else first, after launching putty and connecting to the QNAP, before your commands (above) ?

What did you mean by: "...is there an ext[2|3|4] type on that device?" ?

Thanks again very much!

CaptainCanuck

I don’t think this old unit will be running LVM.

CaptainCanuck wrote: ↑Fri Jan 11, 2019 7:39 am

Thisisnotmyname wrote: ↑Fri Jan 11, 2019 12:14 am I don't know what all specifically you previously did, I guess it's possible you don't have a filesystem anymore. What does...

blkid /dev/md0

give you? is there an ext[2|3|4] type on that device? If there's an ext filesystem there then I guess I'd fsck it...

fsck /dev/md0

Hi Thisisnotmyname,

If I enter/run:

blkid /dev/md0

The result is... nothing / nada / zilch... ? All it does is send me back to the beginning: " [~] # "

Was I supposed to run something else first, after launching putty and connecting to the QNAP, before your commands (above) ?

What did you mean by: "...is there an ext[2|3|4] type on that device?" ?

Thanks again very much!

CaptainCanuck

what happens if you run blkid without any arguments?

OneCD wrote: ↑Fri Jan 11, 2019 7:47 am I don’t think this old unit will be running LVM.

really? how old is this thing?

These were announced about 10 years ago: https://hothardware.com/news/qnap-bring ... nterprises

OneCD wrote: ↑Fri Jan 11, 2019 7:47 am I don’t think this old unit will be running LVM.

Hi OneCD,

I could not tell you if it was running LVM... that's Greek to me!

Any way for me to know, which may be hard since this isn't working right now and I don't know what LVM is!

Thanks, cheers!

CaptainCanuck

OneCD wrote: ↑Fri Jan 11, 2019 8:11 am These were announced about 10 years ago: https://hothardware.com/news/qnap-bring ... nterprises

Oh Oh... now you're "dating" me... yes I am a relic and a noob at the same time!

My head is not firmly up my a@s, but I am definitely lost in the woods when it comes to this stuff! lol Good at following directions, buuuut... no real idea what I'm doing.

Thanks, cheers!

CaptainCanuck

what did blkid without any arguments return?

Thisisnotmyname wrote: ↑Fri Jan 11, 2019 10:03 am what did blkid without any arguments return?

Hi Thisisnotmyname,

When entering:
blkid

The results were:

/dev/sdx1: UUID="d020c7e7-6fa6-40e5-9a12-1f336ba99cd6" TYPE="ext2"
/dev/sdx2: UUID="f5cc1847-b1e7-4f92-baa0-6476310118d5" TYPE="ext2"
/dev/sdx3: UUID="50533813-c010-4300-914a-43e754681583" TYPE="ext2"
/dev/sdx5: UUID="0e0741ff-97bf-45e6-8120-a044674364cb" TYPE="ext2"
/dev/sdx6: UUID="500939d8-97aa-4761-a659-3913c6e927ff" TYPE="ext2"
/dev/sdd1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdd2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdd4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdc1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdc2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdc4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdb1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdb2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdb3: UUID="4e3f2593-07db-4688-8c96-7afef8c7761e" TYPE="ext4"
/dev/sdb4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sda1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sda2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sda3: UUID="4e3f2593-07db-4688-8c96-7afef8c7761e" EXT_JOURNAL="00007800-000 0-0000-0000-000000005e3c" TYPE="ext4"
/dev/sdareal4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdh1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdh2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdh4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdg1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdg2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdg3: UUID="4e3f2593-07db-4688-8c96-7afef8c7761e" TYPE="ext4"
/dev/sdg4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdf1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdf2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdf4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sde1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sde2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sde4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/md9: UUID="0f43f648-6da6-45c8-9b7b-d49a86c92da8" TYPE="ext3"
/dev/sda4: UUID="e2a497fb-a267-4671-93c8-f2e7523be7ac" TYPE="ext3"
/dev/md8: UUID="f1fb7dd7-6efb-4001-952a-d5f42d89303d" TYPE="swap"

Is that helpful?

Question: When running blkid, should it return the same results each time it's ran ?
------------When I ran it a second time, the results appear different... as seen here:
/dev/sdx1: UUID="d020c7e7-6fa6-40e5-9a12-1f336ba99cd6" TYPE="ext2"
/dev/sdx2: UUID="f5cc1847-b1e7-4f92-baa0-6476310118d5" TYPE="ext2"
/dev/sdx3: UUID="50533813-c010-4300-914a-43e754681583" TYPE="ext2"
/dev/sdx5: UUID="0e0741ff-97bf-45e6-8120-a044674364cb" TYPE="ext2"
/dev/sdx6: UUID="500939d8-97aa-4761-a659-3913c6e927ff" TYPE="ext2"
/dev/sdd1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdd2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdd4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdc1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdc2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdc4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdb1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdb2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdb3: UUID="4e3f2593-07db-4688-8c96-7afef8c7761e" TYPE="ext4"
/dev/sdb4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sda1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sda2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sda3: UUID="4e3f2593-07db-4688-8c96-7afef8c7761e" EXT_JOURNAL="00007800-0000-0000-0000-000000005e3c" TYPE="ext4"
/dev/sdareal4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdh1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdh2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdh4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdg1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdg2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdg3: UUID="4e3f2593-07db-4688-8c96-7afef8c7761e" TYPE="ext4"
/dev/sdg4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sdf1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sdf2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sdf4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/sde1: UUID="5ebea00e-7ffd-d970-b3c0-36f1f5cfdce5" TYPE="mdraid"
/dev/sde2: UUID="4b757026-4e54-1e57-ca0d-c15ffae9225a" TYPE="mdraid"
/dev/sde4: UUID="98b89c41-f806-57ec-b6e3-050a0708f1a4" TYPE="mdraid"
/dev/md9: UUID="0f43f648-6da6-45c8-9b7b-d49a86c92da8" TYPE="ext3"
/dev/sda4: UUID="e2a497fb-a267-4671-93c8-f2e7523be7ac" TYPE="ext3"
/dev/md8: TYPE="swap" UUID="f1fb7dd7-6efb-4001-952a-d5f42d89303d"

Again many thanks for sticking with me through this! Cheers!

CaptainCanuck

No idea what is going on here. Not really sure what you did previously.

I guess cat1 models have no LVM relaunch

RAID is active but volume is not mounted which means problem is in filesystem.

You could try this:

/etc/init.d/services.sh stop
/etc/init.d/opentftp.sh stop
/etc/init.d/Qthttpd.sh stop
umount /dev/md0
e2fsck -f -v -C 0 /dev/md0
mount /dev/md0
reboot

TS-809 is a CAT1 with no LVM!

The P3R rule of thumb:
All model numbers ending with a 9 (TS-XX9) was a CAT1 at release. Only TS-X69 (low-end Intel) and TS-X79 (high-end Intel) was later upgraded to CAT2 with new firmware but of course needed a reinitialization to use LVM.

Remember though that those TS-XX9-models weren't the only CAT1 models. We also have the TS-X10, TS-X12 and the really, really old TS-X01.

storageman wrote: ↑Fri Jan 11, 2019 4:41 pm No idea what is going on here. Not really sure what you did previously.

I guess cat1 models have no LVM relaunch

RAID is active but volume is not mounted which means problem is in filesystem.

You could try this:

/etc/init.d/services.sh stop
/etc/init.d/opentftp.sh stop
/etc/init.d/Qthttpd.sh stop
umount /dev/md0
e2fsck -f -v -C 0 /dev/md0
mount /dev/md0
reboot

yep, time for fsck, if that doesn't work I think you've trashed your array.

storageman wrote: ↑Fri Jan 11, 2019 4:41 pm No idea what is going on here. Not really sure what you did previously.

Hi Storageman,

In my haste (stupidity), I quickly read some forum posts for a fix when the volume just randomly unmounted itself. I did the following trying to get it back up and mounted:
viewtopic.php?t=79123
and then this:
viewtopic.php?p=224731
... I did both of the above before my brain kicked in and I asked for help here in the forums.

Not sure if the above added to the mess of the random unmounting of the volume... thereby confusing the solution?...
--The QNAP was running along fine as always and then "BEEP"... it suddenly went into unmount status

storageman wrote: ↑Fri Jan 11, 2019 4:41 pm I guess cat1 models have no LVM relaunch

RAID is active but volume is not mounted which means problem is in filesystem.

You could try this:

/etc/init.d/services.sh stop
/etc/init.d/opentftp.sh stop
/etc/init.d/Qthttpd.sh stop
umount /dev/md0
e2fsck -f -v -C 0 /dev/md0
mount /dev/md0
reboot

When I run:
/etc/init.d/services.sh stop
/etc/init.d/opentftp.sh stop
/etc/init.d/Qthttpd.sh stop
umount /dev/md0
e2fsck -f -v -C 0 /dev/md0
mount /dev/md0
reboot

I receive this message:

[~] # /etc/init.d/services.sh stop
Default volume not found.
Stop qpkg service: Default volume not found.
.
Stop service: cloud3p.sh vpn_openvpn.sh vpn_pptp.sh ldap_server.sh antivirus.sh iso_mount.sh qbox.sh qsyncman.sh rsyslog.sh snmp lunportman.sh iscsitrgt.sh twonkymedia.sh init_iTune.sh ImRd.sh crond.sh nvrd.sh StartMediaService.sh bt_scheduler.sh btd.sh mysqld.sh recycled.sh Qthttpd.sh atalk.sh nfs ftp.sh smb.sh versiond.sh .
[~] # /etc/init.d/opentftp.sh stop
[~] # /etc/init.d/Qthttpd.sh stop
Shutting down Qthttpd services: OK.
[~] # umount /dev/md0
umount: /dev/md0: not mounted
[~] # e2fsck -f -v -C 0 /dev/md0
e2fsck 1.41.4 (27-Jan-2009)
e2fsck: Invalid argument while trying to open /dev/md0

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>

[~] # mount /dev/md0
mount: can't find /dev/md0 in /etc/fstab or /etc/mtab
[~] # reboot

Soooo... I see what it says, but will wait for direction or confirmation of the correct argument(s) so I don't mess anything up worse!

Many thanks, cheers!

CaptainCanuck

P3R wrote: ↑Fri Jan 11, 2019 5:14 pm TS-809 is a CAT1 with no LVM!

The P3R rule of thumb:
All model numbers ending with a 9 (TS-XX9) was a CAT1 at release. Only TS-X69 (low-end Intel) and TS-X79 (high-end Intel) was later upgraded to CAT2 with new firmware but of course needed a reinitialization to use LVM.

Remember though that those TS-XX9-models weren't the only CAT1 models. We also have the TS-X10, TS-X12 and the really, really old TS-X01.

Hi P3R,

Thank you for the details!

Thanks!

CaptainCanuck

Thisisnotmyname wrote: ↑Fri Jan 11, 2019 10:38 pm

storageman wrote: ↑Fri Jan 11, 2019 4:41 pm No idea what is going on here. Not really sure what you did previously.

I guess cat1 models have no LVM relaunch

RAID is active but volume is not mounted which means problem is in filesystem.

You could try this:

/etc/init.d/services.sh stop
/etc/init.d/opentftp.sh stop
/etc/init.d/Qthttpd.sh stop
umount /dev/md0
e2fsck -f -v -C 0 /dev/md0
mount /dev/md0
reboot

yep, time for fsck, if that doesn't work I think you've trashed your array.

Hi Thisisnotmyname,

Ok, I will wait for confirmation after my post above of the results so I don't mess anything up further!

Many thanks, cheers!

CaptainCanuck