NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New HDDs failing in Pro 2
Hello, I've been running a ReadyNAS Pro 2 with two 2TB WD red drives. I primarily use it as a backup and media server. I recently bought two 3TB drives (also red) to expand. Along the way I did somet...
bgg1 wrote:
With one old drive in, everything else (except for the few corrupted folders) seems to be working well - I can access all other files (at least the ones I tried), and can stream movies on Plex to my phone from both the drive and from an attached USB drive.
I'm not sure what the underlying issue is.
Options I see are
(a) try again on the new hard drive install/expansion. That might work, but some file corruption likely remains.
(b) format one of the 3 TB drives in a PC, and copy the data off the NAS to it. Then remove both 2 TB drives, and do a factory install with the remaining 3 TB drive. Reconfigure the NAS, install your apps, and restore the data from the copy. Then move the 3 TB drive from the PC to the NAS. This will take longer, but will ensure that everything is clean when you are done. You'd also preserve both of the 2 TB drives.
I shut down and tried booting up with the 2nd of the original drives now in slot 1. Booted fine, and i can access the data, but frontview gives me the error message: Volume scan failed to run properly. I tried rebooting with volume scan set to run on reboot with same results.
UPDATE: One thing I just noticed on this second drive is that one of the folders in my media share is listed as NAME_data instead of just NAME, and in that folder is another folder e00, and in there are folders d00 through d03, each one with many approx 1MB .au files. I found one other folder that was renamed to X_dsta with empty folders e00>d00 insid, and one additional X_data folder found. My assumption is that these are folders that got corrupted somehow. I will check the 1st drive again to see if thhey are there too.
2nd UPDATE: I rebooted with the first drive again. Same three folders are corrupt. Now i have the volume scan error on this disk as well. But other than said three folders, everthing else seems to be there.
For what it's worth, I just looked at my e-mail and saw the following from today. These are from after inserting and scanning the old disks. (multiple e-mails)
***** File system check performed at Wed Jan 4 09:56:05 EST 2017 *****
fsck 1.42.12 (29-Aug-2014)
/dev/c/c: recovering journal
/dev/c/c: clean, 113518/30121984 files, 310788421/481951744 blocks
fsck.ext4: Bad magic number in super-block while trying to open /dev/c/c_2015_03_03_00_00
/dev/c/c_2015_03_03_00_00:
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
***** File system check forced at Wed Jan 4 10:04:39 EST 2017 *****
fsck 1.42.12 (29-Aug-2014)
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/c/c: 113516/30121984 files (20.0% non-contiguous), 310786824/481951744 blocks
e2fsck 1.42.12 (29-Aug-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/c/c_2015_03_03_00_00
fsck 1.42.12 (29-Aug-2014)
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/c/c: 113516/30121984 files (20.0% non-contiguous), 310786824/481951744 blocks
e2fsck 1.42.12 (29-Aug-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
***** File system check performed at Wed Jan 4 10:26:35 EST 2017 *****
fsck 1.42.12 (29-Aug-2014)
/dev/c/c: clean, 113239/30121984 files, 310803974/481951744 blocks
fsck 1.42.12 (29-Aug-2014)
/dev/c/c: clean, 113239/30121984 files, 310803974/481951744 blocks
fsck.ext4: Bad magic number in super-block while trying to open /dev/c/c_2015_03_03_00_00
/dev/c/c_2015_03_03_00_00:
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
/dev/c/c_2015_03_03_00_00:
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
***** File system check forced at Wed Jan 4 10:32:47 EST 2017 *****
fsck 1.42.12 (29-Aug-2014)
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/c/c: 113237/30121984 files (19.9% non-contiguous), 310802803/481951744 blocks e2fsck 1.42.12 (29-Aug-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/c/c_2015_03_03_00_00
fsck 1.42.12 (29-Aug-2014)
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/c/c: 113237/30121984 files (19.9% non-contiguous), 310802803/481951744 blocks
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/c/c_2015_03_03_00_00
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
