Jump to content
XPEnology Community

HDD Not recognized


underw3b
 Share

Recommended Posts

Hello everyone,

 

I just installed xpenology (version 5) on an old computer and it works fine !

 

The only problem is that i have 2 hdd (one plugin sata the other in IDE) but xpenology only detect one (sata plugin). In the bios, i can see both without any issues. I used to have freenas and it worked fine too with both hdd.

 

Is there anyone who could help me?

 

Thanx you ! :roll:

 

config :

DSM_DS3612xs_4493

NB_x64_5031_DSM_50-4493_Xpenology_nl

Link to comment
Share on other sites

Hmn... To be perfectly honest, I'm not sure what to try next. what does dmesg tell you about the harware? If you are using nanoboot, try gnoboot (could be a driver support issue). If you boot the machine to a ubuntu live cd/usb is the drive recognised?

 

Andrew

Link to comment
Share on other sites

SSH session :

 

DiskStation> dmesg | grep sd

[ 6.087334] sd 3:0:0:0: [sdd] 488397168 512-byte logical blocks: (250 GB/232 GiB)

[ 6.087364] sd 3:0:0:0: [sdd] Write Protect is off

[ 6.087366] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00

[ 6.087379] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, does n't support DPO or FUA

[ 6.105956] sdd: sdd1 sdd2 sdd3 < sdd5 >

[ 6.107508] sd 3:0:0:0: [sdd] Attached SCSI disk

[ 6.188675] sd 3:0:0:0: Attached scsi generic sg0 type 0

[ 6.343833] md: invalid raid superblock magic on sdd5

[ 6.343838] md: sdd5 does not have a valid v0.90 superblock, not importing!

[ 6.343851] md: considering sdd1 ...

[ 6.343856] md: adding sdd1 ...

[ 6.343858] md: sdd2 has different UUID to sdd1

[ 6.343866] md: bind

[ 6.343883] md: running:

[ 6.344206] md: considering sdd2 ...

[ 6.344215] md: adding sdd2 ...

[ 6.344467] md: bind

[ 6.344477] md: running:

[ 14.932720] md: bind

[ 17.872360] sd 4:0:0:0: [sdu] 60532992 512-byte logical blocks: (30.9 GB/28.8 GiB)

[ 17.872846] sd 4:0:0:0: [sdu] Write Protect is off

[ 17.872849] sd 4:0:0:0: [sdu] Mode Sense: 23 00 00 00

[ 17.873348] sd 4:0:0:0: [sdu] No Caching mode page present

[ 17.873350] sd 4:0:0:0: [sdu] Assuming drive cache: write through

[ 17.873641] sd 4:0:0:0: Attached scsi generic sg1 type 0

[ 17.881247] sd 4:0:0:0: [sdu] No Caching mode page present

[ 17.881251] sd 4:0:0:0: [sdu] Assuming drive cache: write through

[ 17.882638] sdu: sdu1

[ 17.889975] sd 4:0:0:0: [sdu] No Caching mode page present

[ 17.889980] sd 4:0:0:0: [sdu] Assuming drive cache: write through

[ 17.889983] sd 4:0:0:0: [sdu] Attached SCSI removable disk

DiskStation> dmesg | grep hd

[ 0.000000] Command line: ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305

[ 0.000000] Kernel command line: ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305

[ 2.124864] forcedeth 0000:00:07.0: highdma pwrctl mgmt lnktim msi desc-v3

Link to comment
Share on other sites

Well, in the administration pannel i only saw the WD disk (232GIB) but i didn't see the MAXTOR disk (250GIB). I don't understand anymore ^^ I'm installing gnoboot now to see.

 

What is the difference between gnoboot and nanoboot ? which one should i take ?

 

Do you think it's because i didn't erase both disk before installation ?

Link to comment
Share on other sites

I tried gnoboot : nothing

 

I tried to format both HDD with gparted in MBR format (msdos) and not GPT : only one HDD is detected in the admin panel

 

455421Sanstitre.png

 

So, i know that both HDD are in the same format and erase before installation but i don't know what to do now.... :???:

Link to comment
Share on other sites

I believe gnoboot has more drivers for internal cards/hardware than nanoboot... at least that used to be the case, but may not be so anymore.

 

I'm not sure exactly what is (not) happening to cause this.

 

Since it worked with both disks and freenas, We can presume that the hardware is ok. This probably also means that the BIOS settings are also ok. This leaves us with a limited number of possibilities:

 

1) the device that your missing disk is on is not supported by nanoboot or gnoboot - getting it to work would mean asking either of the developers to add a driver for your Mobo.

 

2) The partitions left over from the freenas install interfered with the install of the DSM. Try booting to a usb image with DBAN on it and completely zero both disks (this will take a while) I usually don't let DBAN run all the way through when I am trying to get a disk to the "uninitialised" state, it is usually enough to let DBAN run for 5-10 minutes - this does enough damage to the disk boot sectors and partitions that the is for all intents and purposes unformatted. (DBAN is normally used to overwrite all sectors of a disk so that if you give or sell it to someone they cannot recover whatever data you had stored on it) If you only changed the MBR with gparted then the partition table was unchanged, what you need to do is get rid of all the partitions. I use DBAN just because I am lazy (it boots faster than my other image with gparted)

 

Andrew

Link to comment
Share on other sites

Thx for your help jagwaugh.

 

I'm going to download DBAN and erase my disk. It's the last solution i see. Otherwise, i'll give up and i'll try to find another HDD.

 

As you said, it worked fine with freenas (i was in RAID 1) so it's too bad :???: but i find xpenology much better :grin:

 

Thx again !

Link to comment
Share on other sites

You're welcome.

 

In a perverse way it is actually good to have problems at the beginning, as it forces you to go a bit deeper into how the thing works before you start adding all kinds of packages and data to it. Later on, if or when something does go wrong that little bit of knowledge will be useful.

 

Andrew

Link to comment
Share on other sites

 Share

×
×
  • Create New...