Device with N/A capacity

peleroform · 14. April 2016

Dear all,

in my physical disks, is one disk shown as capacity N/A (see picture). It is there sdj.
I tried to wipe it in the GUI as also with in SSH.
I only get the error in GUI:

Code

Error #4000:
exception 'OMVException' with message 'Failed to execute command 'export LANG=C; sgdisk --zap-all '/dev/sdj' 2>&1': Problem opening
/dev/sdj
 for reading! Error is
6
.
Problem opening '
' for writing! Program will now terminate.
Warning! MBR not overwritten! Error is
2
!' in /usr/share/openmediavault/engined/rpc/diskmgmt.inc:313
Stack trace:
#0 [internal function]: OMVRpcServiceDiskMgmt->wipe(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('wipe', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('DiskMgmt', 'wipe', Array, Array, 1)
#4 {main}

Alles anzeigen

in SSH by using fdisk with

Code

fdisk /dev/sdj

I get:
fdisk: unable to open /dev/sdj: No such device or address

The disk is a 1.2GB HDD - dont ask why I use such a small and old one.

Thats the first problem. Than I thought, maybe a disk crash, by opening SMART > Devices I get:

Code

communication failure

That error I also get somethimes when I try to open the filesystems overview.

What can I do? What informations can I give to you?

Thanks for your help

Regards.

subzero79 · 14. April 2016

Dodgy quality disk? is it an old IDE disk or usb what?

where did you get that one, also do you really care 1.2GB?

If fdisk cannot recognize then is pretty much game over

peleroform · 15. April 2016

Thats an old IDE disk, pluged in with USB converter.
In another system the disk will be found.., so a hardware failure would not be reason I think.
The disk is from an other system, where the board broke.
About the reason to use such a small, old, slow disk, just I have my reasons.

subzero79 · 15. April 2016

Zitat von peleroform

In another system the disk will be found.., so a hardware failure would not be reason I think.

What kind of system?

I guess the USB converter might be the issue. What does the lsusb says about the converter?

peleroform · 15. April 2016

its another debian jessie system

Code

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 07cc:0320 Carry Computer Eng., Co., Ltd Mass Storage (UIS        DMC4W)
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 004: ID 4971:1015 SimpleTech
Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 006: ID 2109:2812
Bus 001 Device 007: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 009: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 010: ID 174c:5136 ASMedia Technology Inc.
Bus 001 Device 011: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technolo        gy Corp. JM20329 SATA Bridge
Bus 001 Device 012: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technolo        gy Corp. JM20329 SATA Bridge
Bus 001 Device 013: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 014: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 015: ID 174c:5106 ASMedia Technology Inc. Transcend StoreJet 25M3
Bus 001 Device 016: ID 152d:0551 JMicron Technology Corp. / JMicron USA Technolo        gy Corp.
Bus 001 Device 017: ID 174c:5136 ASMedia Technology Inc.
Bus 001 Device 018: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technolo        gy Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 001 Device 019: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technolo        gy Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 001 Device 020: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technolo        gy Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 001 Device 021: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technolo        gy Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 001 Device 022: ID 13fd:1040 Initio Corporation
Bus 001 Device 023: ID 0d49:7310 Maxtor
Bus 001 Device 024: ID 152d:0551 JMicron Technology Corp. / JMicron USA Technolo        gy Corp.

Alles anzeigen

Dont ask which one it is...
The most of the other disks are using the same sort of converter.

Do you someone have an idea why connection failure is during opening SMART?

subzero79 · 15. April 2016

Zitat von peleroform

Do you someone have an idea why connection failure is during opening SMART?

For that particular disk? or for all the disks?

For that 1.2GB disk IDE? is it mechanical drive? find it hard to believe it can have smart attributes. When did you purchase that jewel? or what model/brand is it? IIRC smart came along maybe around 9-10 years agofor consumer drives.

Anyway when you connect drives through usb the smart attributes fetch need to be called in a special way by smartctl. ATM i cannot recall if you need to change this default or omv recognizes the device as usb adapter and executes the proper command. There was a thread about this a few months ago I'll have to dig it.

subzero79 · 15. April 2016

This is the thread that i was talking about

Unable to detect device type Smartctl: please specify device type with the -d option

omv adds dynamically the smartctl parameter if it detects the disk as usb device.

TRy in cli smartctl if smart attributes appear using the sat flag

peleroform · 15. April 2016

Thanks at first,

The SMART problem is, when I try to open in the WEBGui in SMART the disc tab. After loading a few secondes a Communication failure is the final result. It depends not on the IDE disk we talked about.
Last time I could see the SMART - disc list all discs where found....But know with that failure I can not say. I think the time out in the webgui is to short to handle all discs.... Maybe it is possible to set the timeout time higher?

The 1,2GB disk is a seagte ST31276A if it can SMART I thats not the problem, just why there is N/A in the device list. In another debian jessie system as also win 10 it is found and mounted.

By the way, I forgot to change my footlines, The system is now a AMD Atholon XP 3000+. The ARM system was to slow to handle such amount of disks.

subzero79 · 15. April 2016

Yes. Sometimes if you have too many disks the http server can timeout if it is not fast enough to fetch all the info. You can increase the value through environment variable. Later on I can post the variable name looking at my wiki, or if you want you can look in the forum.

peleroform · 15. April 2016

It would be nice if you can post the what I should do. I looked in the forum but I could not find what you said. Maybe the wrong search words.

Thanks for your help

subzero79 · 16. April 2016

This file

/etc/default/openmediavault

add at the end

OMV_HTTPREQUEST_TIMEOUT=XXX

replace the xxx by time in milliseconds, the default is 60000 (=60s) so i suggest maybe 120s, if it doesn't work increase it to 180s.

save, then /etc/init.d/openmediavault-engined restart

Device with N/A capacity

Jetzt mitmachen!

Tags