My NAS (Seagate Blackarmor) is refusing to connect to the network after a fsck. I assume the root filesystem (stored on flash) might have been corrupted somehow after running fsck. The setup was a Raid 0 array with 2x2TB drives.
Edit: it might have actually been mdadm with linear span.
I have a USB<->SATA/IDE dock for accessing the disk drives on my laptop, but no way of connecting two drives at the same time.
The data stored on it is not critical but it reaches ~3TB and would like to still have it or at least compare it against another backup. I can also try soldering a TTL-UART converter on the board and work from there. NAS is based on Debian Lenny, I think.
Is there any way to check the integrity on each drive or remove the fsck flag without the other drive?
Are there any other ways to do this? Like image each one drive and use LVM on another system. Don't have enough space for this though. Or maybe buy another SATA-USB adapter.
This is how I did it, just one of the possibilities
The two 3.5" SATA drives were installed in a Win7 desktop machine and booted up an Ubuntu virtual machine inside Oracle VBox. The (raw) drives needed to be set up prior to starting the VM:
VBoxManage internalcommands createrawvmdk -filename "FILENAME" -rawdisk "\.\PhysicalDrive#"
Linux recognized the RAID and LVM setup right away ('Disks' utility) and offered to mount them. The system partition had 1GB and the entire /etc folder was missing plus other several files from /bin and /sbin. After a chkdsk some files were recovered in lost+found.
In the mean time all the files on the NAS drives were synchronized with my other backup.
I then searched for a raw image of the machine (Seagate Blackarmor) and extracted the missing files from the downloaded *.tar.gz archive. I haven't tested booting it yet but obviously some configuration will be missing: ip address, samba shares, mdadm.conf.