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.

[SOLVED] REDBALL! But no errors showing... PROBLEM ESCLATED!

Featured Replies

ok I had just been re-arranging the server area, moved my servers, plugged back in, started up, all looked good. Started to refile some new things to it and suddenly very very slow, pulled up the gui and REDBALL on the drive I was writing to! Checked the log and it was showing errors, but curiously, was also showing TEMPERATURE errors.  Tried to use scripted shutdown from UNMenu.. "array would not stop" went to the main page and Drive 1 was showing red with a temperature of 0,  but the other 8 drives had temps (30-32) but were showing UNFORMATTED!

 

Carefully stoppped the array, did a clean shutdown. Pulled the covers, checked all the cables and made sure all were well seated. Restarted the box, array comes up, Drive 1 still redballed, all others green and online, temperatures on all (29-31)

 

So, how to proceeded????

 

smart for drive 1 and current log attached.

 

4.7PRO if the log isn't obvious

 

redball120706.txt

smartdrive1.txt

  • Author

ok I'm thinking a cable got loose while moving it around.. so???

 

Stop the array.

    Go to the Devices page and un-assign the disk.

    Go to the main page and start the array.

    Stop the array again.

    Go to the Devices page and re-assign the disk.

    Go to the Main page - system should indicate there is a "new" drive to replace the disabled one. Check the confirmation box and click Start to start a parity-reconstruct of the disk.

 

yes?

 

(yeah, paranoia... I've got 20tb of video there and don't want to screw up)

  • Author

ok SMALL PROBLEM... the array won't stop..

 

better said, I did the stop array, and it just ... went away....

 

webserver inactive, no response just hangs waiting...

 

can still putty in however

/diskx shares are no longer visible

 

here's then end of the syslog (I haven't gone farther, it's just sittting there.....)

 

Jul  6 18:09:07 BURBANK emhttp: shcmd (38): /etc/rc.d/rc.samba stop | logger

Jul  6 18:09:07 BURBANK emhttp: shcmd (39): /etc/rc.d/rc.nfsd stop | logger

Jul  6 18:09:08 BURBANK emhttp: Spinning up all drives...

Jul  6 18:09:08 BURBANK emhttp: shcmd (40): sync

Jul  6 18:09:08 BURBANK kernel: mdcmd (25): spinup 0

Jul  6 18:09:08 BURBANK kernel: mdcmd (26): spinup 1

Jul  6 18:09:08 BURBANK kernel: mdcmd (27): spinup 2

Jul  6 18:09:08 BURBANK kernel: mdcmd (28): spinup 3

Jul  6 18:09:08 BURBANK kernel: mdcmd (29): spinup 4

Jul  6 18:09:08 BURBANK kernel: mdcmd (30): spinup 5

Jul  6 18:09:08 BURBANK kernel: mdcmd (31): spinup 6

Jul  6 18:09:08 BURBANK kernel: mdcmd (32): spinup 7

Jul  6 18:09:08 BURBANK kernel: mdcmd (33): spinup 8

Jul  6 18:09:09 BURBANK emhttp: shcmd (41): umount /mnt/disk1 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (42): rmdir /mnt/disk1 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (43): umount /mnt/disk2 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (44): rmdir /mnt/disk2 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (45): umount /mnt/disk3 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (46): rmdir /mnt/disk3 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (47): umount /mnt/disk4 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (48): rmdir /mnt/disk4 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (49): umount /mnt/disk5 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (50): rmdir /mnt/disk5 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (51): umount /mnt/disk6 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (52): rmdir /mnt/disk6 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (53): umount /mnt/disk7 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (54): rmdir /mnt/disk7 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (55): umount /mnt/disk8 >/dev/null 2>&1

Jul  6 18:09:12 BURBANK emhttp: shcmd (56): rmdir /mnt/disk8 >/dev/null 2>&1

Jul  6 18:09:12 BURBANK kernel: mdcmd (34): stop

Jul  6 18:09:12 BURBANK kernel: md1: stopping

Jul  6 18:09:12 BURBANK kernel: md2: stopping

Jul  6 18:09:12 BURBANK kernel: md3: stopping

Jul  6 18:09:12 BURBANK kernel: md4: stopping

Jul  6 18:09:12 BURBANK kernel: md5: stopping

Jul  6 18:09:12 BURBANK kernel: md6: stopping

Jul  6 18:09:12 BURBANK kernel: md7: stopping

Jul  6 18:09:12 BURBANK kernel: md8: stopping

Jul  6 18:09:17 BURBANK kernel: mdcmd (35): spindown 2

Jul  6 18:09:17 BURBANK kernel: mdcmd (36): spindown 2

Jul  6 18:09:20 BURBANK kernel: mdcmd (37): spindown 3

Jul  6 18:09:20 BURBANK kernel: mdcmd (38): spindown 3

Jul  6 18:09:20 BURBANK kernel: mdcmd (39): spindown 4

Jul  6 18:09:21 BURBANK kernel: mdcmd (40): spindown 4

Jul  6 18:09:21 BURBANK kernel: mdcmd (41): spindown 5

Jul  6 18:09:22 BURBANK emhttp: shcmd (57): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Jul  6 18:09:22 BURBANK emhttp: shcmd (58): cp /etc/exports- /etc/exports

Jul  6 18:09:22 BURBANK emhttp: shcmd (59): /etc/rc.d/rc.samba start | logger

ok SMALL PROBLEM... the array won't stop..

 

better said, I did the stop array, and it just ... went away....

 

webserver inactive, no response just hangs waiting...

 

can still putty in however

/diskx shares are no longer visible

 

here's then end of the syslog (I haven't gone farther, it's just sittting there.....)

 

Jul  6 18:09:07 BURBANK emhttp: shcmd (38): /etc/rc.d/rc.samba stop | logger

Jul  6 18:09:07 BURBANK emhttp: shcmd (39): /etc/rc.d/rc.nfsd stop | logger

Jul  6 18:09:08 BURBANK emhttp: Spinning up all drives...

Jul  6 18:09:08 BURBANK emhttp: shcmd (40): sync

Jul  6 18:09:08 BURBANK kernel: mdcmd (25): spinup 0

Jul  6 18:09:08 BURBANK kernel: mdcmd (26): spinup 1

Jul  6 18:09:08 BURBANK kernel: mdcmd (27): spinup 2

Jul  6 18:09:08 BURBANK kernel: mdcmd (28): spinup 3

Jul  6 18:09:08 BURBANK kernel: mdcmd (29): spinup 4

Jul  6 18:09:08 BURBANK kernel: mdcmd (30): spinup 5

Jul  6 18:09:08 BURBANK kernel: mdcmd (31): spinup 6

Jul  6 18:09:08 BURBANK kernel: mdcmd (32): spinup 7

Jul  6 18:09:08 BURBANK kernel: mdcmd (33): spinup 8

Jul  6 18:09:09 BURBANK emhttp: shcmd (41): umount /mnt/disk1 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (42): rmdir /mnt/disk1 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (43): umount /mnt/disk2 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (44): rmdir /mnt/disk2 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (45): umount /mnt/disk3 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (46): rmdir /mnt/disk3 >/dev/null 2>&1

Jul  6 18:09:10 BURBANK emhttp: shcmd (47): umount /mnt/disk4 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (48): rmdir /mnt/disk4 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (49): umount /mnt/disk5 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (50): rmdir /mnt/disk5 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (51): umount /mnt/disk6 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (52): rmdir /mnt/disk6 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (53): umount /mnt/disk7 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (54): rmdir /mnt/disk7 >/dev/null 2>&1

Jul  6 18:09:11 BURBANK emhttp: shcmd (55): umount /mnt/disk8 >/dev/null 2>&1

Jul  6 18:09:12 BURBANK emhttp: shcmd (56): rmdir /mnt/disk8 >/dev/null 2>&1

Jul  6 18:09:12 BURBANK kernel: mdcmd (34): stop

Jul  6 18:09:12 BURBANK kernel: md1: stopping

Jul  6 18:09:12 BURBANK kernel: md2: stopping

Jul  6 18:09:12 BURBANK kernel: md3: stopping

Jul  6 18:09:12 BURBANK kernel: md4: stopping

Jul  6 18:09:12 BURBANK kernel: md5: stopping

Jul  6 18:09:12 BURBANK kernel: md6: stopping

Jul  6 18:09:12 BURBANK kernel: md7: stopping

Jul  6 18:09:12 BURBANK kernel: md8: stopping

Jul  6 18:09:17 BURBANK kernel: mdcmd (35): spindown 2

Jul  6 18:09:17 BURBANK kernel: mdcmd (36): spindown 2

Jul  6 18:09:20 BURBANK kernel: mdcmd (37): spindown 3

Jul  6 18:09:20 BURBANK kernel: mdcmd (38): spindown 3

Jul  6 18:09:20 BURBANK kernel: mdcmd (39): spindown 4

Jul  6 18:09:21 BURBANK kernel: mdcmd (40): spindown 4

Jul  6 18:09:21 BURBANK kernel: mdcmd (41): spindown 5

Jul  6 18:09:22 BURBANK emhttp: shcmd (57): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Jul  6 18:09:22 BURBANK emhttp: shcmd (58): cp /etc/exports- /etc/exports

Jul  6 18:09:22 BURBANK emhttp: shcmd (59): /etc/rc.d/rc.samba start | logger

according to the syslog, it has stopped.

 

 

  • Author

yeah, it was the web interface that was un-responsive... finally putty'ed in, did a command line reboot, came up, this time did the stop/unassign/start/stop/reassign/restart and 8 hours later, things are back to all green..

please mark solved.

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.