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

[4.5] Lost network during disk rebuild

nukhem
in unRAID Server 4.4 [No new topics]

Featured Replies

Hi, today i decided to replace my ATA 200GB drive with a WD green 1TB SATA drive.

 

I started the array to start rebuilding the new disk followed by a refresh in my browser.

Suddenly my connection to the server dissappeared, cannot access the web interface, cannot ping the server, cannot telnet anymore. i'm clueless.

 

After rebooting the server unraid loads fine, initializes eth0 and loses screen output after ' starting samba '

 

Update:

 

I removed the new HDD and the system started fine, i could access the interface again, only the new disk was missing.

So i tried booting with the new hdd installed again, now it was loading fine but all (10) drives all had blue balls next to them :/

 

Needless to say i'm panicking now. I was able to get a syslog now wich i included in this post.

syslog.txt

  • Author

Update2:

 

I reinstalled the old IDE 200GB drive and did a new parity calculation by starting the array. So everything is back like it was before i tried to replace the disk. Should i try again upgrading the drive?

Update2:

 

I reinstalled the old IDE 200GB drive and did a new parity calculation by starting the array. So everything is back like it was before i tried to replace the disk. Should i try again upgrading the drive?

This time, I'd open a telnet window and keep an eye on the system log with

tail -f /var/log/syslog

 

It is possible it is filling with errors eventually using all memory and causing the crash.

 

Joe L.

  • Author

I restarted the procedure with same results as before : losing connection

 

I did however open a telnet window on my main computer to follow the log with these results:

 

Tower login: root

Linux 2.6.31.6-unRAID.

root@Tower:~# tail -f /var/log/syslog

Jan 27 18:09:02 Tower emhttp: _shcmd: shcmd (3): exit status: 1

Jan 27 18:09:02 Tower emhttp: shcmd (4): cp /etc/exports- /etc/exports

Jan 27 18:09:02 Tower emhttp: shcmd (5): killall -HUP smbd

Jan 27 18:09:02 Tower emhttp: shcmd (6): /etc/rc.d/rc.nfsd restart | logger

Jan 27 18:09:03 Tower emhttp: shcmd (6): cp /var/spool/cron/crontabs/root- /var/                    spool/cron/crontabs/root

Jan 27 18:09:03 Tower emhttp: shcmd (7): echo '# Generated mover schedule:' >>/v                    ar/spool/cron/crontabs/root

Jan 27 18:09:03 Tower emhttp: shcmd (8): echo '40 3 * * * /usr/local/sbin/mover                    2>&1 | logger' >>/var/spool/cron/crontabs/root

Jan 27 18:09:03 Tower emhttp: shcmd (9): crontab /var/spool/cron/crontabs/root

Jan 27 18:10:30 Tower in.telnetd[1495]: connect from 192.168.1.99 (192.168.1.99)

Jan 27 18:10:32 Tower login[1496]: ROOT LOGIN  on `pts/0' from `192.168.1.99'

Jan 27 18:11:36 Tower emhttp: read_attr: fopen: No such file or directory

Jan 27 18:11:36 Tower emhttp: shcmd (11): rmmod md-mod >>/var/log/go 2>&1

Jan 27 18:11:36 Tower emhttp: shcmd (12): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,32,8,16,22,0,22,64,8,48,8,64,8,96,8,80,8,144,8,112,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1

Jan 27 18:11:36 Tower kernel: md: unRAID driver removed

Jan 27 18:11:36 Tower kernel: md: unRAID driver 0.95.3 installed

Jan 27 18:11:36 Tower kernel: md: import disk0: [8,0] (sda) SAMSUNG HD103UJ                          S13PJ1KQA01591      offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk1: [8,32] (sdc) SAMSUNG HD103UJ                          S13PJ1BQ603926      offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk2: [8,16] (sdb) WDC WD10EACS-00D6B0                          WD-WCAU45302395 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk3: [22,0] (hdc) WDC WD10EACS-00D6B0 WD-WCAU45413625 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk4: [22,64] (hdd) WDC WD10EADS-00L5B1 WD-WCAU47006749 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk5: [8,48] (sdd) WDC WD10EACS-00D6B0                          WD-WCAU45560163 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk6: [8,64] (sde) WDC WD10EADS-00L5B1                          WD-WCAU46984436 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk7: [8,96] (sdg) WDC WD1001FALS-00J7B1                        WD-WMATV2396461 offset: 63 size: 976761496

Jan 27 18:11:36 Tower kernel: md: import disk8: [8,80] (sdf) SAMSUNG HD103UJ                          S13PJ1KQA01592      offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk9: [8,144] (sdj) SAMSUNG HD103UJ                          S1PVJ1BQ605624      offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk10: [8,112] (sdh) WDC WD10EADS-00L5B1                          WD-WCAU48176712 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: disk10 wrong

Jan 27 18:11:36 Tower kernel: mdcmd (2): set md_num_stripes 1280

Jan 27 18:11:36 Tower kernel: mdcmd (3): set md_write_limit 768

Jan 27 18:11:36 Tower kernel: mdcmd (4): set md_sync_window 288

Jan 27 18:11:36 Tower kernel: mdcmd (5): set spinup_group 0 0

Jan 27 18:11:36 Tower kernel: mdcmd (6): set spinup_group 1 0

Jan 27 18:11:36 Tower kernel: mdcmd (7): set spinup_group 2 0

Jan 27 18:11:36 Tower kernel: mdcmd (8): set spinup_group 3 16

Jan 27 18:11:36 Tower kernel: mdcmd (9): set spinup_group 4 8

Jan 27 18:11:36 Tower kernel: mdcmd (10): set spinup_group 5 0

Jan 27 18:11:36 Tower kernel: mdcmd (11): set spinup_group 6 0

Jan 27 18:11:36 Tower kernel: mdcmd (12): set spinup_group 7 0

Jan 27 18:11:36 Tower kernel: mdcmd (13): set spinup_group 8 0

Jan 27 18:11:36 Tower kernel: mdcmd (14): set spinup_group 9 0

Jan 27 18:11:36 Tower kernel: mdcmd (15): set spinup_group 10 0

Jan 27 18:12:04 Tower emhttp: shcmd (13): /usr/local/sbin/set_ncq sda 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (14): /usr/local/sbin/set_ncq sdc 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (15): /usr/local/sbin/set_ncq sdb 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (16): /usr/local/sbin/set_ncq hdc 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (17): /usr/local/sbin/set_ncq hdd 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (18): /usr/local/sbin/set_ncq sdd 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (19): /usr/local/sbin/set_ncq sde 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (20): /usr/local/sbin/set_ncq sdg 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (21): /usr/local/sbin/set_ncq sdf 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (22): /usr/local/sbin/set_ncq sdj 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (23): /usr/local/sbin/set_ncq sdh 1 >/dev/null

Jan 27 18:12:04 Tower kernel: mdcmd (19): start UPGRADE_DISK

Jan 27 18:12:04 Tower kernel: unraid: allocating 59180K for 1280 stripes (11 disks)

Jan 27 18:12:04 Tower kernel: md1: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md2: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md3: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md4: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md5: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md6: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md7: running, size: 976761496 blocks

Jan 27 18:12:04 Tower kernel: md8: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md9: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md10: running, size: 976762552 blocks

Jan 27 18:12:04 Tower emhttp: shcmd (24): mkdir /mnt/disk1

Jan 27 18:12:04 Tower emhttp: shcmd (25): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1  >/dev/null 2>&1

Jan 27 18:12:04 Tower kernel: mdcmd (21): check

Jan 27 18:12:04 Tower kernel: md: recovery thread woken up ...

Jan 27 18:12:04 Tower kernel: md: recovery thread rebuilding disk10 ...

Jan 27 18:12:04 Tower emhttp: shcmd (25): mkdir /mnt/disk2

Jan 27 18:12:04 Tower emhttp: shcmd (26): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (26): mkdir /mnt/disk3

Jan 27 18:12:04 Tower emhttp: shcmd (27): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (27): mkdir /mnt/disk4

Jan 27 18:12:04 Tower kernel: md: using 1152k window, over a total of 976762552 blocks.

Jan 27 18:12:04 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md1): using ordered data mode

Jan 27 18:12:04 Tower emhttp: shcmd (28): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (28): mkdir /mnt/disk5

Jan 27 18:12:04 Tower emhttp: shcmd (29): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (29): mkdir /mnt/disk6

Jan 27 18:12:04 Tower emhttp: shcmd (30): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md6 /mnt/disk6  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (30): mkdir /mnt/disk7

Jan 27 18:12:04 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

Jan 27 18:12:04 Tower kernel: REISERFS (device md1): checking transaction log (md1)

Jan 27 18:12:04 Tower emhttp: shcmd (30): mkdir /mnt/disk8

Jan 27 18:12:04 Tower emhttp: shcmd (31): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md7 /mnt/disk7  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (31): mkdir /mnt/disk9

Jan 27 18:12:04 Tower emhttp: shcmd (32): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md8 /mnt/disk8  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (32): mkdir /mnt/disk10

Jan 27 18:12:04 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md2): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md3): using ordered data mode

Jan 27 18:12:04 Tower emhttp: shcmd (33): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md9 /mnt/disk9  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (34): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md10 /mnt/disk10  >/dev/null 2>&1

Jan 27 18:12:04 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

Jan 27 18:12:04 Tower kernel: REISERFS (device md2): checking transaction log (md2)

Jan 27 18:12:04 Tower kernel: REISERFS (device md9): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md9): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md8): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md8): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md9): journal params: device md9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:04 Tower kernel: REISERFS (device md9): checking transaction log (md9)

Jan 27 18:12:04 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md4): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md6): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md5): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md7): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md10): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md10): using ordered data mode

Jan 27 18:12:04 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

Jan 27 18:12:04 Tower kernel: REISERFS (device md5): checking transaction log (md5)

Jan 27 18:12:04 Tower kernel: REISERFS (device md8): journal params: device md8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:04 Tower kernel: REISERFS (device md8): checking transaction log (md8)

Jan 27 18:12:04 Tower kernel: REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:04 Tower kernel: REISERFS (device md6): checking transaction log (md6)

Jan 27 18:12:04 Tower kernel: REISERFS (device md7): journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:04 Tower kernel: REISERFS (device md7): checking transaction log (md7)

Jan 27 18:12:05 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:05 Tower kernel: REISERFS (device md3): checking transaction log (md3)

Jan 27 18:12:05 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:05 Tower kernel: REISERFS (device md4): checking transaction log (md4)

Jan 27 18:12:05 Tower kernel: REISERFS (device md10): journal params: device md10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:05 Tower kernel: REISERFS (device md10): checking transaction log (md10)

 

I restarted the procedure with same results as before : losing connection

 

I did however open a telnet window on my main computer to follow the log with these results:

 

Tower login: root

Linux 2.6.31.6-unRAID.

root@Tower:~# tail -f /var/log/syslog

Jan 27 18:09:02 Tower emhttp: _shcmd: shcmd (3): exit status: 1

Jan 27 18:09:02 Tower emhttp: shcmd (4): cp /etc/exports- /etc/exports

Jan 27 18:09:02 Tower emhttp: shcmd (5): killall -HUP smbd

Jan 27 18:09:02 Tower emhttp: shcmd (6): /etc/rc.d/rc.nfsd restart | logger

Jan 27 18:09:03 Tower emhttp: shcmd (6): cp /var/spool/cron/crontabs/root- /var/                    spool/cron/crontabs/root

Jan 27 18:09:03 Tower emhttp: shcmd (7): echo '# Generated mover schedule:' >>/v                    ar/spool/cron/crontabs/root

Jan 27 18:09:03 Tower emhttp: shcmd (8): echo '40 3 * * * /usr/local/sbin/mover                     2>&1 | logger' >>/var/spool/cron/crontabs/root

Jan 27 18:09:03 Tower emhttp: shcmd (9): crontab /var/spool/cron/crontabs/root

Jan 27 18:10:30 Tower in.telnetd[1495]: connect from 192.168.1.99 (192.168.1.99)

Jan 27 18:10:32 Tower login[1496]: ROOT LOGIN  on `pts/0' from `192.168.1.99'

Jan 27 18:11:36 Tower emhttp: read_attr: fopen: No such file or directory

Jan 27 18:11:36 Tower emhttp: shcmd (11): rmmod md-mod >>/var/log/go 2>&1

Jan 27 18:11:36 Tower emhttp: shcmd (12): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,32,8,16,22,0,22,64,8,48,8,64,8,96,8,80,8,144,8,112,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1

Jan 27 18:11:36 Tower kernel: md: unRAID driver removed

Jan 27 18:11:36 Tower kernel: md: unRAID driver 0.95.3 installed

Jan 27 18:11:36 Tower kernel: md: import disk0: [8,0] (sda) SAMSUNG HD103UJ                          S13PJ1KQA01591       offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk1: [8,32] (sdc) SAMSUNG HD103UJ                          S13PJ1BQ603926       offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk2: [8,16] (sdb) WDC WD10EACS-00D6B0                           WD-WCAU45302395 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk3: [22,0] (hdc) WDC WD10EACS-00D6B0 WD-WCAU45413625 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk4: [22,64] (hdd) WDC WD10EADS-00L5B1 WD-WCAU47006749 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk5: [8,48] (sdd) WDC WD10EACS-00D6B0                           WD-WCAU45560163 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk6: [8,64] (sde) WDC WD10EADS-00L5B1                           WD-WCAU46984436 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk7: [8,96] (sdg) WDC WD1001FALS-00J7B1                         WD-WMATV2396461 offset: 63 size: 976761496

Jan 27 18:11:36 Tower kernel: md: import disk8: [8,80] (sdf) SAMSUNG HD103UJ                          S13PJ1KQA01592       offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk9: [8,144] (sdj) SAMSUNG HD103UJ                          S1PVJ1BQ605624       offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: import disk10: [8,112] (sdh) WDC WD10EADS-00L5B1                           WD-WCAU48176712 offset: 63 size: 976762552

Jan 27 18:11:36 Tower kernel: md: disk10 wrong

Jan 27 18:11:36 Tower kernel: mdcmd (2): set md_num_stripes 1280

Jan 27 18:11:36 Tower kernel: mdcmd (3): set md_write_limit 768

Jan 27 18:11:36 Tower kernel: mdcmd (4): set md_sync_window 288

Jan 27 18:11:36 Tower kernel: mdcmd (5): set spinup_group 0 0

Jan 27 18:11:36 Tower kernel: mdcmd (6): set spinup_group 1 0

Jan 27 18:11:36 Tower kernel: mdcmd (7): set spinup_group 2 0

Jan 27 18:11:36 Tower kernel: mdcmd (8): set spinup_group 3 16

Jan 27 18:11:36 Tower kernel: mdcmd (9): set spinup_group 4 8

Jan 27 18:11:36 Tower kernel: mdcmd (10): set spinup_group 5 0

Jan 27 18:11:36 Tower kernel: mdcmd (11): set spinup_group 6 0

Jan 27 18:11:36 Tower kernel: mdcmd (12): set spinup_group 7 0

Jan 27 18:11:36 Tower kernel: mdcmd (13): set spinup_group 8 0

Jan 27 18:11:36 Tower kernel: mdcmd (14): set spinup_group 9 0

Jan 27 18:11:36 Tower kernel: mdcmd (15): set spinup_group 10 0

Jan 27 18:12:04 Tower emhttp: shcmd (13): /usr/local/sbin/set_ncq sda 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (14): /usr/local/sbin/set_ncq sdc 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (15): /usr/local/sbin/set_ncq sdb 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (16): /usr/local/sbin/set_ncq hdc 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (17): /usr/local/sbin/set_ncq hdd 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (18): /usr/local/sbin/set_ncq sdd 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (19): /usr/local/sbin/set_ncq sde 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (20): /usr/local/sbin/set_ncq sdg 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (21): /usr/local/sbin/set_ncq sdf 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (22): /usr/local/sbin/set_ncq sdj 1 >/dev/null

Jan 27 18:12:04 Tower emhttp: shcmd (23): /usr/local/sbin/set_ncq sdh 1 >/dev/null

Jan 27 18:12:04 Tower kernel: mdcmd (19): start UPGRADE_DISK

Jan 27 18:12:04 Tower kernel: unraid: allocating 59180K for 1280 stripes (11 disks)

Jan 27 18:12:04 Tower kernel: md1: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md2: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md3: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md4: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md5: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md6: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md7: running, size: 976761496 blocks

Jan 27 18:12:04 Tower kernel: md8: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md9: running, size: 976762552 blocks

Jan 27 18:12:04 Tower kernel: md10: running, size: 976762552 blocks

Jan 27 18:12:04 Tower emhttp: shcmd (24): mkdir /mnt/disk1

Jan 27 18:12:04 Tower emhttp: shcmd (25): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1  >/dev/null 2>&1

Jan 27 18:12:04 Tower kernel: mdcmd (21): check

Jan 27 18:12:04 Tower kernel: md: recovery thread woken up ...

Jan 27 18:12:04 Tower kernel: md: recovery thread rebuilding disk10 ...

Jan 27 18:12:04 Tower emhttp: shcmd (25): mkdir /mnt/disk2

Jan 27 18:12:04 Tower emhttp: shcmd (26): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (26): mkdir /mnt/disk3

Jan 27 18:12:04 Tower emhttp: shcmd (27): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (27): mkdir /mnt/disk4

Jan 27 18:12:04 Tower kernel: md: using 1152k window, over a total of 976762552 blocks.

Jan 27 18:12:04 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md1): using ordered data mode

Jan 27 18:12:04 Tower emhttp: shcmd (28): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (28): mkdir /mnt/disk5

Jan 27 18:12:04 Tower emhttp: shcmd (29): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (29): mkdir /mnt/disk6

Jan 27 18:12:04 Tower emhttp: shcmd (30): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md6 /mnt/disk6  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (30): mkdir /mnt/disk7

Jan 27 18:12:04 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

Jan 27 18:12:04 Tower kernel: REISERFS (device md1): checking transaction log (md1)

Jan 27 18:12:04 Tower emhttp: shcmd (30): mkdir /mnt/disk8

Jan 27 18:12:04 Tower emhttp: shcmd (31): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md7 /mnt/disk7  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (31): mkdir /mnt/disk9

Jan 27 18:12:04 Tower emhttp: shcmd (32): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md8 /mnt/disk8  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (32): mkdir /mnt/disk10

Jan 27 18:12:04 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md2): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md3): using ordered data mode

Jan 27 18:12:04 Tower emhttp: shcmd (33): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md9 /mnt/disk9  >/dev/null 2>&1

Jan 27 18:12:04 Tower emhttp: shcmd (34): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md10 /mnt/disk10  >/dev/null 2>&1

Jan 27 18:12:04 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

Jan 27 18:12:04 Tower kernel: REISERFS (device md2): checking transaction log (md2)

Jan 27 18:12:04 Tower kernel: REISERFS (device md9): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md9): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md8): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md8): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md9): journal params: device md9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:04 Tower kernel: REISERFS (device md9): checking transaction log (md9)

Jan 27 18:12:04 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md4): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md6): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md5): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md7): using ordered data mode

Jan 27 18:12:04 Tower kernel: REISERFS (device md10): found reiserfs format "3.6" with standard journal

Jan 27 18:12:04 Tower kernel: REISERFS (device md10): using ordered data mode

Jan 27 18:12:04 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

Jan 27 18:12:04 Tower kernel: REISERFS (device md5): checking transaction log (md5)

Jan 27 18:12:04 Tower kernel: REISERFS (device md8): journal params: device md8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:04 Tower kernel: REISERFS (device md8): checking transaction log (md8)

Jan 27 18:12:04 Tower kernel: REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:04 Tower kernel: REISERFS (device md6): checking transaction log (md6)

Jan 27 18:12:04 Tower kernel: REISERFS (device md7): journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:04 Tower kernel: REISERFS (device md7): checking transaction log (md7)

Jan 27 18:12:05 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:05 Tower kernel: REISERFS (device md3): checking transaction log (md3)

Jan 27 18:12:05 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:05 Tower kernel: REISERFS (device md4): checking transaction log (md4)

Jan 27 18:12:05 Tower kernel: REISERFS (device md10): journal params: device md10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:12:05 Tower kernel: REISERFS (device md10): checking transaction log (md10)

 

I don't see anything unusual in the syslog segment you posted.
  • Author

I replaced the new 1 TB drive with a precleared 500GB drive i had spare with same results. The log seems to get a bit further now before it crashes.

 

Tower login: root

Linux 2.6.31.6-unRAID.

root@Tower:~# tail -f /var/log/syslog

Jan 27 18:30:34 Tower kernel: mdcmd (8): set spinup_group 3 16

Jan 27 18:30:34 Tower kernel: mdcmd (9): set spinup_group 4 8

Jan 27 18:30:34 Tower kernel: mdcmd (10): set spinup_group 5 0

Jan 27 18:30:34 Tower kernel: mdcmd (11): set spinup_group 6 0

Jan 27 18:30:34 Tower kernel: mdcmd (12): set spinup_group 7 0

Jan 27 18:30:34 Tower kernel: mdcmd (13): set spinup_group 8 0

Jan 27 18:30:34 Tower kernel: mdcmd (14): set spinup_group 9 0

Jan 27 18:30:34 Tower kernel: mdcmd (15): set spinup_group 10 0

Jan 27 18:31:21 Tower in.telnetd[1536]: connect from 192.168.1.99 (192.168.1.99)

Jan 27 18:31:25 Tower login[1537]: ROOT LOGIN  on `pts/0' from `192.168.1.99'

Jan 27 18:31:58 Tower emhttp: shcmd (13): /usr/local/sbin/set_ncq sda 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (14): /usr/local/sbin/set_ncq sdc 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (15): /usr/local/sbin/set_ncq sdb 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (16): /usr/local/sbin/set_ncq hdc 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (17): /usr/local/sbin/set_ncq hdd 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (18): /usr/local/sbin/set_ncq sdd 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (19): /usr/local/sbin/set_ncq sde 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (20): /usr/local/sbin/set_ncq sdg 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (21): /usr/local/sbin/set_ncq sdf 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (22): /usr/local/sbin/set_ncq sdi 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: shcmd (23): /usr/local/sbin/set_ncq sdh 1 >/dev/null

Jan 27 18:31:58 Tower emhttp: writing mbr on disk 10 (/dev/sdh)

Jan 27 18:31:58 Tower emhttp: re-reading /dev/sdh partition table

Jan 27 18:31:58 Tower kernel:  sdh: sdh1

Jan 27 18:31:59 Tower kernel: mdcmd (20): start UPGRADE_DISK

Jan 27 18:31:59 Tower kernel: unraid: allocating 59180K for 1280 stripes (11 disks)

Jan 27 18:31:59 Tower kernel: md1: running, size: 976762552 blocks

Jan 27 18:31:59 Tower kernel: md2: running, size: 976762552 blocks

Jan 27 18:31:59 Tower kernel: md3: running, size: 976762552 blocks

Jan 27 18:31:59 Tower kernel: md4: running, size: 976762552 blocks

Jan 27 18:31:59 Tower kernel: md5: running, size: 976762552 blocks

Jan 27 18:31:59 Tower kernel: md6: running, size: 976762552 blocks

Jan 27 18:31:59 Tower kernel: md7: running, size: 976761496 blocks

Jan 27 18:31:59 Tower kernel: md8: running, size: 976762552 blocks

Jan 27 18:31:59 Tower kernel: md9: running, size: 976762552 blocks

Jan 27 18:31:59 Tower kernel: md10: running, size: 488385496 blocks

Jan 27 18:31:59 Tower emhttp: shcmd (24): mkdir /mnt/disk1

Jan 27 18:31:59 Tower emhttp: shcmd (25): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1  >/dev/null 2>&1

Jan 27 18:31:59 Tower emhttp: shcmd (25): mkdir /mnt/disk2

Jan 27 18:31:59 Tower kernel: mdcmd (22): check

Jan 27 18:31:59 Tower kernel: md: recovery thread woken up ...

Jan 27 18:31:59 Tower kernel: md: recovery thread rebuilding disk10 ...

Jan 27 18:31:59 Tower emhttp: shcmd (26): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2  >/dev/null 2>&1

Jan 27 18:31:59 Tower emhttp: shcmd (26): mkdir /mnt/disk3

Jan 27 18:31:59 Tower emhttp: shcmd (27): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3  >/dev/null 2>&1

Jan 27 18:31:59 Tower emhttp: shcmd (27): mkdir /mnt/disk4

Jan 27 18:31:59 Tower emhttp: shcmd (28): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4  >/dev/null 2>&1

Jan 27 18:31:59 Tower kernel: md: using 1152k window, over a total of 488385496 blocks.

Jan 27 18:31:59 Tower emhttp: shcmd (28): mkdir /mnt/disk5

Jan 27 18:31:59 Tower emhttp: shcmd (29): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5  >/dev/null 2>&1

Jan 27 18:31:59 Tower emhttp: shcmd (29): mkdir /mnt/disk6

Jan 27 18:31:59 Tower emhttp: shcmd (30): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md6 /mnt/disk6  >/dev/null 2>&1

Jan 27 18:31:59 Tower emhttp: shcmd (30): mkdir /mnt/disk7

Jan 27 18:31:59 Tower emhttp: shcmd (31): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md7 /mnt/disk7  >/dev/null 2>&1

Jan 27 18:31:59 Tower emhttp: shcmd (31): mkdir /mnt/disk8

Jan 27 18:31:59 Tower emhttp: shcmd (31): mkdir /mnt/disk9

Jan 27 18:31:59 Tower emhttp: shcmd (32): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md8 /mnt/disk8  >/dev/null 2>&1

Jan 27 18:31:59 Tower emhttp: shcmd (33): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md9 /mnt/disk9  >/dev/null 2>&1

Jan 27 18:31:59 Tower emhttp: shcmd (33): mkdir /mnt/disk10

Jan 27 18:31:59 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md2): using ordered data mode

Jan 27 18:31:59 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md1): using ordered data mode

Jan 27 18:31:59 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md3): using ordered data mode

Jan 27 18:31:59 Tower kernel: REISERFS (device md9): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md9): using ordered data mode

Jan 27 18:31:59 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

Jan 27 18:31:59 Tower kernel: REISERFS (device md2): checking transaction log (md2)

Jan 27 18:31:59 Tower emhttp: shcmd (34): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md10 /mnt/disk10  >/dev/null 2>&1

Jan 27 18:31:59 Tower kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md6): using ordered data mode

Jan 27 18:31:59 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

Jan 27 18:31:59 Tower kernel: REISERFS (device md1): checking transaction log (md1)

Jan 27 18:31:59 Tower kernel: REISERFS (device md9): journal params: device md9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:31:59 Tower kernel: REISERFS (device md9): checking transaction log (md9)

Jan 27 18:31:59 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md4): using ordered data mode

Jan 27 18:31:59 Tower kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md7): using ordered data mode

Jan 27 18:31:59 Tower kernel: REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:31:59 Tower kernel: REISERFS (device md6): checking transaction log (md6)

Jan 27 18:31:59 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md5): using ordered data mode

Jan 27 18:31:59 Tower kernel: REISERFS (device md8): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md8): using ordered data mode

Jan 27 18:31:59 Tower kernel: REISERFS (device md10): found reiserfs format "3.6" with standard journal

Jan 27 18:31:59 Tower kernel: REISERFS (device md10): using ordered data mode

Jan 27 18:31:59 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

Jan 27 18:31:59 Tower kernel: REISERFS (device md5): checking transaction log (md5)

Jan 27 18:31:59 Tower kernel: REISERFS (device md7): journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:31:59 Tower kernel: REISERFS (device md7): checking transaction log (md7)

Jan 27 18:31:59 Tower kernel: REISERFS (device md8): journal params: device md8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:31:59 Tower kernel: REISERFS (device md8): checking transaction log (md8)

Jan 27 18:31:59 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:31:59 Tower kernel: REISERFS (device md3): checking transaction log (md3)

Jan 27 18:31:59 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:31:59 Tower kernel: REISERFS (device md4): checking transaction log (md4)

Jan 27 18:31:59 Tower kernel: REISERFS (device md10): journal params: device md10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jan 27 18:31:59 Tower kernel: REISERFS (device md10): checking transaction log (md10)

Jan 27 18:31:59 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

Jan 27 18:31:59 Tower kernel: REISERFS (device md5): Using r5 hash to sort names

Jan 27 18:31:59 Tower kernel: REISERFS (device md1): Using r5 hash to sort names

Jan 27 18:32:00 Tower kernel: REISERFS (device md6): Using r5 hash to sort names

Jan 27 18:32:00 Tower kernel: REISERFS (device md7): Using r5 hash to sort names

Jan 27 18:32:00 Tower kernel: REISERFS (device md8): Using r5 hash to sort names

Jan 27 18:32:00 Tower kernel: REISERFS (device md9): Using r5 hash to sort names

Jan 27 18:32:00 Tower kernel: REISERFS (device md3): Using r5 hash to sort names

Jan 27 18:32:00 Tower kernel: REISERFS (device md4): Using r5 hash to sort names

Jan 27 18:32:00 Tower kernel: REISERFS (device md10): Using r5 hash to sort names

 

 

  • Author

I backed up my flashdrive before i disconnected the IDE drive. Would it hurt if i loaded that backup again on my flashdrive to avoid having parity calculated again if i decide to just keep the old IDE drive?

I backed up my flashdrive before i disconnected the IDE drive. Would it hurt if i loaded that backup again on my flashdrive to avoid having parity calculated again if i decide to just keep the old IDE drive?

That's exactly what I do when experimenting.

Put back the old IDE drive, and put back the old config folder.  Reboot... you are on-line with no parity check.

 

Can you power up with the old disks and the new one plugged in too?  (just don't assign the new one)

and then you can run a smartctl report on the new drive that seems to crash your server.

  • Author

That's the reason why i replaced it with my precleared 500GB with the same result.

That's the reason why i replaced it with my precleared 500GB with the same result.

Then it points to some other hardware. 

 

Power supply? Are you getting to its limits?

Memory?  Are the timings, voltage, and speed set correctly?

Motherboard... try some of the boot codes as shown in the wiki.

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.