[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 14/09/17 19:21, mr meowski wrote:
On 12/09/17 15:44, Julian Hall wrote:However, the suspect drive is detected and appears in Computer, but does not appear in Disks [I'm running Mint 18.3]. It refuses to mount with the error 'unable to read superblock'. dmseg | tail says '[13060.101764] EXT4-fs (dm-0): unable to read superblock'. Could / should I try to reformat the disk and put it back in the NAS or is it dead? If I should try to reformat it, how would I do that with a RAID 1 disk please?Fortunately that error message only tells you that the potential ext4 filesystem Mint has automatically detected on the RAID member disk is corrupted, rather than the disk has failed. Are there any other disk related errors in dmesg after plugging in and manipulating the disk (i.e., open it in gparted and poke around)? Your Synology NAS will have it's own native interface (presumably) for adding a disk to an existing degraded array - you'll have to use that so don't worry about formatting the disk on Linux first. You might be interested in "benching" or stress-testing the disk first under Linux before you try putting it back in the NAS though? Especially if you have good reason to suspect it of being faulty. Cheers
Hi,Sorry for the delay in replying. I was able to look at the disk in Gparted, and the partitions were there, it just won't mount. The Synology has no facility to add a HDD manually, it just automatically detects disks which have no problems and offers them to add to an array. As this one has issues it won't see it. That being the case I decided to remove all the partitions in Linux and /then/ try it back in the NAS. To all intents and purposes it is now a flat HDD. The NAS still will not detect it.
Kind regards, Julian -- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq