TS-1263U-RP after update no disks

[dotinho]

Good morning, I just bought in second hand this NAS TS-1263U-RP, in a very good condition and the seller says it already update to the latest firmware 5.0.1from QNAP.

When I first try setup, to "Smart Installation" was found on the webgui, so I decided to downgrade to 5.0.0 build with the setup now show the "Smart Installation" button, after pressing the button, show "No disks".

After inspect via ssh, all 12 bays do green led when disk is on and disk show in /dev/sd*, but on first setup always show "No disks"

At this point I make a serial cable to reach debug on boot firmware, and I found the disks are recognised as removable drives and no internal drives.

on boot sequence I see this on debug console line:

Code: Select all

ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
ata4.00: ATA-11: ST4000NE001-2MA101, EN01, max UDMA/133
ata4.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
scsi 3:0:0:0: Direct-Access     Seagate  ST4000NE001-2MA1 EN01 PQ: 0 ANSI: 5
ata4.00: set queue depth = 32
sd 3:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
sd 3:0:0:0: [sda] Attached SCSI removable disk

Code: Select all

[~] # /sbin/storage_util  --sys_startup
Detect disk(8, 16)...
ignore non-root enclosure disk(8, 16).
Detect disk(8, 0)...
ignore non-root enclosure disk(8, 0).
dev_count = 0
Detect disk(8, 16)...
ignore non-root enclosure disk(8, 16).
Detect disk(8, 0)...
ignore non-root enclosure disk(8, 0).

I also check this guide and didn't solve, disks are still as removable media.
[garbage url removed]

Is there any file to check like enclosure configuration or external drives vs internal drives?

Thanks.

[dolbyman]

I removed the URL as the forum autocensored it to spam


The disks contain the firmware .. so whatever the seller updated it to, does not matter
Were the disks yours and empty or were they supplied with the system ?

[dotinho]

Hello,
Thank you for the help wit url.

Common SATA Disks, actually the one I'm trying never been used before, I also try with old, already formatted in FAT also try with SSD, all disks behave the same way.

From command line I can mount and unmount without any issue, but on the QNAP OS can't map internal drives, it maps all as removable disks. I believe that's the reason on start installation says "No disks"

I know Synology has a file for map external drives and internal drives. I think QNAP maybe have a configuration file for that function. but I don't know.

I also see many threads with "ignore non-root enclosure disk(8, 16)" but no one says how they solve.

[dolbyman]

Only the initial bootstrap is on the DOM, otherwise that NAS has nothing to save any configs (all is saved on the disks)

Try a firmware recovery

Base firmware
http://eu1.qnap.com/Storage/tsd/fullima ... -1.3.0.img

and Guide
https://www.qnap.com/en/how-to/faq/arti ... -based-nas

[dotinho]

I can't recover on this model. I have also check that.
The only option is via update firmware via qFinder, witch I have done up and down try to find a version that fits my device, but I didn't find any.
Then I realise probably is a configuration gone bad abut enclosure or on the disks bay.

I also cable to access directly on console port, and I think I' out of options. I even ask on Reddit if someone has a nas like mine, able to send the internal flash image so I can compare with mine, but with no success.

And of course I can reflash via ssh because if device get bricked, I cannot ever access to it and his lost.

One curious question, where you get that image? I can't find it earlier and I really search for it.

[dolbyman]

I found it in a German thread about the same topic

https://forum.qnapclub.de/thread/43787- ... post394481

[dotinho]

Thank you.

I'll only compare the files for now.

That's the thing I don't want to do:

Code: Select all

cd /
mkdir usb
mount /dev/sdc1 /usb #(Slash hinter sdc1 entfernen)
cp /usb/dom.img /dev/sdb

Because if breaks, I broke for good.

I see also the newer models let access bios by console, but I also have try without success, probably console is only initiated by kernel and not by motherboard itself.

[dolbyman]

At this point I would ask the seller for a refund

If you have no warranty to have QNAP handle it and do not want to risk bricking the unit yourself, your options are VERY limited.

[dotinho]

I agree with you, I already ask for a refund that has been refused, and that's why I'm here.

Meanwhile I'll keep you posted.

Thank you for the support.