ReadyNas 312 - External storage device is connected but the file system is not recognized

The drive is powered by an adapter brick. It is not bus powered.

Do you have any other suggestions?

Is there a way I can remove any memory of this disk from the NAS so that the NAS sees it as entirely new when I reconnect it?

---

mikebomb wrote:

Is there a way I can remove any memory of this disk from the NAS so that the NAS sees it as entirely new when I reconnect it?

---

Very formal answer is to request a LoV or SoV from the vendor for your disk system 8-). No, this isn't Netgear here.

At the end of the day, it's very likely just an industry storage block (HDD, SSD, ...). Not that this does make the data unusable, remove the portions of a disk are sufficient to re-use your own storage.

Wiping data off of an SSD is a little different than erasing data from a HDD thanks to the wear-leveling algorithms used to write data evenly to an SSD. To securely erase all the data on an SSD, you use a command—called ATA Secure Erase or NVMe Secure Erase, appropriately enough—that’s built into the firmware of modern SATA and NVMe SSDs and older PATA/IDE drives.

On Linux (or for the sake on any NAS), clear the first block (two 512-byte sectors for MBR and header, and 16KiB for partition entries):

dd if=/dev/zero of=/dev/sdwhatever bs=512 count=34

Watch your step if you don't know what you do.... 

---

schumaku wrote:

---

mikebomb wrote:

Is there a way I can remove any memory of this disk from the NAS so that the NAS sees it as entirely new when I reconnect it?

---

 

On Linux (or for the sake on any NAS), clear the first block (two 512-byte sectors for MBR and header, and 16KiB for partition entries):

 

---

schumaku - you might be misunderstanding the question.

I believe @mikebomb just wants to start over with the USB identifiers, as he is up to USB_HDD_11.

Not sure how to do that (fwiw, I don't use USB drives).

StephenB schumaku You are both misunderstanding the question.

When I first connected this drive, it was new to the NAS and the NAS mounted and put it in the partition table and did whatever else it does when a new drive is connected.

Now, when I connect this drive, the NAS says, "I know this drive. I'm going to look up where to mount it, what partitions it has, and how to handle it." Since something is wrong with that somewhere, every time I connect this drive now I get errors.

Is there any way to wipe the memory of this drive from the NAS so that if I connect it, the NAS treats it as a drive it has never before seen? Or do I just have to buy a different drive and either return this one or find some other use for it, because as it stands now, it CANNOT be used with the NAS?

---

mikebomb wrote:

 

Now, when I connect this drive, the NAS says, "I know this drive. I'm going to look up where to mount it, what partitions it has, and how to handle it." Since something is wrong with that somewhere, every time I connect this drive now I get errors.

 

---

If you have a spare internal disk, you can test that theory by 

• powering down gracefully, removing the hard drives (labeling by slot)
• power up with only the spare disk, and doing a factory default
• doing minimal setup via the web ui

Then connect the drive, and see if it mounts properly.

After testing, power down again, and restore the original hard drives to their original slots.

---

mikebomb wrote:

Now, when I connect this drive, the NAS says, "I know this drive. I'm going to look up where to mount it, what partitions it has, and how to handle it." Since something is wrong with that somewhere, every time I connect this drive now I get errors.

 

Is there any way to wipe the memory of this drive from the NAS so that if I connect it, the NAS treats it as a drive it has never before seen? Or do I just have to buy a different drive and either return this one or find some other use for it, because as it stands now, it CANNOT be used with the NAS?

---

When dumping all partition tables from the external USB device, the only information left is the serial number the external storage device which libusb is making use of for re-mounting it when I have this right. Another NAS vendor has implemented my proposal years ago to use the volume label instead of the serial number, allowing to have an identity, and offer an accordingly named shared folder.   As there is no other data, no partition, no file system, ... there is not much other usage of this device.

---

schumaku wrote:

---

---

When dumping all partition tables from the external USB device, the only information left is the serial number the external storage device

---

Yeah.  Not sure if libusb makes use of it directly, or if the readynas application is somehow involved.  

In mikebomb's case, the mount point is changing on every attempt (up to USB_HDD_11, or higher).  If his issue was linked to bad state tied to the serial number, then I'd think it wouldn't be creating those mount points.

Anyway, if it is bad state, then the experiment I outlined above would result in the drive mounting normally, 

---

StephenB wrote:

---

If you have a spare internal disk, you can test that theory by 

• powering down gracefully, removing the hard drives (labeling by slot)
• power up with only the spare disk, and doing a factory default
• doing minimal setup via the web ui

Then connect the drive, and see if it mounts properly.

I have spare disks, I think. I'll see if I can run that experiment this weekend.