Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

NSS4000 Volumes not showing up after powerfailure

Hello,

A little background info.... my NSS4000 had the internal firmware damaged with a reboot/powerloss within a few months of receiving the machine back in 2007... so I do use the external USB Boot loader to start the box; and it has been working great since.

   My reliable IT staff moved my UPS and my NSS4000 went through a few unexecpected power cycles in the freak snow storm last week in Connecticut.    When power was stable, I noticed my shares were no longer accessible.   Logging in to the device I see the following on Storage/Status page:

nss4000-volumes.JPG

I was able to save the configs to a USB drive and it shows my missing volumes in fstab (maybe there is more to it when mounting volumes from a raid device):

/dev/RAIDA/privatevol               /mnt/RAIDA/privatevol          xfs          defaults,usrquota,grpquota          0 0

/mnt/RAIDA/privatevol/d               /mnt/ftp_dir/d          none          rw,bind          0 0

/dev/RAIDA/scratchvol               /mnt/RAIDA/scratchvol          xfs          defaults,usrquota,grpquota          0 0

/dev/RAIDA/internalvol               /mnt/RAIDA/internalvol          xfs          defaults,usrquota,grpquota          0 0

/mnt/RAIDA/homevol/homes               /mnt/ftp_dir/home1          none          rw,bind          0 0

/mnt/RAIDA/internalvol/internal               /mnt/ftp_dir/internal          none          rw,bind          0 0

/mnt/RAIDA/scratchvol/public               /mnt/ftp_dir/public          none          rw,bind          0 0

/dev/RAIDA/homevol               /mnt/RAIDA/homevol          xfs          defaults,usrquota,grpquota          0 0

/mnt/RAIDA/homevol/.autohome/               /mnt/ftp_dir/homes          none          rw,bind          0 0

I am not sure what to look for in the log files... but I do see messages that seem like there may be other problems... in dmesg and messages I see the following type of errors:

Nov  9 17:49:30 nas kernel: Data CRC 558256a4 != calculated CRC 32fcada3 for node at 00370f74

Nov  9 17:49:30 nas kernel: Data CRC 558256a4 != calculated CRC 32fcada3 for node at 00370f74

Also in messages I see:

Nov  9 21:16:49 nas kernel: VFS: Mounted root (squashfs filesystem) readonly.

Nov  9 21:16:49 nas kernel: Freeing unused kernel memory: 160k freed

Nov  9 21:16:49 nas kernel: block2mtd: version $Revision: 1.1.1.3 $

Nov  9 21:16:49 nas kernel: block2mtd: default erase size is [4096]

Nov  9 21:16:49 nas kernel: block2mtd: mtd0: [d: /dev/scsibd1] erase_size = 128KiB [131072]

Nov  9 21:16:49 nas kernel: Empty flash at 0x011aaf1c ends at 0x011ab000

Nov  9 21:16:49 nas kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x011ab000: 0xb96a instead

Nov  9 21:16:49 nas kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x011ab004: 0x74d0 instead

Nov  9 21:16:49 nas kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x011ab008: 0x0802 instead

Nov  9 21:16:49 nas kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x011ab00c: 0xe250 instead

Nov  9 21:16:49 nas kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x011ab010: 0xaae5 instead

Nov  9 21:16:49 nas kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x011ab014: 0x3008 instead

Nov  9 21:16:49 nas kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x011ab018: 0x28f3 instead

Nov  9 21:16:49 nas kernel: Data CRC 558256a4 != calculated CRC 32fcada3 for node at 00370f74

Nov  9 21:16:49 nas last message repeated 8 times

I don't know if these type of messages existed before my problem... they certainly don't look good to me.      My thoughts were to try booting up with a drive missing (but which one should I take out)... or looking for another NSS4000 on ebay and putting the drives in it.

Any ideas?

Thanks

Mike

2 REPLIES
New Member

Re: NSS4000 Volumes not showing up after powerfailure

To anyone that may find themselves in the same situation...

I think it is back up and running.  I wasn't sure if the NSS4000 was dead... so I did the following:

1. made one "Save of the current configuration"

2. powered off

3. popped out the drives (labeling the position of course)

4. powered up with a new drive to test creating a new jbod array and volume (which failed with the same type of errors in my original post.)

5. Restored All Settings to Factory Defaults

6. Rebooted

7. Was able to create new JBOD Array on single drive with volumes (tested CIF and FTP.. worked this time)

8. Restored the configuration that I saved on Step 1

9. I let it fully reboot... and powered it off (still had wrong drive in)

10. Put original drives back in

11. Back in Business!!!!

I'm not sure why restoring factory defaults cleared out the problem... but I am glad I didn't lose my files.

Mike

PS... how do I mark this conversation as Answered and no longer a question?

Silver

Re: NSS4000 Volumes not showing up after powerfailure

Mike,

Thanks for the repost with answer definitely should help others in the future.

Thanks,
jasbryan

1202
Views
0
Helpful
2
Replies
CreatePlease to create content