June 7, 201115 yr I recently upgraded from the free version to the plus version and added a 4th drive. (1 parity, 3 data). I am using version 4.7 I stopped the array, went to the Devices tab and added the new drive to the array. Then went back to the Main tab and the array status says Unformatted disk(s) present. I clicked the checkbox and clicked format. The screen says it's formatting, but if I refresh the screen or close the browser it just goes back to saying it's unformatted. It's a 500GB drive and I let it sit at the screen saying it's formatting overnight, but it's clearly not formatting the drive. I have tried several times, but it's just not formatting that drive. Any suggestions?
June 7, 201115 yr Hi, They can take a while to format if they haven't been pre_cleared first. Try using the pre_clear script to format the drive first. It will give you an update as it goes along. http://lime-technology.com/forum/index.php?topic=2817.0 Josh
June 7, 201115 yr Hi, They can take a while to format if they haven't been pre_cleared first. Try using the pre_clear script to format the drive first. It will give you an update as it goes along. http://lime-technology.com/forum/index.php?topic=2817.0 Josh Pre-clearing has absolutely no effect on the time it takes to format a drive. If you did not pre-clear a drive, then when you start an array after adding it, unRAID will clear it first and then format it. During its process of clearing the drive the array will be off-line. (That could take 4 or 5 hours or more for a large or slow drive) Once the drive is cleared it will show as "unformatted" If sounds as if the clearing had already occurred. Formatting should take only a few minutes. Post a syslog for analysis. It sounds as if the disk encountered errors. Joe L.
June 8, 201115 yr Attached is my syslog. Perhaps a bad drive? Your syslog contains: Jun 8 02:39:13 UNRAID emhttp: shcmd (34): mkreiserfs -q /dev/md3 2>&1 | logger Jun 8 02:39:13 UNRAID logger: mkreiserfs 3.6.21 (2009 www.namesys.com) Jun 8 02:39:13 UNRAID logger: Jun 8 02:39:13 UNRAID logger: Jun 8 02:39:13 UNRAID logger: The problem has occurred looks like a hardware problem. If you have Jun 8 02:39:13 UNRAID logger: bad blocks, we advise you to get a new hard drive, because once you Jun 8 02:39:13 UNRAID logger: get one bad block that the disk drive internals cannot hide from Jun 8 02:39:13 UNRAID logger: your sight,the chances of getting more are generally said to become Jun 8 02:39:13 UNRAID logger: much higher (precise statistics are unknown to us), and this disk Jun 8 02:39:13 UNRAID logger: drive is probably not expensive enough for you to you to risk your Jun 8 02:39:13 UNRAID logger: time and data on it. If you don't want to follow that follow that Jun 8 02:39:13 UNRAID logger: advice then if you have just a few bad blocks, try writing to the Jun 8 02:39:13 UNRAID logger: bad blocks and see if the drive remaps the bad blocks (that means Jun 8 02:39:13 UNRAID logger: it takes a block it has in reserve and allocates it for use for Jun 8 02:39:13 UNRAID logger: of that block number). If it cannot remap the block, use badblock Jun 8 02:39:13 UNRAID logger: option (-B) with reiserfs utils to handle this block correctly. Jun 8 02:39:13 UNRAID logger: Jun 8 02:39:13 UNRAID logger: bread: Cannot read the block (0): (Input/output error). Jun 8 02:39:13 UNRAID logger: Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 0 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 1 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 2 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 3 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 4 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 5 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 6 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 7 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 8 Jun 8 02:39:13 UNRAID kernel: Buffer I/O error on device md3, logical block 9 Jun 8 02:39:13 UNRAID emhttp: shcmd (35): mkdir /mnt/disk3 Jun 8 02:39:13 UNRAID emhttp: shcmd (36): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger Jun 8 02:39:13 UNRAID logger: mount: wrong fs type, bad option, bad superblock on /dev/md3, Jun 8 02:39:13 UNRAID logger: missing codepage or helper program, or other error Jun 8 02:39:13 UNRAID logger: In some cases useful info is found in syslog - try Jun 8 02:39:13 UNRAID logger: dmesg | tail or so Jun 8 02:39:13 UNRAID logger: Jun 8 02:39:13 UNRAID emhttp: _shcmd: shcmd (36): exit status: 32 Jun 8 02:39:13 UNRAID emhttp: disk3 mount error: 32 Jun 8 02:39:13 UNRAID emhttp: shcmd (37): rmdir /mnt/disk3 Jun 8 02:39:13 UNRAID kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 2, size 4096) Jun 8 02:39:13 UNRAID kernel: REISERFS warning (device md3): sh-2006 read_super_block: bread failed (dev md3, block 16, size 4096) Jun 8 02:39:13 UNRAID kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3 It indicated the drive cannot be read, therefore, the format failed. It could be a defective drive, or it could be as simple as a defective/loose cable to the drive. Power down, re-seat/replace the cables (both power and data) and try once more. Joe L.
Archived
This topic is now archived and is closed to further replies.