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.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

(SOLVED) Orange Lights on Tower Main page

focusonthemusic
in General Support (V5 and Older)

Featured Replies

O.k. I have been having drive issues that might be clearing up.

Now I have my array up and I have two disc with orange lights. What does orange mean?

 

Next is if you get a chance to read my prior two drives failed within hours of each other post.

these are the two drives I replaced which have the orange lights. I had to run initconfig for the system to start the array. and yes prior to finding out have already pushed the format button thinking it would bring the drives 100% up by now.

 

???  thanks in advance

  • Quote

    Not doubting your color vision, but would you mind posting a screenshot?  unRAID's orange and red icons look kind of similar but mean very different things...

  • Quote
    • Author

    It's attached, I have had the red lights prior to the array being fixed. Now that the array is started I am getting these lights. before I started the array one of the disc lights was blue the other I can't remember.

     

    I need to make sure the disc drive are not bad. I think the main problem was my Icy Dock bay, Two of the bay area seem to be dead. any drive I put into the last two bay will not be seen. on top of that it knocks of bar area

    2 where it will not recognize the drive also. bad part it's 4 month old, I think that is pass the warranty time line.

     

    Here is a small segment of the syslog:

     

    Mar 24 09:10:12 Tower ifplugd(eth0)[1485]: ifplugd 0.28 initializing.

    Mar 24 09:10:12 Tower ifplugd(eth0)[1485]: Using interface eth0/6C:F0:49:77:09:7E with driver (version: 2.3LK-NAPI)

    Mar 24 09:10:12 Tower ifplugd(eth0)[1485]: Using detection mode: SIOCETHTOOL

    Mar 24 09:10:12 Tower ifplugd(eth0)[1485]: Initialization complete, link beat detected.

    Mar 24 09:10:12 Tower kernel: r8169: eth0: link up

    Mar 24 09:10:12 Tower kernel: r8169: eth0: link up

    Mar 24 09:10:12 Tower ifplugd(eth0)[1485]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

    Mar 24 09:10:12 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 hw ether 6C:F0:49:77:09:7E

    Mar 24 09:10:12 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.1.14 broadcast 192.168.1.255 netmask 255.255.255.0

    Mar 24 09:10:12 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1

    Mar 24 09:10:12 Tower ifplugd(eth0)[1485]: Program executed successfully.

    Mar 24 09:10:12 Tower rpc.statd[1534]: Version 1.1.4 Starting

    Mar 24 09:10:12 Tower emhttp: unRAID System Management Utility version 4.5.6

    Mar 24 09:10:12 Tower emhttp: Copyright © 2005-2010, Lime Technology, LLC

    Mar 24 09:10:12 Tower emhttp: Pro key detected, GUID: 05DC-A761-5GDJ-PPQKXVN13J3V

    Mar 24 09:10:12 Tower emhttp: shcmd (1): udevadm settle

    Mar 24 09:10:12 Tower emhttp: Device inventory:

    Mar 24 09:10:12 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host7 (sdd) WDC_WD20EARS-00MVWB0_WD-WCAZA1227437

    Mar 24 09:10:12 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 host7 (sde) WDC_WD20EARS-00MVWB0_WD-WCAZA1226695

    Mar 24 09:10:12 Tower emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 host8 (sdf) WDC_WD20EARS-00MVWB0_WD-WCAZA1097252

    Mar 24 09:10:12 Tower emhttp: pci-0000:00:1f.5-scsi-1:0:0:0 host10 (sdg) WDC_WD20EARS-00MVWB0_WD-WMAZA2769039

    Mar 24 09:10:12 Tower emhttp: pci-0000:03:00.0-scsi-0:0:0:0 host1 (sda) WDC_WD20EARS-00MVWB0_WD-WCAZA0866229

    Mar 24 09:10:12 Tower emhttp: pci-0000:03:00.0-scsi-1:0:0:0 host2 (sdb) WDC_WD20EARS-00MVWB0_WD-WMAZA3280116

    Mar 24 09:10:12 Tower emhttp: pci-0000:06:00.0-scsi-1:0:0:0 host4 (sdc) WDC_WD5000AAKS-00YGA0_WD-WCAS80645836

    Mar 24 09:10:12 Tower emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger

    Mar 24 09:10:12 Tower emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,48,8,80,8,64,0,0,0,0,8,96,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger

    Mar 24 09:10:12 Tower kernel: xor: automatically using best checksumming function: pIII_sse

    Mar 24 09:10:12 Tower kernel: pIII_sse : 10022.000 MB/sec

    Mar 24 09:10:12 Tower kernel: xor: using function: pIII_sse (10022.000 MB/sec)

    Mar 24 09:10:12 Tower emhttp: Spinning up all drives...

    Mar 24 09:10:12 Tower emhttp: shcmd (4): /usr/sbin/hdparm -S0 /dev/sdc >/dev/null

    Mar 24 09:10:12 Tower kernel: md: unRAID driver 0.95.4 installed

    Mar 24 09:10:12 Tower kernel: md: import disk0: [8,48] (sdd) WDC WD20EARS-00M WD-WCAZA1227437 offset: 63 size: 1953514552

    Mar 24 09:10:12 Tower kernel: md: import disk1: [8,80] (sdf) WDC WD20EARS-00M WD-WCAZA1097252 offset: 63 size: 1953510424

    Mar 24 09:10:12 Tower kernel: md: import disk2: [8,64] (sde) WDC WD20EARS-00M WD-WCAZA1226695 offset: 63 size: 1953514552

    Mar 24 09:10:12 Tower kernel: md: disk3 missing

    Mar 24 09:10:12 Tower kernel: md: disk4 missing

    Mar 24 09:10:12 Tower kernel: md: import disk5: [8,96] (sdg) WDC WD20EARS-00M WD-WMAZA2769039 offset: 63 size: 1953514552

    Mar 24 09:10:12 Tower kernel: mdcmd (2): set md_num_stripes 1280

    Mar 24 09:10:12 Tower kernel: mdcmd (3): set md_write_limit 768

    Mar 24 09:10:12 Tower kernel: mdcmd (4): set md_sync_window 288

    Mar 24 09:10:12 Tower kernel: mdcmd (5): set spinup_group 0 0

    Mar 24 09:10:12 Tower kernel: mdcmd (6): set spinup_group 1 4

    Mar 24 09:10:12 Tower kernel: mdcmd (7): set spinup_group 2 2

    Mar 24 09:10:12 Tower kernel: mdcmd (8): set spinup_group 5 0

    Mar 24 09:10:12 Tower kernel: mdcmd (9): spinup 0

    Mar 24 09:10:12 Tower kernel: mdcmd (10): spinup 1

    Mar 24 09:10:12 Tower kernel: mdcmd (11): spinup 2

    Mar 24 09:10:12 Tower kernel: mdcmd (12): spinup 5

    Mar 24 09:10:12 Tower emhttp: stale configuration

    Mar 24 09:10:12 Tower emhttp: shcmd (5): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

    Mar 24 09:10:12 Tower emhttp: _shcmd: shcmd (5): exit status: 1

    Mar 24 09:10:12 Tower emhttp: shcmd (6): cp /etc/exports- /etc/exports

    Mar 24 09:10:12 Tower emhttp: shcmd (7): killall -HUP smbd

    Mar 24 09:10:12 Tower emhttp: shcmd (8): /etc/rc.d/rc.nfsd restart | logger

    Mar 24 09:10:13 Tower emhttp: shcmd (8): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root

    Mar 24 09:10:13 Tower emhttp: shcmd (9): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root

    Mar 24 09:10:13 Tower emhttp: shcmd (10): echo '0 */1 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root

    Mar 24 09:10:13 Tower emhttp: shcmd (11): crontab /var/spool/cron/crontabs/root

    Mar 24 09:10:20 Tower init: Re-reading inittab

    Mar 24 09:12:11 Tower emhttp: shcmd (13): modprobe -rw md-mod 2>&1 | logger

    Mar 24 09:12:11 Tower kernel: md: unRAID driver removed

    Mar 24 09:12:11 Tower emhttp: shcmd (14): modprobe md-mod super=/boot/config/super.dat slots=8,48,8,80,8,64,8,0,0,0,8,96,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger

    Mar 24 09:12:11 Tower kernel: xor: automatically using best checksumming function: pIII_sse

    Mar 24 09:12:11 Tower kernel: pIII_sse : 10028.400 MB/sec

    Mar 24 09:12:11 Tower kernel: xor: using function: pIII_sse (10028.400 MB/sec)

    Mar 24 09:12:11 Tower kernel: md: unRAID driver 0.95.4 installed

    Mar 24 09:12:11 Tower kernel: md: import disk0: [8,48] (sdd) WDC WD20EARS-00M WD-WCAZA1227437 offset: 63 size: 1953514552

    Mar 24 09:12:11 Tower kernel: md: import disk1: [8,80] (sdf) WDC WD20EARS-00M WD-WCAZA1097252 offset: 63 size: 1953510424

    Mar 24 09:12:11 Tower kernel: md: import disk2: [8,64] (sde) WDC WD20EARS-00M WD-WCAZA1226695 offset: 63 size: 1953514552

    Mar 24 09:12:11 Tower kernel: md: import disk3: [8,0] (sda) WDC WD20EARS-00M WD-WCAZA0866229 offset: 63 size: 1953514552

    Mar 24 09:12:11 Tower kernel: md: disk4 missing

    Mar 24 09:12:11 Tower kernel: md: import disk5: [8,96] (sdg) WDC WD20EARS-00M WD-WMAZA2769039 offset: 63 size: 1953514552

    Mar 24 09:12:11 Tower kernel: mdcmd (2): set md_num_stripes 1280

    Mar 24 09:12:11 Tower kernel: mdcmd (3): set md_write_limit 768

    Mar 24 09:12:11 Tower kernel: mdcmd (4): set md_sync_window 288

    Mar 24 09:12:11 Tower kernel: mdcmd (5): set spinup_group 0 0

    Mar 24 09:12:11 Tower kernel: mdcmd (6): set spinup_group 1 4

    Mar 24 09:12:11 Tower kernel: mdcmd (7): set spinup_group 2 2

    Mar 24 09:12:11 Tower kernel: mdcmd (8): set spinup_group 3 0

    Mar 24 09:12:11 Tower kernel: mdcmd (9): set spinup_group 5 0

    Mar 24 09:12:13 Tower emhttp: shcmd (15): modprobe -rw md-mod 2>&1 | logger

    Mar 24 09:12:13 Tower kernel: md: unRAID driver removed

    Mar 24 09:12:13 Tower emhttp: shcmd (16): modprobe md-mod super=/boot/config/super.dat slots=8,48,8,80,8,64,8,0,8,16,8,96,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger

    Mar 24 09:12:13 Tower kernel: xor: automatically using best checksumming function: pIII_sse

    Mar 24 09:12:13 Tower kernel: pIII_sse : 10058.000 MB/sec

    Mar 24 09:12:13 Tower kernel: xor: using function: pIII_sse (10058.000 MB/sec)

    Mar 24 09:12:13 Tower kernel: md: unRAID driver 0.95.4 installed

    Mar 24 09:12:13 Tower kernel: md: import disk0: [8,48] (sdd) WDC WD20EARS-00M WD-WCAZA1227437 offset: 63 size: 1953514552

    Mar 24 09:12:13 Tower kernel: md: import disk1: [8,80] (sdf) WDC WD20EARS-00M WD-WCAZA1097252 offset: 63 size: 1953510424

    Mar 24 09:12:13 Tower kernel: md: import disk2: [8,64] (sde) WDC WD20EARS-00M WD-WCAZA1226695 offset: 63 size: 1953514552

    Mar 24 09:12:13 Tower kernel: md: import disk3: [8,0] (sda) WDC WD20EARS-00M WD-WCAZA0866229 offset: 63 size: 1953514552

    Mar 24 09:12:13 Tower kernel: md: import disk4: [8,16] (sdb) WDC WD20EARS-00M WD-WMAZA3280116 offset: 63 size: 1953514552

    Mar 24 09:12:13 Tower kernel: md: import disk5: [8,96] (sdg) WDC WD20EARS-00M WD-WMAZA2769039 offset: 63 size: 1953514552

    Mar 24 09:12:13 Tower kernel: mdcmd (2): set md_num_stripes 1280

    Mar 24 09:12:13 Tower kernel: mdcmd (3): set md_write_limit 768

    Mar 24 09:12:13 Tower kernel: mdcmd (4): set md_sync_window 288

    Mar 24 09:12:13 Tower kernel: mdcmd (5): set spinup_group 0 0

    Mar 24 09:12:13 Tower kernel: mdcmd (6): set spinup_group 1 4

    Mar 24 09:12:13 Tower kernel: mdcmd (7): set spinup_group 2 2

    Mar 24 09:12:13 Tower kernel: mdcmd (8): set spinup_group 3 0

    Mar 24 09:12:13 Tower kernel: mdcmd (9): set spinup_group 4 0

    Mar 24 09:12:13 Tower kernel: mdcmd (10): set spinup_group 5 0

    Mar 24 09:12:34 Tower kernel: mdcmd (16): set md_num_stripes 1280

    Mar 24 09:12:34 Tower kernel: mdcmd (17): set md_write_limit 768

    Mar 24 09:12:34 Tower kernel: mdcmd (18): set md_sync_window 288

    Mar 24 09:12:34 Tower kernel: mdcmd (19): set spinup_group 0 0

    Mar 24 09:12:34 Tower kernel: mdcmd (20): set spinup_group 1 4

    Mar 24 09:12:34 Tower kernel: mdcmd (21): set spinup_group 2 2

    Mar 24 09:12:34 Tower kernel: mdcmd (22): set spinup_group 3 0

    Mar 24 09:12:34 Tower kernel: mdcmd (23): set spinup_group 4 0

    Mar 24 09:12:34 Tower kernel: mdcmd (24): set spinup_group 5 0

    Mar 24 09:12:45 Tower kernel: mdcmd (28): set md_num_stripes 1280

    Mar 24 09:12:45 Tower kernel: mdcmd (29): set md_write_limit 768

    Mar 24 09:12:45 Tower kernel: mdcmd (30): set md_sync_window 288

    Mar 24 09:12:45 Tower kernel: mdcmd (31): set spinup_group 0 0

    Mar 24 09:12:45 Tower kernel: mdcmd (32): set spinup_group 1 4

    Mar 24 09:12:45 Tower kernel: mdcmd (33): set spinup_group 2 2

    Mar 24 09:12:45 Tower kernel: mdcmd (34): set spinup_group 3 32

    Mar 24 09:12:45 Tower kernel: mdcmd (35): set spinup_group 4 0

    Mar 24 09:12:45 Tower kernel: mdcmd (36): set spinup_group 5 8

    Mar 24 09:12:53 Tower kernel: mdcmd (40): set md_num_stripes 1280

    Mar 24 09:12:53 Tower kernel: mdcmd (41): set md_write_limit 768

    Mar 24 09:12:53 Tower kernel: mdcmd (42): set md_sync_window 288

    Mar 24 09:12:53 Tower kernel: mdcmd (43): set spinup_group 0 0

    Mar 24 09:12:53 Tower kernel: mdcmd (44): set spinup_group 1 4

    Mar 24 09:12:53 Tower kernel: mdcmd (45): set spinup_group 2 2

    Mar 24 09:12:53 Tower kernel: mdcmd (46): set spinup_group 3 48

    Mar 24 09:12:53 Tower kernel: mdcmd (47): set spinup_group 4 40

    Mar 24 09:12:53 Tower kernel: mdcmd (48): set spinup_group 5 24

    Mar 24 09:12:58 Tower kernel: mdcmd (52): set md_num_stripes 1280

    Mar 24 09:12:58 Tower kernel: mdcmd (53): set md_write_limit 768

    Mar 24 09:12:58 Tower kernel: mdcmd (54): set md_sync_window 288

    Mar 24 09:12:58 Tower kernel: mdcmd (55): set spinup_group 0 0

    Mar 24 09:12:58 Tower kernel: mdcmd (56): set spinup_group 1 4

    Mar 24 09:12:58 Tower kernel: mdcmd (57): set spinup_group 2 2

    Mar 24 09:12:58 Tower kernel: mdcmd (58): set spinup_group 3 48

    Mar 24 09:12:58 Tower kernel: mdcmd (59): set spinup_group 4 40

    Mar 24 09:12:58 Tower kernel: mdcmd (60): set spinup_group 5 24

    Mar 24 09:13:08 Tower kernel: mdcmd (66): start STOPPED

    Mar 24 09:13:08 Tower kernel: unraid: allocating 33720K for 1280 stripes (6 disks)

    Mar 24 09:13:08 Tower kernel: md1: running, size: 1953510424 blocks

    Mar 24 09:13:08 Tower kernel: md2: running, size: 1953514552 blocks

    Mar 24 09:13:08 Tower kernel: md3: running, size: 1953514552 blocks

    Mar 24 09:13:08 Tower kernel: md4: running, size: 1953514552 blocks

    Mar 24 09:13:08 Tower kernel: md5: running, size: 1953514552 blocks

    Mar 24 09:13:08 Tower emhttp: shcmd (17): udevadm settle

    Mar 24 09:13:08 Tower emhttp: shcmd (18): mkdir /mnt/disk1

    Mar 24 09:13:08 Tower emhttp: shcmd (18): mkdir /mnt/cache

    Mar 24 09:13:08 Tower emhttp: shcmd (18): mkdir /mnt/disk4

    Mar 24 09:13:08 Tower emhttp: shcmd (18): mkdir /mnt/disk3

    Mar 24 09:13:08 Tower emhttp: shcmd (18): mkdir /mnt/disk5

    Mar 24 09:13:08 Tower emhttp: shcmd (18): mkdir /mnt/disk2

    Mar 24 09:13:08 Tower emhttp: shcmd (19): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger

    Mar 24 09:13:08 Tower emhttp: shcmd (20): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 2>&1 | logger

    Mar 24 09:13:08 Tower emhttp: shcmd (21): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger

    Mar 24 09:13:08 Tower emhttp: shcmd (22): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4 2>&1 | logger

    Mar 24 09:13:08 Tower emhttp: shcmd (23): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/sdc1 /mnt/cache 2>&1 | logger

    Mar 24 09:13:08 Tower emhttp: shcmd (24): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger

    Mar 24 09:13:08 Tower kernel: mdcmd (68): check

    Mar 24 09:13:08 Tower kernel: md: recovery thread woken up ...

    Mar 24 09:13:08 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md3,

    Mar 24 09:13:08 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md4,

    Mar 24 09:13:08 Tower logger: missing codepage or helper program, or other error

    Mar 24 09:13:08 Tower logger: In some cases useful info is found in syslog - try

    Mar 24 09:13:08 Tower logger: dmesg | tail or so

    Mar 24 09:13:08 Tower logger: missing codepage or helper program, or other error

    Mar 24 09:13:08 Tower logger:

    Mar 24 09:13:08 Tower logger: In some cases useful info is found in syslog - try

    Mar 24 09:13:08 Tower logger: dmesg | tail or so

    Mar 24 09:13:08 Tower logger:

    Mar 24 09:13:08 Tower emhttp: _shcmd: shcmd (24): exit status: 32

    Mar 24 09:13:08 Tower emhttp: disk4 mount error: 32

    Mar 24 09:13:08 Tower emhttp: shcmd (25): rmdir /mnt/disk4

    Mar 24 09:13:08 Tower emhttp: _shcmd: shcmd (25): exit status: 32

    Mar 24 09:13:08 Tower emhttp: disk3 mount error: 32

    Mar 24 09:13:08 Tower emhttp: shcmd (26): rmdir /mnt/disk3

    Mar 24 09:13:08 Tower kernel: REISERFS warning (device md4): sh-2006 read_super_block: bread failed (dev md4, block 2, size 4096)

    Mar 24 09:13:08 Tower kernel: REISERFS warning (device md4): sh-2006 read_super_block: bread failed (dev md4, block 16, size 4096)

    Mar 24 09:13:08 Tower kernel: REISERFS warning (device md4): sh-2021 reiserfs_fill_super: can not find reiserfs on md4

    Mar 24 09:13:08 Tower kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 2, size 4096)

    Mar 24 09:13:08 Tower kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 16, size 4096)

    Mar 24 09:13:08 Tower kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3

    Mar 24 09:13:08 Tower kernel: REISERFS (device sdc1): found reiserfs format "3.6" with standard journal

    Mar 24 09:13:08 Tower kernel: REISERFS (device sdc1): using ordered data mode

    Mar 24 09:13:08 Tower kernel: REISERFS (device sdc1): journal params: device sdc1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Mar 24 09:13:08 Tower kernel: REISERFS (device sdc1): checking transaction log (sdc1)

    Mar 24 09:13:08 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

    Mar 24 09:13:08 Tower kernel: REISERFS (device md2): using ordered data mode

    Mar 24 09:13:08 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal

    Mar 24 09:13:08 Tower kernel: REISERFS (device md5): using ordered data mode

    Mar 24 09:13:08 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal

    Mar 24 09:13:08 Tower kernel: REISERFS (device md1): using ordered data mode

    Mar 24 09:13:08 Tower kernel: REISERFS (device sdc1): Using r5 hash to sort names

    Mar 24 09:13:08 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Mar 24 09:13:08 Tower kernel: REISERFS (device md2): checking transaction log (md2)

    Mar 24 09:13:08 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Mar 24 09:13:08 Tower kernel: REISERFS (device md5): checking transaction log (md5)

    Mar 24 09:13:08 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Mar 24 09:13:08 Tower kernel: REISERFS (device md1): checking transaction log (md1)

    Mar 24 09:13:08 Tower kernel: REISERFS (device md5): Using r5 hash to sort names

    Mar 24 09:13:08 Tower kernel: md: recovery thread has nothing to resync

    Mar 24 09:13:08 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

    Mar 24 09:13:08 Tower kernel: REISERFS (device md1): Using r5 hash to sort names

    Mar 24 09:13:09 Tower emhttp: shcmd (31): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

    Mar 24 09:13:09 Tower emhttp: shcmd (32): cp /etc/exports- /etc/exports

    Mar 24 09:13:09 Tower emhttp: shcmd (33): mkdir /mnt/user

    Mar 24 09:13:09 Tower emhttp: shcmd (34): /usr/local/sbin/shfs /mnt/user -cache 1 -floor 2000000 -o noatime,big_writes,allow_other,default_permissions

    Mar 24 09:13:09 Tower emhttp: shcmd (35): mkdir /mnt/user0

    Mar 24 09:13:09 Tower emhttp: shcmd (36): /usr/local/sbin/shfs /mnt/user0 -cache 0 -o noatime,big_writes,allow_other,default_permissions

    Mar 24 09:13:10 Tower emhttp: get_config_idx: fopen /boot/config/shares/mysql.cfg: No such file or directory - assigning defaults

    Mar 24 09:13:10 Tower emhttp: shcmd (37): killall -HUP smbd

    Mar 24 09:13:10 Tower emhttp: shcmd (38): /etc/rc.d/rc.nfsd restart | logger

    Unmenu_screen_shot.JPG.08971754216588438efef45b90f2ee2f.JPG

  • Quote

    OK, definitely orange.  As the message says, unRAID doesn't recognize the two disk's formatting and claims they are unformatted.  If these disks are new or otherwise empty and that is what you expect, then go ahead and click the 'I'm sure' checkbox and format the disks.  The formatting will take a few minutes, so just walk away for a bit and then come back and refresh the page.

  • Quote

    If the disks have data that you want to recover you'll need to run reiserfsck.

  • Quote
    • Author

    Well, started the format drives, I think it's been to many cycles of trying to get this set up working again.,

     

    My main problem is the Icy Dock Bay # 4 and 5. I think it could have corrupted the drive of getting anything off them. not sure just thinking after trying to run format and the drive still not working. looking at the syslog it looks like it can't find the file system. ?

     

    Mar 24 09:38:28 Tower emhttp: shcmd (4): /usr/sbin/hdparm -S0 /dev/sdc >/dev/null

    Mar 24 09:38:28 Tower kernel: md: unRAID driver 0.95.4 installed

    Mar 24 09:38:28 Tower kernel: md: import disk0: [8,64] (sde) WDC WD20EARS-00M WD-WCAZA1227437 offset: 63 size: 1953514552

    Mar 24 09:38:28 Tower kernel: md: import disk1: [8,96] (sdg) WDC WD20EARS-00M WD-WCAZA1097252 offset: 63 size: 1953510424

    Mar 24 09:38:28 Tower kernel: md: import disk2: [8,80] (sdf) WDC WD20EARS-00M WD-WCAZA1226695 offset: 63 size: 1953514552

    Mar 24 09:38:28 Tower kernel: md: import disk3: [8,0] (sda) WDC WD20EARS-00M WD-WCAZA0866229 offset: 63 size: 1953514552

    Mar 24 09:38:28 Tower kernel: md: import disk4: [8,16] (sdb) WDC WD20EARS-00M WD-WMAZA3280116 offset: 63 size: 1953514552

    Mar 24 09:38:28 Tower kernel: md: import disk5: [8,112] (sdh) WDC WD20EARS-00M WD-WMAZA2769039 offset: 63 size: 1953514552

    Mar 24 09:38:28 Tower kernel: mdcmd (2): set md_num_stripes 1280

    Mar 24 09:38:28 Tower kernel: mdcmd (3): set md_write_limit 768

    Mar 24 09:38:28 Tower kernel: mdcmd (4): set md_sync_window 288

    Mar 24 09:38:28 Tower kernel: mdcmd (5): set spinup_group 0 0

    Mar 24 09:38:28 Tower kernel: mdcmd (6): set spinup_group 1 4

    Mar 24 09:38:28 Tower kernel: mdcmd (7): set spinup_group 2 2

    Mar 24 09:38:28 Tower kernel: mdcmd (8): set spinup_group 3 48

    Mar 24 09:38:28 Tower kernel: mdcmd (9): set spinup_group 4 40

    Mar 24 09:38:28 Tower kernel: mdcmd (10): set spinup_group 5 24

    Mar 24 09:38:28 Tower kernel: mdcmd (11): spinup 0

    Mar 24 09:38:28 Tower kernel: mdcmd (12): spinup 1

    Mar 24 09:38:28 Tower kernel: mdcmd (13): spinup 2

    Mar 24 09:38:28 Tower kernel: mdcmd (14): spinup 3

    Mar 24 09:38:28 Tower kernel: mdcmd (15): spinup 4

    Mar 24 09:38:28 Tower kernel: mdcmd (16): spinup 5

    Mar 24 09:38:28 Tower kernel: mdcmd (18): start STOPPED

    Mar 24 09:38:28 Tower kernel: unraid: allocating 33720K for 1280 stripes (6 disks)

    Mar 24 09:38:28 Tower kernel: md1: running, size: 1953510424 blocks

    Mar 24 09:38:28 Tower kernel: md2: running, size: 1953514552 blocks

    Mar 24 09:38:28 Tower kernel: md3: running, size: 1953514552 blocks

    Mar 24 09:38:28 Tower kernel: md4: running, size: 1953514552 blocks

    Mar 24 09:38:28 Tower kernel: md5: running, size: 1953514552 blocks

    Mar 24 09:38:28 Tower emhttp: shcmd (5): udevadm settle

    Mar 24 09:38:28 Tower emhttp: shcmd (6): mkdir /mnt/disk4

    Mar 24 09:38:28 Tower emhttp: shcmd (6): mkdir /mnt/cache

    Mar 24 09:38:28 Tower emhttp: shcmd (6): mkdir /mnt/disk2

    Mar 24 09:38:28 Tower emhttp: shcmd (6): mkdir /mnt/disk1

    Mar 24 09:38:28 Tower emhttp: shcmd (7): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4 2>&1 | logger

    Mar 24 09:38:28 Tower emhttp: shcmd (8): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger

    Mar 24 09:38:28 Tower emhttp: shcmd (8): mkdir /mnt/disk3

    Mar 24 09:38:28 Tower emhttp: shcmd (8): mkdir /mnt/disk5

    Mar 24 09:38:28 Tower emhttp: shcmd (9): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/sdc1 /mnt/cache 2>&1 | logger

    Mar 24 09:38:28 Tower emhttp: shcmd (10): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger

    Mar 24 09:38:28 Tower kernel: mdcmd (20): check

    Mar 24 09:38:28 Tower kernel: md: recovery thread woken up ...

    Mar 24 09:38:28 Tower emhttp: shcmd (11): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 2>&1 | logger

    Mar 24 09:38:28 Tower emhttp: shcmd (12): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger

    Mar 24 09:38:28 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md4,

    Mar 24 09:38:28 Tower logger: missing codepage or helper program, or other error

    Mar 24 09:38:28 Tower logger: In some cases useful info is found in syslog - try

    Mar 24 09:38:28 Tower logger: dmesg | tail or so

    Mar 24 09:38:28 Tower logger:

    Mar 24 09:38:28 Tower emhttp: _shcmd: shcmd (12): exit status: 32

    Mar 24 09:38:28 Tower emhttp: disk4 mount error: 32

    Mar 24 09:38:28 Tower emhttp: shcmd (13): rmdir /mnt/disk4

    Mar 24 09:38:28 Tower kernel: REISERFS warning (device md4): sh-2006 read_super_block: bread failed (dev md4, block 2, size 4096)

    Mar 24 09:38:28 Tower kernel: REISERFS warning (device md4): sh-2006 read_super_block: bread failed (dev md4, block 16, size 4096)

    Mar 24 09:38:28 Tower kernel: REISERFS warning (device md4): sh-2021 reiserfs_fill_super: can not find reiserfs on md4

    Mar 24 09:38:28 Tower kernel: REISERFS (device sdc1): found reiserfs format "3.6" with standard journal

    Mar 24 09:38:28 Tower kernel: REISERFS (device sdc1): using ordered data mode

    Mar 24 09:38:28 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md3,

    Mar 24 09:38:28 Tower logger: missing codepage or helper program, or other error

    Mar 24 09:38:28 Tower logger: In some cases useful info is found in syslog - try

    Mar 24 09:38:28 Tower logger: dmesg | tail or so

    Mar 24 09:38:28 Tower logger:

    Mar 24 09:38:28 Tower emhttp: _shcmd: shcmd (14): exit status: 32

    Mar 24 09:38:28 Tower emhttp: disk3 mount error: 32

    Mar 24 09:38:28 Tower emhttp: shcmd (15): rmdir /mnt/disk3

    Mar 24 09:38:28 Tower kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 2, size 4096)

    Mar 24 09:38:28 Tower kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 16, size 4096)

    Mar 24 09:38:28 Tower kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3

    Mar 24 09:38:28 Tower kernel: REISERFS (device sdc1): journal params: device sdc1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Mar 24 09:38:28 Tower kernel: REISERFS (device sdc1): checking transaction log (sdc1)

    Mar 24 09:38:28 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal

    Mar 24 09:38:28 Tower kernel: REISERFS (device md1): using ordered data mode

    Mar 24 09:38:28 Tower kernel: REISERFS (device sdc1): Using r5 hash to sort names

    Mar 24 09:38:28 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Mar 24 09:38:28 Tower kernel: REISERFS (device md1): checking transaction log (md1)

    Mar 24 09:38:28 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal

    Mar 24 09:38:28 Tower kernel: REISERFS (device md5): using ordered data mode

    Mar 24 09:38:28 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

    Mar 24 09:38:28 Tower kernel: REISERFS (device md2): using ordered data mode

    Mar 24 09:38:28 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Mar 24 09:38:28 Tower kernel: REISERFS (device md5): checking transaction log (md5)

    Mar 24 09:38:28 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Mar 24 09:38:28 Tower kernel: REISERFS (device md2): checking transaction log (md2)

    Mar 24 09:38:29 Tower kernel: REISERFS (device md5): Using r5 hash to sort names

    Mar 24 09:38:29 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

    Mar 24 09:38:29 Tower kernel: REISERFS (device md1): Using r5 hash to sort names

    Mar 24 09:38:29 Tower kernel: md: recovery thread has nothing to resync

    Mar 24 09:38:29 Tower emhttp: shcmd (20): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

    Mar 24 09:38:29 Tower emhttp: _shcmd: shcmd (20): exit status: 1

    Mar 24 09:38:29 Tower emhttp: shcmd (21): cp /etc/exports- /etc/exports

    Mar 24 09:38:29 Tower emhttp: shcmd (22): mkdir /mnt/user

    Mar 24 09:38:29 Tower emhttp: shcmd (23): /usr/local/sbin/shfs /mnt/user -cache 1 -floor 2000000 -o noatime,big_writes,allow_other,default_permissions

    Mar 24 09:38:29 Tower emhttp: shcmd (24): mkdir /mnt/user0

    Mar 24 09:38:29 Tower emhttp: shcmd (25): /usr/local/sbin/shfs /mnt/user0 -cache 0 -o noatime,big_writes,allow_other,default_permissions

    Mar 24 09:38:29 Tower emhttp: shcmd (26): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root

    Mar 24 09:38:29 Tower emhttp: shcmd (27): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root

    Mar 24 09:38:29 Tower emhttp: shcmd (28): echo '0 */1 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root

    Mar 24 09:38:29 Tower emhttp: shcmd (29): crontab /var/spool/cron/crontabs/root

    Mar 24 09:38:30 Tower emhttp: get_config_idx: fopen /boot/config/shares/mysql.cfg: No such file or directory - assigning defaults

    Mar 24 09:38:30 Tower emhttp: shcmd (30): killall -HUP smbd

    Mar 24 09:38:30 Tower emhttp: shcmd (31): /etc/rc.d/rc.nfsd restart | logger

    Mar 24 09:38:36 Tower init: Re-reading inittab

    Mar 24 09:49:54 Tower emhttp: shcmd (32): mkreiserfs -q /dev/md3 2>&1 | logger

    Mar 24 09:49:54 Tower emhttp: shcmd (32): mkreiserfs -q /dev/md4 2>&1 | logger

    Mar 24 09:49:54 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com)

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com)

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower logger: The problem has occurred looks like a hardware problem. If you have

    Mar 24 09:49:54 Tower logger: bad blocks, we advise you to get a new hard drive, because once you

    Mar 24 09:49:54 Tower logger: get one bad block that the disk drive internals cannot hide from

    Mar 24 09:49:54 Tower logger: your sight,the chances of getting more are generally said to become

    Mar 24 09:49:54 Tower logger: much higher (precise statistics are unknown to us), and this disk

    Mar 24 09:49:54 Tower logger: drive is probably not expensive enough for you to you to risk your

    Mar 24 09:49:54 Tower logger: time and data on it. If you don't want to follow that follow that

    Mar 24 09:49:54 Tower logger: advice then if you have just a few bad blocks, try writing to the

    Mar 24 09:49:54 Tower logger: bad blocks and see if the drive remaps the bad blocks (that means

    Mar 24 09:49:54 Tower logger: it takes a block it has in reserve and allocates it for use for

    Mar 24 09:49:54 Tower logger: of that block number). If it cannot remap the block, use badblock

    Mar 24 09:49:54 Tower logger: option (-B) with reiserfs utils to handle this block correctly.

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower logger: bread: Cannot read the block (0): (Input/output error).

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower logger: The problem has occurred looks like a hardware problem. If you have

    Mar 24 09:49:54 Tower logger: bad blocks, we advise you to get a new hard drive, because once you

    Mar 24 09:49:54 Tower logger: get one bad block that the disk drive internals cannot hide from

    Mar 24 09:49:54 Tower logger: your sight,the chances of getting more are generally said to become

    Mar 24 09:49:54 Tower logger: much higher (precise statistics are unknown to us), and this disk

    Mar 24 09:49:54 Tower logger: drive is probably not expensive enough for you to you to risk your

    Mar 24 09:49:54 Tower logger: time and data on it. If you don't want to follow that follow that

    Mar 24 09:49:54 Tower logger: advice then if you have just a few bad blocks, try writing to the

    Mar 24 09:49:54 Tower logger: bad blocks and see if the drive remaps the bad blocks (that means

    Mar 24 09:49:54 Tower logger: it takes a block it has in reserve and allocates it for use for

    Mar 24 09:49:54 Tower logger: of that block number). If it cannot remap the block, use badblock

    Mar 24 09:49:54 Tower logger: option (-B) with reiserfs utils to handle this block correctly.

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower logger: bread: Cannot read the block (0): (Input/output error).

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 0

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 1

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 2

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 3

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 4

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 5

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 6

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 7

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 8

    Mar 24 09:49:54 Tower kernel: Buffer I/O error on device md4, logical block 9

    Mar 24 09:49:54 Tower emhttp: shcmd (34): mkdir /mnt/disk4

    Mar 24 09:49:54 Tower emhttp: shcmd (35): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4 2>&1 | logger

    Mar 24 09:49:54 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md4,

    Mar 24 09:49:54 Tower logger: missing codepage or helper program, or other error

    Mar 24 09:49:54 Tower logger: In some cases useful info is found in syslog - try

    Mar 24 09:49:54 Tower logger: dmesg | tail or so

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower emhttp: _shcmd: shcmd (35): exit status: 32

    Mar 24 09:49:54 Tower emhttp: disk4 mount error: 32

    Mar 24 09:49:54 Tower emhttp: shcmd (36): rmdir /mnt/disk4

    Mar 24 09:49:54 Tower kernel: REISERFS warning (device md4): sh-2006 read_super_block: bread failed (dev md4, block 2, size 4096)

    Mar 24 09:49:54 Tower kernel: REISERFS warning (device md4): sh-2006 read_super_block: bread failed (dev md4, block 16, size 4096)

    Mar 24 09:49:54 Tower kernel: REISERFS warning (device md4): sh-2021 reiserfs_fill_super: can not find reiserfs on md4

    Mar 24 09:49:54 Tower emhttp: shcmd (37): mkdir /mnt/disk3

    Mar 24 09:49:54 Tower emhttp: shcmd (38): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger

    Mar 24 09:49:54 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md3,

    Mar 24 09:49:54 Tower logger: missing codepage or helper program, or other error

    Mar 24 09:49:54 Tower logger: In some cases useful info is found in syslog - try

    Mar 24 09:49:54 Tower logger: dmesg | tail or so

    Mar 24 09:49:54 Tower logger:

    Mar 24 09:49:54 Tower emhttp: _shcmd: shcmd (38): exit status: 32

    Mar 24 09:49:54 Tower emhttp: disk3 mount error: 32

    Mar 24 09:49:54 Tower emhttp: shcmd (39): rmdir /mnt/disk3

    Mar 24 09:49:54 Tower kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 2, size 4096)

    Mar 24 09:49:54 Tower kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 16, size 4096)

    Mar 24 09:49:54 Tower kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3

    Mar 24 09:49:55 Tower emhttp: shcmd (40): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

    Mar 24 09:49:55 Tower emhttp: shcmd (41): cp /etc/exports- /etc/exports

    Mar 24 09:49:55 Tower emhttp: get_config_idx: fopen /boot/config/shares/mysql.cfg: No such file or directory - assigning defaults

    Mar 24 09:49:55 Tower emhttp: shcmd (42): killall -HUP smbd

    Mar 24 09:49:55 Tower emhttp: shcmd (43): /etc/rc.d/rc.nfsd restart | logger

    Mar 24 09:51:02 Tower login[3890]: invalid password for `UNKNOWN' on `tty1'

    Mar 24 09:51:07 Tower login[3890]: ROOT LOGIN on `tty1'

    Mar 24 09:51:18 Tower unmenu-status: Starting unmenu web-server

    Mar 24 10:00:01 Tower logger: mover started

    Mar 24 10:00:01 Tower logger: .

    Mar 24 10:00:02 Tower logger: mover finished

  • Quote
    • Author

    format did not work again, are the drive just that messed up?

  • Quote

    I would do this. Remove those 2 drives by unassigning them. Run initconfig again to create a valid array without them. Start the array and build the parity.

     

    At the same time, download the newest preclear script and run it on those 2 drives. There is an option to only write the 0's and skip the pre-read and post-read steps if you want it to go faster. Once the preclear is done and the drives precleared and still appear OK you can attempt to add them again. They should add and format and be ready to use within 10 minutes.

     

    If you have a monitor and keyboard attached to the server you can use ctrl-F1 and ctrl-F2 to switch to different log-in prompts to do both preclears at once. Otherwise, you can telnet in 2 times and do them both at once. Do not break the telnet session while it is running or you have to start again. A zero write will take about 9 hours and a full preclear about 28 hours.

     

    Peter

  • Quote

    ^ That's alt-f1 and alt-f2, otherwise everything you said is correct.

  • Quote
    • Author

    Can I do this scenario,

      1) being that the original drives 500gb are still with out any faults. If I stop the array, remove the 2.0tb drives that I thought where the issue. Add the 500gb drive to the device and start the array. could I do an Initconfig and rebuild from there?

     

    2) problem being I don't remember their order in the array. not sure which one was #3 and 4 in sequence. Is there a way to figure that out?

     

    once again I am new to Linux so any and all command lines are helpful for me to move forward

     

    thanks again

  • Quote

    Yes, that will work.  It doesn't matter which disk was #3 and which was #4, unRAID will still figure it out.  Initconfig will invalidate your parity data, but it won't touch any of the data you actually care about.

  • Quote

    Yes, you can do that. You have to do the initconfig and then you start. It won't matter which order the drives were in. If you find the drives swapped backwards compared to the way you want them then you just stop the array and swap them and then start it again.

     

    Peter

  • Quote
    • Author

    I have to say thanks for the sound advice and quick response. I hope the parity come out o.k., I have just one orange on the parity drive now.

     

    I reinstalled the original 500gb drives and it looks like the array is healthy. The real reason for the drives failing was the Icy Dock bay having bad bays.

     

     

    Parity and my system are back up to a 100%, you could mark this up to solved...

    Screen_shot_2.JPG.30ce602db4e5fe72522fcce34778def2.JPG

  • Quote

    • Archived

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

    Go to topic listing

    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.