Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unassigned disk accidently

Featured Replies

Hi ,

 

I accidently unassigned a disk and the parity disk , while trying to do the adv format drive procedure of a WDEARS 2T disk. (parity disk).

 

When I place the jumper on the parity disk , the unraid is starting on the console , but I cannot reach the unraid webpage and the shares are not available.

 

Now I have the following situation :

 

both the parity disk and disk 1 are unassigned in the devices while the array is offline, and are not installed in the main menu.

Disk 1 contains 800 Gb of data I don't want to loose ..

Disk 2 ,3,4 and 5 are active.

 

What can I do to reassigning both drives please ?? So I don't loose my data .

 

Vic

If you reassign Disk1, the array should start (without any protection).  Assuming it does and you again can access all the data, stop the array, assign the parity disk and let it recalculate parity.

 

Or am I misunderstanding your issue?

I think he said he cannot get to the unRAID web-page.  makes it harder to re-assign disk1.

 

I would un-plug the parity drive and see if you can boot to where you can see the web-management page.

 

You are not the first to report an issue with the BIOS / boot sequence locking up after a jumper is added.  

(or, remove the jumper, as a second possibility)

 

 

Whatever you do, do  NOT format any drives...  Keep your fingers off of the "Format" button if it does show itself.

 

Joe L.

  • Author

Hi jazzysmooth ,

I cannot reassign my disk , the disk devices in the devicesmenu are unassigned , whille using the dropdown featureoose a  disk  

Is there a way to reassign Disk1 please ?

 

 

  • Author

Hi Joe L;

 

I have acces to unRAID web-page now.

How can I reassign my disk1 ?

 

Vic

  • Author

Hi Joe ,

I already have removed the jumper

Hi Joe L;

 

I have acces to unRAID web-page now.

How can I reassign my disk1 ?

 

Vic

Stop the array (if started) Go to the "Devices" page and re-assign it.

 

Joe L.

  • Author

Hi Joe

 

That is what I want to do , in the devices page the parity device and disk1 device are unassigned.

When using the dropdown button , I have no choice except unassigned...

 

that is my problem

 

What can I do ?

 

any idea ??

Hi Joe

 

That is what I want to do , in the devices page the parity device and disk1 device are unassigned.

When using the dropdown button , I have no choice except unassigned...

 

that is my problem

 

What can I do ?

 

any idea ??

Now I understand.  That is even easier.  You probably do not have either the power or SATA cable attached to the drive properly.  If the BIOS cannot see the drive, then neither can unRAID.

 

When you boot, do you see the drive in the BIOS? 

 

Joe L.

  • Author

OK , I will check the cables and reboot my unraid  server

 

 

Meanwhile I attached the syslog file , hope it will be usefull ...

syslog-2010-10-07-1.zip

  • Author

I checked the cables , OK , I cannot see all the drives in the Bios , but I am shure they are all alive.

 

In the unraid page  , same problem .

But in the unmenu page I can see in the array management menu that there are 2 drive partitions not protected in the array: my 2 missing drives :

WDC_WD20EARS-00MVWB0_WD-WMAZ20126761 : 2TB parity disk

ST31000528AS_6VP0SYFT : my 1 TB datadisk containing 800 GB data

 

THere is a mount  button :

/dev/sdg1 mounted on /mnt/disk/sdg1

/dev/sdf1 mounted on /mnt/disk/sdf1

 

 

I tried : the second button :  result :

 

/dev/sdf1 mounted on /mnt/disk/sdf1

Using command: mount -r -o noatime,nodiratime -t reiserfs /dev/sdf1 /mnt/disk/sdf1 2>&1

 

mount: /dev/sdf1: can't read superblock

 

 

How can I assign them

OK , I will check the cables and reboot my unraid  server

 

 

Meanwhile I attached the syslog file , hope it will be usefull ...

I do not see it complaining in the syslog about disk1 being missing.

 

Did you press the button labeled as "restore" ???    (I'm hoping not, but I need to know)

 

If after you get the disk1 drive to show up and get it assigned you go back to the main page and it says something like

New Drive against it, DO NOT START THE ARRAY as it will also probably say something about clearing it before bringing it online.  That would clear all your old data from it.   (Not what you want at all)

 

Instead, you must initialize a new disk configuration by pressing the button labeled as "restore" again.  (again I'm assuming you pressed it once already)

Then it will just start the array and completely re-construct parity as if you never had done it before.

 

Joe L.

  • Author

Yes I did press the button labeled as "restore" , but nothing happend.

 

I still saw only 4 of my 6 harddisks.

 

 

Yes I did press the button labeled as "restore" , but nothing happend.

 

I still saw only 4 of my 6 harddisks.

 

 

Pressing the button labeled "restore" immediately sets a new disk configuration based on the currently assigned and working disks.  It does NOTHING to restore data.  It also immediately invalidates parity based on the prior configuration.

 

So, right now, you must first assign the two missing drives.  Now that they show up in the BIOS they should show up in the drop-down list on the "Devices" page.   Do they?

 

If not, reboot.

 

Joe L.

  • Author

Hi,

 

I rebooted my unraid server, but still the same problem:  ???

 

When I stop the array I cannot assign a disk , when prssing the button unassigned , I cannot assing any disk.

But when I use the array management webpage in the unmenu interface I see the following :

Drive Partitions - Not In Protected Array :

WDC_WD20EARS-00MVWB0_WD-WMAZ20126761 22°C    2000.3G    /dev/sdf (that is my parity disk )

ST31000528AS_6VP0SYFT 22°C 1000.2G /dev/sdg (that is my 1TB datadisk )

In this menu I can Mount the sdg disk :

/dev/sdg1 mounted on /mnt/disk/sdg1

Using command: mount -r -o noatime,nodiratime -t reiserfs /dev/sdg1 /mnt/disk/sdg1 2>&1:

I ran a Smart Short test:

Smart Short Test of /dev/sdg will take from several minutes to an hour or more.

 

smartctl -t short -d ata /dev/sdg 2>&1

 

smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen

Home page is http://smartmontools.sourceforge.net/

hare

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===

Sending command: "Execute SMART Short self-test routine immediately in off-line mode".

Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.

Testing has begun.

Please wait 1 minutes for test to complete.

Test will complete after Sat Oct  9 20:02:52 2010

 

Use smartctl -X to abort test.  see log attached

S

I can use the button share/dev/sdg  and I can acces my data !

 

But still i cannot see this disk in the  standard main menu nor assign this disk ....

 

what is happening ???

 

 

 

OK , I will check the cables and reboot my unraid  server

Meanwhile I attached the syslog file , hope it will be usefull ...

 

 

The syslog you atatched

 

(a) has NO disk with serial number 6VP0SYFT in Inventory list. this imply unRAID has no knowledge of its existence.

(b) unRAID complaint disk0 is removed, unRAID detect parity disk is gone.

© unRAID did not complaint disk1 is removed, hence unRAID has NO knowledge there is a disk1.

 

Can you post a latest syslog?

 

Oct  9 19:42:27 Tower emhttp: Device inventory:

Oct  9 19:42:27 Tower emhttp: pci-0000:04:00.0-scsi-0:0:0:0 host0 (sda) ata-ST31000528AS_9VP0ZXXZ

Oct  9 19:42:27 Tower emhttp: pci-0000:04:00.0-scsi-1:0:0:0 host1 (sdb) ata-ST31000528AS_6VP0SNEC

Oct  9 19:42:27 Tower emhttp: pci-0000:04:00.0-scsi-2:0:0:0 host2 (sdc) ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20115579

Oct  9 19:42:27 Tower emhttp: pci-0000:04:00.0-scsi-3:0:0:0 host3 (sde) ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20114009

 

Oct  9 19:42:33 Tower kernel: md: import disk2: [8,0] (sda) ST31000528AS                        9VP0ZXXZ offset: 63 size: 976762552

Oct  9 19:42:33 Tower kernel: md: disk2 new disk

Oct  9 19:42:33 Tower kernel: md: import disk3: [8,16] (sdb) ST31000528AS                      6VP0SNEC offset: 63 size: 976762552

Oct  9 19:42:33 Tower kernel: md: disk3 new disk

Oct  9 19:42:33 Tower kernel: md: import disk4: [8,64] (sde) WDC WD20EARS-00MVWB0    WD-WMAZ20114009 offset: 63 size: 1953514552

Oct  9 19:42:33 Tower kernel: md: disk4 new disk

Oct  9 19:42:33 Tower kernel: md: import disk5: [8,32] (sdc) WDC WD20EARS-00MVWB0    WD-WMAZ20115579 offset: 63 size: 1953514552

Oct  9 19:42:33 Tower kernel: md: disk5 new disk

                   

 

From your syslog, here is what unRAID knows about your disks through probing and they all had been imported into

unRAID domain, i think that is why you can see none available in drop-down menu in Device page because from

unRAID perspective there are none available disk(s) existing.

 

Two things you need to fix first

 

Oct  9 19:40:03 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Oct  9 19:40:03 Tower kernel: ata4.00: port_status 0x20200000

Oct  9 19:40:03 Tower kernel: ata4.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Oct  9 19:40:03 Tower kernel:          res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error)

Oct  9 19:40:03 Tower kernel: ata4.00: status: { DRDY ERR }

Oct  9 19:40:03 Tower kernel: ata4.00: configured for UDMA/133

Oct  9 19:40:03 Tower kernel: ata4: EH complete

Oct  9 19:40:03 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Oct  9 19:40:03 Tower kernel: ata4.00: port_status 0x20200000

Oct  9 19:40:03 Tower kernel: ata4.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Oct  9 19:40:03 Tower kernel:          res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error)

Oct  9 19:40:03 Tower kernel: ata4.00: status: { DRDY ERR }

Oct  9 19:40:03 Tower kernel: ata4.00: configured for UDMA/133

Oct  9 19:40:03 Tower kernel: ata4: EH complete

(a) There are plenty of SATA error on ata4, so for those two missing disks, use different SATA ports/cables/power cables. you need to

    fix all SATA errors until you have a clean system for next steps. Those SATA error might be preventing unRAID to do further probing.

 

Oct  9 19:42:33 Tower kernel: read_file: error 2 opening /boot/config/super.dat

Oct  9 19:42:33 Tower kernel: md: could not read superblock from /boot/config/super.dat

Oct  9 19:42:33 Tower kernel: md: initializing superblock

 

(b) There is always error when unRAID try to check super.dat file on your USB drive. either this drive is broken or file system on this

    USB drive might be corrupted.

 

 

In the mean time, definitely do a memtest

 

 

 

 

 

  • Author

Hi ,

I tested the usb memory stick : no problems found.

Disk 0 and 1 are using the SATA controller of the systemboard

The other 4 disks are using the sata SATA300 TX4, can I connect disk Disk 0 and 1 to SATA300 TX4 without any riscs of loosing data ?

 

How do I run a memory test ??

Do you mean the Ram on the systemboard ?  Testing this ram in the BIOS ??

 

When you boot unRAID it first takes you to a screen where you can select the memory test. 

select the memory test and let it run for several passes. (preferably overnight)

 

 

  • Author

Iran the memory test several times, no problem found.

 

Disk 0 and 1 are using the SATA controller of the systemboard

The other 4 disks are using the sata SATA300 TX4.

Can or may I connect disk Disk 0 and 1 to SATA300 TX4 without any riscs of loosing data ?

So I can  see if these disk ar assignable in the unraid menu when connected to another SATAZ contrl

 

thanks in advance

Can or may I connect disk Disk 0 and 1 to SATA300 TX4 without any riscs of loosing data ?

 

As long as you

 

(a) don't run "initconfig"

(b) don't assign/un-assign ANY disk in Device page.

© don't start RAID system when it has been stopped by unRAID

 

You can connect disk to whatever SATA port, unRAID will stop whole RAID system whenever it detects any discrepancy in configuration.

(a) don't run "initconfig"

 

Don't run initconfig OR press the Restore button (they do the same thing, and both are bad).

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.