jsbarde

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

jsbarde's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Been with Unraid for 8 years. I came for the easy expandable arrays and stayed because of the great vm and docker support. Does everything I need and more.
  2. That appears to be exactly what it was. When you delete a docker "image" it does not clean up the appdata directory. Once I removed that and started over it worked great. Thanks for the help!
  3. What's weird is this is my first install, tho it's possible I had an old one at some point. (the docker was deleted but maybe it left stuff behind) I'll delete everything and start over and see what that does.
  4. I'm getting what appears to be to be some kind of mysql error on first install: Initiating database upgrade to version 1.30.4 from version 1.28.1 Upgrading database to version 1.30.4 Loading config from DB Saving config to DB Upgrading DB to 1.28.99 from 1.28.1 ERROR 1142 (42000) at line 393: CREATE command denied to user 'zmuser'@'localhost' for table 'Servers' Output: Column Id exists in States Column Id exists in States Column IsActive exists in States Column IsActive exists in States Command 'mysql -hlocalhost -uzmuser -p"zmpass" zm < /usr/share/zoneminder/db/zm_update-1.28.99.sql' exited with status: 1 Freshening configuration in database Loading config from DB Saving config to DB * Starting Apache httpd web server apache2 * Starting ZoneMinder: failure *** /etc/my_init.d/30_firstrun.sh failed with status 255 *** Killing all processes... I saw some posts on other forums about a bad upgrade script in the past...but that don't sound like the answer to me. Any ideas?
  5. Ok, so this is how we ended up. During the process at some point it appears I triggered a parity check, which I noticed later and canceled. Not sure if that helped or hurt. I then backed up everything I could get from the bad 2tb drive, it appears it was most of it. This took quite a while. I then shut down the server and put in the new precleared 3tb drive in place of the 2tb drive. Then I rebuilt the data from the 2tb drive with the parity. (this took quite a while too) I still had reiserfs errors so I did a check and then had to do a rebuild-tree. (that also took a decent amount of time) There are quite a few files in the lost+found folder but they all seem to work (at least from a fast check) and it appears that drive was rebuilt quite nicely too. Even after all my screw-ups unraid still did a nice job of protecting my data. Thanks to everyone for all there help and suggestions!
  6. I can stand to loose some data on this drive, just just movies and tv. So I don't have to get crazy on it. Let me make sure I understand the steps: 1. I stop the array and remove the 2tb drive that's having errors. 2. I restart the array and force the parity to update (how do I do that, is it just a regular parity check from the web interface?) 3. Once it's rebuilt I can add in my new 3tb drive and then copy the data (that I can get) from my bad 2tb drive. (I'm assuming this is from the command line, what's the best way to do that?) And then I should be good as new.
  7. haha yeah all my home stuff is homestar runner, and we still have a web server called trogdor at work
  8. I actually do have 1 drive that's having some issues. Part of what I was doing today was preclearing a 3tb red drive to replace a 2tb green drive that was having issues. The smart report for the failing drive is attached. Also to make matters worse I'm getting the following errors in the syslog /usr/bin/tail -f /var/log/syslog 2>&1 Nov 16 21:37:32 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 62985 does not match to the expected one 2 Nov 16 21:37:32 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 460718117. Fsck? Nov 16 21:37:32 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [444 446 0x0 SD] Nov 16 21:37:32 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 36020 does not match to the expected one 1 Nov 16 21:37:32 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 468160837. Fsck? Nov 16 21:37:32 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [352 356 0x0 SD] Nov 16 21:37:32 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 28913 does not match to the expected one 1 Nov 16 21:37:32 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 470811105. Fsck? Nov 16 21:37:32 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [347 350 0x0 SD] Nov 16 21:37:32 Homestar02 shfs/user: shfs_open: open: /mnt/disk1/Video/Television/Futurama/Season 3/Futurama S03E03 - -The Cryonic Woman.mkv (30) Read-only file system Nov 16 21:37:38 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 62985 does not match to the expected one 2 Nov 16 21:37:38 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 460718117. Fsck? Nov 16 21:37:38 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [444 447 0x0 SD] Nov 16 21:37:38 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 62985 does not match to the expected one 2 Nov 16 21:37:38 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 460718117. Fsck? Nov 16 21:37:38 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [444 446 0x0 SD] Nov 16 21:37:38 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 36020 does not match to the expected one 1 Nov 16 21:37:38 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 468160837. Fsck? Nov 16 21:37:38 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [352 356 0x0 SD] Nov 16 21:37:38 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 28913 does not match to the expected one 1 Nov 16 21:37:38 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 470811105. Fsck? Nov 16 21:37:38 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [347 350 0x0 SD] Nov 16 21:37:42 Homestar02 shfs/user: shfs_open: open: /mnt/disk1/Video/Television/Futurama/Season 3/Futurama S03E06 - -Bendless Love.mkv (30) Read-only file system Nov 16 21:37:46 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 62985 does not match to the expected one 2 Nov 16 21:37:46 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 460718117. Fsck? Nov 16 21:37:46 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [444 447 0x0 SD] Nov 16 21:37:46 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 62985 does not match to the expected one 2 Nov 16 21:37:46 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 460718117. Fsck? Nov 16 21:37:46 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [444 446 0x0 SD] Nov 16 21:37:46 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 36020 does not match to the expected one 1 Nov 16 21:37:46 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 468160837. Fsck? Nov 16 21:37:46 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [352 356 0x0 SD] Nov 16 21:37:46 Homestar02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 28913 does not match to the expected one 1 Nov 16 21:37:46 Homestar02 kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 470811105. Fsck? Nov 16 21:37:46 Homestar02 kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [347 350 0x0 SD] I'll hold off on doing anything until I hear back, I have a feeling I might be in trouble WD_2tb_green_sdm.txt
  9. So by accident (not paying attention when reading instructions) I ran mkfs.btrfs -f /dev/sdb1 on my parity drive. What do I need to do to undo this? I'm not a linux guy so I have no idea where to start, so far unraid doesn't seem to care but I suspect it's going to be a major issue soon.