NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
partition
3 TopicsFile system broken after power cut down
Recently, there were electrical works in my building and appartment that caused a power cut down. The beep of my UPS was probably to annoying for workers so they decided to unplug the NAS that was then running on the battery (facepalm). When power was restored, I plugged it back on my UPS, and press the start button. Then I received an email: New disk detected. [Disk 1] (Nas) A new disk was added to the ReadyNAS. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. Wow! No! It's not a new disk! Wait... And guess what? ... Power cut again, and unplugged from battery again. Since then, it won't start. So I extracted the disk, tried to clean, to put it back several times, then I decided to proceed to a check/repair/forensic journey... When I analyze the partition structure of the 2 TB disk, it seems to be partially broken. I use a Freecom Hard Drive Dock Duplicator to both connect the disk to USB to a working machine (and old 32-bits IBM X60) and duplicate the disk autonomously as is to be sure I have a backup if I did something wrong. What I want to achieve is either: fix the booting issue and make the NAS start as usual or retreive all the data from the disk and start a fresh install of the NAS, loosing all the configuration I did (scripts and crons and manually installed services and security tools etc.). When docked through USB, the device is mounted as /dev/sdb, /dev/sdb1, /dev/sdb2 and /dev/sdb3. Please note that I'm not familiar with RAID, filesystems, disk partitionning and data forensics. The following is all I have, without being sure of what it means. Please tell me if you see/understand something in this mess, and if I'm wrong. sudo mdadm -E /dev/sdb3 /dev/sdb3: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : 1858b355:7c24531e:2fddde7f:10cf1e0b Name : x60:99 (local to host x60) Creation Time : Sun Jan 1 19:35:50 2017 Raid Level : raid1 Raid Devices : 1 Avail Dev Size : 3897323368 (1858.39 GiB 1995.43 GB) Array Size : 1948661632 (1858.39 GiB 1995.43 GB) Used Dev Size : 3897323264 (1858.39 GiB 1995.43 GB) Data Offset : 262144 sectors Super Offset : 8 sectors Unused Space : before=262056 sectors, after=104 sectors State : active Device UUID : a8fe3d88:cb0c2668:fe0eac8d:b3b5d84c Internal Bitmap : 8 sectors from superblock Update Time : Sun Jan 1 19:35:50 2017 Bad Block Log : 512 entries available at offset 72 sectors Checksum : 2ebf2efb - correct Events : 0 Device Role : Active device 0 Array State : A ('A' == active, '.' == missing, 'R' == replacing) testdisk Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63 Partition Start End Size in sectors P Linux Raid 64 8386607 8386544 [E0469AA064B8:0] P Linux Raid 8388672 9437231 1048560 [E0469AA064B8:1] >P Linux Raid 9437248 3906760519 3897323272 [E0469AA064B8:2] Since then I did something wrong, before cloning the disk so the mistake is forever: tried testdisk partition discovery and write partition structure to disk Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63 Partition Start End Size in sectors P Linux Raid 64 8386607 8386544 [E0469AA064B8:0] P Linux Raid 8388672 9437231 1048560 [E0469AA064B8:1] >P Linux Raid 9437248 3906760519 3897323272 [x60:2] (How can I rename the third partition so it is back to original name?) Assembling the RAID partition sudo mdadm --assemble -v /dev/md99 /dev/sdb3 sudo mdadm --query --detail /dev/md99 /dev/md99: Version : 1.2 Creation Time : Sun Jan 1 19:35:50 2017 Raid Level : raid1 Array Size : 1948661632 (1858.39 GiB 1995.43 GB) Used Dev Size : 1948661632 (1858.39 GiB 1995.43 GB) Raid Devices : 1 Total Devices : 1 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Sun Jan 1 19:35:50 2017 State : clean Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : x60:99 (local to host x60) UUID : 1858b355:7c24531e:2fddde7f:10cf1e0b Events : 0 Number Major Minor RaidDevice State 0 8 19 0 active sync /dev/sdb3 sudo mount -t btrfs -o ro /dev/md99 /mnt/nashd/ mount: wrong fs type, bad option, bad superblock on /dev/md99, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. Any ideas? Thank you. Tim2KViews0likes8CommentsAdding a BackUPS Pro using serial COM port
Hi, I have just purchased a Startech ICUSB2321F which uses the FTDI FT232R chip with the intention of using it to connect an old APC BackUPS Pro with a serial port to a Netgear ReadyNAS Duo2 with a USB port. (The Netgear ReadyNAS Dashboard supports monitoring and display of UPS.) On connecting the UPS to the NAS via the Startech cable the NAS recognises the USB device, as shown by the following output of "lsusb": Bus 002 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC The NAS is running the Debian 6 Squeeze distribution with the following Linux version, as shown by the output of "uname -a" Linux lamanai 2.6.31.8.duov2 #1 Thu Apr 18 18:24:47 HKT 2013 armv5tel GNU/Linux I think I require a copy of ftdi_sio.ko and usbserial.ko drivers built for this version of Linux but have been unable to locate any on the internet. Note I have downloaded package linux-image-2.6.32-5-kirkwood_2.6.32-48squeeze6_armel.deb and extracted the files but when I do insmod using these I get the error: insmod: error inserting 'ftdi_sio.ko': -1 Invalid module format I do not think I can build the drivers from source on the NAS because it lacks a development environment and the repositories no longer appear to be available? If I try to do "apt-get install gcc" on my ReadyNAS I get errors of this form: Err http://ftp.us.debian.org/debian/ squeeze/main libc-bin armel 2.11.3-4 404 Not Found [IP: 128.30.2.26 80] And does this NAS have the space on its OS partition to store the necessary development tools and Linux kernal headers assuming they are available? (what is the name of the OS partition for a space query?) Any assistance or suggestions on these matters would be appreciated. PaulSolved2.4KViews0likes1CommentPlease Help: can't ssh, can't start services_case nos.: 25913382 / 25923232
My problems started this morning by getting this email message every 10 minutes: System volume root usage is 81 %. This condition should not occur in normal conditions. Please contact technical support. Looking into my system it looked like there was a lot of stuff in my /var directory, so I wanted to move that to a different partition. I did a little research and followed the instructions here to move my /var directory to /home/var: http://serverfault.com/questions/429937/how-to-move-var-to-another-existing-partition Basically, I did this: mkdir -p /home/var rsync -va /var /home/var mv /var /var.old mkdir -p /var mount -o bind /home/var /var added this line to /etc/fstab: /home/var /var none bind Then, could not access web admin page for readynas, something about the management service not running, so I hard rebooted. When it came back up it automatically went into setup wizard. I tried to ssh into my readynas but couldnt. I tried to turn on ssh service via the web admin page, but doesnt seem to let me turn on any services. No other services are working either (Plex, Subsonic). How can I fix this? My old var folder should still be there. I want to just change it back to the way it was, but since I cant ssh in I dont know how to do that. Please help. Jeff2.7KViews0likes7Comments