October 12, 201015 yr 1. I removed Disk3 to use in a windows machine 4 weeks ago, I continued to read access on Disk3 on the tower but no writes were performed. 2. I removed the same 1TB drive from the windows machine and re-installed as disk3 again. 3. When I started unraid it immediately started checking parity which I cancelled. 4. As disk 3 was formatted as a windows disk I pressed the format button to install the new file system. 5. I then pressed start and left it overnight checking parity. 6. Disk 3 now has the green ball but shows as Unformatted. 7. Parity is valid. I do not know what to do next any help would be much appreciated, syslog is attached. Thanks. syslog.zip
October 12, 201015 yr 1. I removed Disk3 to use in a windows machine 4 weeks ago, I continued to read access on Disk3 on the tower but no writes were performed.You could have written to the "missing" drive. But that is not important now. 2. I removed the same 1TB drive from the windows machine and re-installed as disk3 again.It should have started the process of re-constructing disk3 from parity and the other disks. It would look very similar other than it would be disk3 that would be "red" until the re-construction was completed. 3. When I started unraid it immediately started checking parity which I cancelled.I think it was the re-construction you cancelled. 4. As disk 3 was formatted as a windows disk I pressed the format button to install the new file system.This was a mistake. It did not matter what the disk was formatted as, since it was going to be re-constructed. Since you canceled the re-construction the disk could not be mounted, therefore it showed as un-formatted. 5. I then pressed start and left it overnight checking parity. 6. Disk 3 now has the green ball but shows as Unformatted. 7. Parity is valid. I do not know what to do next any help would be much appreciated, syslog is attached. Thanks. I fear you may have formatted the copy of your data that was being "simulated" by parity in combination with the other data drives. In other words... pressing the button was a mistake. For the array to have given you that choice I would have thought you pressed the button labeled as "restore" to force a new disk configuration. That action effectively erased the ability to re-construct the missing drive with data, now when you re-construct the replacement drive it will be re-constructed as a freshly formatted drive. Looking at the syslog I see some clues it might not have worked as I am guessing. First, the flash drive seems to have some file-system corruption and was mounted as read-only to prevent more damage Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: File system has been set read-only Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) Oct 11 16:48:33 NAS kernel: FAT: Filesystem error (dev sda) Oct 11 16:48:33 NAS kernel: fat_get_cluster: invalid cluster chain (i_pos 2973327) As a result, when you then started the array it could not write the config/super.dat file on the flash drive. Oct 11 16:48:33 NAS kernel: md: recovery thread checking parity... Oct 11 16:48:33 NAS kernel: write_file: error 30 opening /boot/config/super.dat Oct 11 16:48:33 NAS kernel: md: could not write superblock from /boot/config/super.dat Oct 11 16:48:33 NAS kernel: md: using 1152k window, over a total of 976762552 blocks. As you indicated, it could not mount the drive formatted as an NTFS drive, so its attempt to mount it as disk3 failed. Oct 11 16:48:33 NAS kernel: REISERFS (device md3): using ordered data mode Oct 11 16:48:33 NAS emhttp: _shcmd: shcmd (10): exit status: 32 Oct 11 16:48:33 NAS emhttp: disk3 mount error: 32 Oct 11 16:48:33 NAS emhttp: shcmd (11): rmdir /mnt/disk3 Then I see you canceling the re-construction that had started. Unnfortunately, the flash drive was un-writable, so the super.dat file could not be updated. Oct 11 17:01:43 NAS kernel: mdcmd (20): nocheck Oct 11 17:01:43 NAS kernel: md: md_do_sync: got signal, exit... Oct 11 17:01:43 NAS kernel: write_file: error 30 opening /boot/config/super.dat Oct 11 17:01:43 NAS kernel: md: could not write superblock from /boot/config/super.dat The process to re-construct drive 3 was not completed. Oct 11 17:01:43 NAS kernel: md: recovery thread sync completion status: -4 You pressed the format button. Oct 11 17:01:52 NAS emhttp: shcmd (58): mkreiserfs -q /dev/md3 >/dev/null 2>&1 But apparently, both reads and writes to the disk3 device failed AND its expected size changed? Oct 11 17:01:52 NAS kernel: attempt to access beyond end of device Oct 11 17:01:52 NAS kernel: sdb1: rw=0, want=1953524992, limit=1953520002 Oct 11 17:01:52 NAS kernel: md: disk3 read error Oct 11 17:01:52 NAS kernel: handle_stripe read error: 1953524984/3, count: 1 Oct 11 17:01:52 NAS kernel: attempt to access beyond end of device Oct 11 17:01:52 NAS kernel: sdb1: rw=1, want=1953524992, limit=1953520002 Oct 11 17:01:52 NAS kernel: md: disk3 write error Oct 11 17:01:52 NAS kernel: handle_stripe write error: 1953524984/3, count: 1 Oct 11 17:01:52 NAS kernel: md: recovery thread woken up ... Oct 11 17:01:52 NAS kernel: write_file: error 30 opening /boot/config/super.dat Oct 11 17:01:52 NAS kernel: md: could not write superblock from /boot/config/super.dat Oct 11 17:01:52 NAS kernel: md: recovery thread has nothing to resync Oct 11 17:03:00 NAS emhttp: shcmd (59): mkdir /mnt/disk3 Then, it starts complaining about the disk size. Oct 11 17:40:00 NAS emhttp: _shcmd: shcmd (221): exit status: 32 Oct 11 17:40:00 NAS emhttp: disk3 mount error: 32 Oct 11 17:40:00 NAS emhttp: shcmd (222): rmdir /mnt/disk3 Oct 11 17:40:00 NAS kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Oct 11 17:40:00 NAS kernel: REISERFS warning (device md3): sh-462 check_advise_trans_params: bad transaction max size (3722033764). FSCK? Oct 11 17:40:00 NAS kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Oct 11 17:40:00 NAS kernel: REISERFS (device md1): checking transaction log (md1) Oct 11 17:40:00 NAS kernel: REISERFS warning (device md3): sh-2022 reiserfs_fill_super: unable to initialize journal space Oct 11 17:40:00 NAS kernel: REISERFS (device md2): checking transaction log (md2) Oct 11 17:40:00 NAS kernel: REISERFS (device md2): Using r5 hash to sort names Oct 11 17:40:00 NAS kernel: REISERFS (device md1): Using r5 hash to sort names Oct 11 17:40:01 NAS emhttp: shcmd (225): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Oct 11 17:40:01 NAS emhttp: shcmd (226): cp /etc/exports- /etc/exports Oct 11 17:40:01 NAS emhttp: shcmd (227): mkdir /mnt/user Oct 11 17:40:01 NAS emhttp: shcmd (228): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions Oct 11 17:40:02 NAS emhttp: get_config_idx: fopen /boot/config/shares/Negatives.cfg: No such file or directory - assigning defaults Oct 11 17:40:02 NAS emhttp: shcmd (229): killall -HUP smbd Oct 11 17:40:02 NAS emhttp: shcmd (230): /etc/rc.d/rc.nfsd restart | logger Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520008, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520016, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520024, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520032, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520040, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520048, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520056, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520064, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520072, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520080, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520088, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520096, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520104, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520112, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520120, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520128, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520136, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520144, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520152, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520160, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520168, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520176, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520184, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520192, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520200, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520208, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=0, want=1953520216, limit=1953520002 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Writes to it failed too. Oct 11 22:52:25 NAS kernel: md: disk3 read error Oct 11 22:52:25 NAS kernel: handle_stripe read error: 1953520368/3, count: 1 Oct 11 22:52:25 NAS kernel: attempt to access beyond end of device Oct 11 22:52:25 NAS kernel: sdb1: rw=1, want=1953520376, limit=1953520002 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520000/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520008/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520016/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520024/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520032/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520040/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520048/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520056/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520064/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520072/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520080/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error Oct 11 22:52:25 NAS kernel: handle_stripe write error: 1953520088/3, count: 1 Oct 11 22:52:25 NAS kernel: md: disk3 write error You have multiple problems. 1. The flash drive file-system is corrupted and needs repair. 2. Your hard disk size seems to have changed. (Was an HPA added by your windows machine? or by your current motherboard? Is either a Gigabyte brand motherboard?) 3. You re-formatted your "simulated" disk3. (basically, ending its ability to re-construct its old data onto a physical disk. Now it will re-construct a formatted disk) You might be able to recover some of the files of the newly "formatted" disk by leaving disk3 un-assigned and then performing the steps described here in the wiki for recovering files from a mistakenly formatted drive. http://lime-technology.com/wiki/index.php?title=FAQ#How_can_I_undelete_files_from_an_unRAID_disk.3F Before you do anything you need to move the flash drive to a window's PC and run scandisk/checkdisk on it to repair its file-system damage. Joe L.
Archived
This topic is now archived and is closed to further replies.