Expanding RAID volume on NAS326 is not working

Options
13»

Comments

  • Night Hawk
    Night Hawk Posts: 2  Freshman Member
    edited August 2020
    Options
    I'm trying to follow the steps outlined by Joonas but I'm running into a problem when I try to check the file system on my disk before resizing the partition. I'm getting an error message saying /dev/md2 is in use. Is there any way to tell what process(es) are using it? 

    Edit: I did some more investigation. I haven't used LINUX before but when I did "mount | grep /dev/sd" I saw my device was sdc2. I tried "e2fsck -f /dev/sdc2" and got an error message saying the volume was mounted and I ran would severely damage the disk if I proceeded. The drive isn't in use other than what I'm doing to it currently so is this a boilerplate error or am I risking damaging the file system by doing the check?

  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    Joonas list has one fatal flaw. After point 11 'enter :wq' you should run 'poweroff' to initiate the shutdown.
  • Night Hawk
    Night Hawk Posts: 2  Freshman Member
    Options
    I am doing "poweroff" after exiting vi. Are there any other processes that might be keeping the drive open?
  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    lsof | grep /dev/md2

    might tell. I'm not sure if lsof is available.

    What does 'ps' say?
  • Bliko01
    Bliko01 Posts: 6  Freshman Member
    Options
    Hello, I did the procedure
    # umount /i-data/14fa6d39 
    # e2fsck -f /dev/md2
    e2fsck 1.42.12 (29-Aug-2014)
    /dev/md2 is in use.
    e2fsck: Cannot continue, aborting.
     # resize2fs /dev/md2
    resize2fs 1.42.12 (29-Aug-2014)
    resize2fs: Device or resource busy while trying to open /dev/md2
    Couldn't find valid filesystem superblock.
  • Bliko01
    Bliko01 Posts: 6  Freshman Member
    Options
    used  e2fsck -f  and resize2fs command on /dev/vg_5809fa3c/lv_94593ae instead of md2.
    It finally worked fine. Thanks a lot Mijzelf for your explanations
  • Jerry
    Jerry Posts: 3
    First Anniversary
    Options
    trying to edit /etc/init.d/rc.shutdown, permission denied. Any comments
  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    You need to become 'root' first, by executing 'su'.
  • Jerry
    Jerry Posts: 3
    First Anniversary
    Options
    Thank you Mijzelf, it worked out.

Consumer Product Help Center