May 29, 201610 yr so i upgraded to v6.1.9 from v5 disk2 has REISERFS error (device md2): vs-7000 i was searching the forum but didnt see that error thanks lee May 29 14:03:54 Tower rpc.mountd[3138]: Version 1.2.8 starting May 29 14:03:54 Tower emhttp: Starting Docker... May 29 14:03:54 Tower logger: /usr/bin/docker not enabled May 29 14:03:55 Tower avahi-daemon[2106]: Service "Tower" (/services/smb.service) successfully established. May 29 14:04:34 Tower shfs/user: shfs_readdir: fstatat: jcg-other-stuff (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk2/backup/old-vhs-movies-tapes/hi8-tapes (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: fstatat: jcg-other-stuff (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk2/backup/old-vhs-movies-tapes/hi8-tapes (13) Permission denied May 29 14:06:00 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/newperms /mnt/disk2 May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118104 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118109 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118110 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118108 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118105 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS (device md2): Remounting filesystem read-only May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0
May 29, 201610 yr Community Expert What did you search for, "vs-7000"? I got 4 results when I searched for that. See search tips in my sig. Also, as RobJ said in your other thread, check disk filesystems is what you need.
May 29, 201610 yr Author yeah looks like i goofed later after trying to research when searching i wasn't on the main page im doing the check disk filesystems like robj said i did so far reiserfsck --check /dev/md2 and the output told me to run reiserfsck --rebuild-tree /dev/md2 as of right now i am just waiting for it to complete before it started it said there would be a lost+and+found folder where is that located after this is done? big thank you to Robj and trurl
May 29, 201610 yr before it started it said there would be a lost+and+found folder where is that located after this is done? In the root folder of the drive
May 29, 201610 yr Author just a update looks like its done doing its thing and stable once again i didnt see any files in lost and found so i either lost a few or it was able to fix everything and i didnt lose anything thank you Robj and trurl Squid
Archived
This topic is now archived and is closed to further replies.