Odd problem here. I'm on 5.0 B7 and I have a 1.5TB "MBR: unaligned" parity drive. Just added a new 1.5TB drive to my array (different make and model from the parity drive - the new disk is a WD Green Caviar WD15EARS). This is the first drive I've added since upgrading from 4.5 to 5.0b7. The drive is unjumpered (will double check this in the morning).

 

Per the manual instructions: I installed the new drive, started the array, assigned drive to new location, clicked format. Drive was cleared/formatted, array restarted, but when I login to the web gui, it shows the new drive as "Unformatted" and I can't access my array over SMB. When I click on the drive in the web GUI to get more details, it shows as "MBR: 4k aligned."

 

Though the array shows as being started in the web GUI (green icons with a note saying unformatted disk present), I can't access it via SMB. Further, when I telnet into the box and type ls, I only see 5 commands (initconfig, mdcmd, mkmbr, powerdown, samba).

 

Finally, ran a short SMART test on the new drive and it appears as though it passed.

 

Not sure what's going on here and not sure if it has anything to do with this "4k aligned" or EARS stuff. Not touching my box until I hear back from someone. Any help is appreciated. Thanks!

uh oh...here's an excerpt of my log... (disk 5 is the new HDD)

 

Jul  8 03:25:27 Tower emhttp_event: array_started

Jul  8 03:25:27 Tower emhttp: Mounting disks...

Jul  8 03:25:27 Tower emhttp: shcmd (84): mkdir /mnt/disk1

Jul  8 03:25:27 Tower emhttp: shcmd (85): mkdir /mnt/disk2

Jul  8 03:25:27 Tower emhttp: shcmd (86): mkdir /mnt/disk4

Jul  8 03:25:27 Tower emhttp: shcmd (87): mkdir /mnt/disk3

Jul  8 03:25:27 Tower emhttp: shcmd (88): mkdir /mnt/disk5

Jul  8 03:25:27 Tower emhttp: shcmd (90): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 |logger

Jul  8 03:25:27 Tower emhttp: shcmd (89): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 |logger

Jul  8 03:25:27 Tower kernel: mdcmd (43): check NOCORRECT

Jul  8 03:25:27 Tower kernel: md: recovery thread woken up ...

Jul  8 03:25:27 Tower emhttp: shcmd (91): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 |logger

Jul  8 03:25:27 Tower emhttp: shcmd (92): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 2>&1 |logger

Jul  8 03:25:27 Tower emhttp: shcmd (93): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5 2>&1 |logger

Jul  8 03:25:27 Tower kernel: md: recovery thread has nothing to resync

Jul  8 03:25:39 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md5,

Jul  8 03:25:39 Tower logger:        missing codepage or helper program, or other error

Jul  8 03:25:39 Tower logger:        In some cases useful info is found in syslog - try

Jul  8 03:25:39 Tower logger:        dmesg | tail  or so

Jul  8 03:25:39 Tower logger:

Jul  8 03:25:39 Tower emhttp: _shcmd: shcmd (93): exit status: 32

Jul  8 03:25:39 Tower emhttp: disk5 mount error: 32

Jul  8 03:25:39 Tower emhttp: shcmd (94): rmdir /mnt/disk5

Jul  8 03:25:39 Tower kernel: REISERFS warning (device md5): sh-2021 reiserfs_fill_super: can not find reiserfs on md5

Jul  8 03:25:39 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal

Jul  8 03:25:39 Tower kernel: REISERFS (device md3): using ordered data mode

Jul  8 03:25:39 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal

Jul  8 03:25:39 Tower kernel: REISERFS (device md4): using ordered data mode

Jul  8 03:25:39 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

Jul  8 03:25:39 Tower kernel: REISERFS (device md2): using ordered data mode

Jul  8 03:25:39 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal

Jul  8 03:25:39 Tower kernel: REISERFS (device md1): using ordered data mode

Jul  8 03:25:39 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

Jul  8 03:25:39 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

Jul  8 03:25:39 Tower kernel: REISERFS (device md4): checking transaction log (md3)

Jul  8 03:25:39 Tower kernel: REISERFS (device md3): checking transaction log (md3)

Jul  8 03:25:39 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

Jul  8 03:25:39 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

Jul  8 03:25:39 Tower kernel: REISERFS (device md2): checking transaction log (md1)

Jul  8 03:25:39 Tower kernel: REISERFS (device md1): checking transaction log (md1)

Jul  8 03:25:39 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

Jul  8 03:25:39 Tower kernel: REISERFS (device md4): Using r5 hash to sort names

Jul  8 03:25:39 Tower kernel: REISERFS (device md3): Using r5 hash to sort names

Jul  8 03:25:39 Tower kernel: REISERFS (device md1): Using r5 hash to sort names

Are you sure you formatted it?

 

At first, you will get an option to add the disk to the array. I believe you have to check a box when you do this step. unRAID would go off and clear the disk and the array would be offline for that time. After this step, you have to do a seperate format of the disk. There should be a format button available to format it. Double check that only the disk you want to format is showing as unformatted before doing this step.

 

The syslog section you posted is fairly typical of the section you see when the array is started and I would expect those added errors with an unformatted disk (the mount and reiserfs errors). The disk can't be mounted if the disk has not been formatted yet.

 

Peter

 

Good point, I clicked format again, it looks like the array is working, but still can't access it over SMB. Tried rebooting to no avail. Any help...?

You'll probably need to post more of the log for help. I'm not sure what to suggest.

 

Peter

Are you using an AOC-SASLP-MV8 controller?  If so, please post what hard drives you have connected to it and how they are formatted.

Thanks.

 

Somehow things started working again. Not sure what was going on.  I swear I had to click that format button at least 3 different times. Will change topic title. Thanks guys!

Somehow things started working again. Not sure what was going on.  I swear I had to click that format button at least 3 different times. Will change topic title. Thanks guys!

You might want to upgrade to the latest version of unRAID.  Lots of things fixed since 5.0beta7.