No permission for my Drives, using Ubuntu 20.4

[Madlady 8]

When I go to add the folders to Emby Server, i get "The directory "/media/rootadmin/SATAHD-2000H-INT' could not be found.

We had a bad storm come through and knocked the power out and it crash. So finally got to the point where I could put ubuntu back on the server, with much help from reading and research. Now I finally found out where to add the server on the system. I am not at the point where I need to add the drives with the media on it, and emby server is not allowing me to add the folders.

I have read through this topic here and I see people solving there problems and thats great, but not really showing how and others I just dont understand. At this point I think I am going to mess up this system. I am an extreme NOOB, i watched my husband work on it and get it, but I never paid attention to it. He has passed away, been gone for 7months now,  and I am stuck and dont want to loose all his hard work. We have all our memories on the pc. So I can watch them and get them off onto something else more solid.

So here is what I have done.

All the drives are mounted, there are 8 of them.

I ran the command ls -l /media/rootadmin/SATAHD2000H-INT

The result are:

total 128
drwxrwxr-x  2 rootadmin rootadmin 90112 Jun 27 21:04 'All Completed Torrents'
drwxrwxrwx  5 root      root       4096 Jun  7  2021  Backups
drwxrwxr-x  8 rootadmin rootadmin  4096 Apr 29 12:39  CookBooks
drwx------  2 root      root      16384 Aug  9  2016  lost+found
drwxrwxr-- 42 rootadmin rootadmin  4096 Jun 28 13:11 'Movies - Live Action'
drwxr-xr-x 14 rootadmin rootadmin  4096 Sep 16  2022 'Music Audio'
drwxrwxrwx 11 root      root       4096 Oct 11  2023 'Videos - Tutorials'
drwxrwxrwx 18 root      root       4096 Jan 26  2024 'Videos - YouTube'

I then ran command:

setfacl -m user:emby:rxw /media/rootadmin/SATAHD-2000H-INT

I go back to Emby server and I still can not add the folders back.

Now my next step:

I took a look at fstab and now I am totally lost.

Im afraid at this point of loosing his machine.

Can someone please assist me?

 

Maddy..aka Madlady(gamertag)

Thanks in advance.

 

 

Edited October 17, 2024 by Madlady
Misspelled words

[guunter 49]

1 hour ago, Madlady said:

When I go to add the folders to Emby Server, i get "The directory "/media/rootadmin/SATAHD-2000H-INT' could not be found.

We had a bad storm come through and knocked the power out and it crash. So finally got to the point where I could put ubuntu back on the server, with much help from reading and research. Now I finally found out where to add the server on the system. I am not at the point where I need to add the drives with the media on it, and emby server is not allowing me to add the folders.

I have read through this topic here and I see people solving there problems and thats great, but not really showing how and others I just dont understand. At this point I think I am going to mess up this system. I am an extreme NOOB, i watched my husband work on it and get it, but I never paid attention to it. He has passed away, been gone for 7months now,  and I am stuck and dont want to loose all his hard work. We have all our memories on the pc. So I can watch them and get them off onto something else more solid.

So here is what I have done.

All the drives are mounted, there are 8 of them.

I ran the command ls -l /media/rootadmin/SATAHD2000H-INT

The result are:

total 128
drwxrwxr-x  2 rootadmin rootadmin 90112 Jun 27 21:04 'All Completed Torrents'
drwxrwxrwx  5 root      root       4096 Jun  7  2021  Backups
drwxrwxr-x  8 rootadmin rootadmin  4096 Apr 29 12:39  CookBooks
drwx------  2 root      root      16384 Aug  9  2016  lost+found
drwxrwxr-- 42 rootadmin rootadmin  4096 Jun 28 13:11 'Movies - Live Action'
drwxr-xr-x 14 rootadmin rootadmin  4096 Sep 16  2022 'Music Audio'
drwxrwxrwx 11 root      root       4096 Oct 11  2023 'Videos - Tutorials'
drwxrwxrwx 18 root      root       4096 Jan 26  2024 'Videos - YouTube'

I then ran command:

setfacl -m user:emby:rxw /media/rootadmin/SATAHD-2000H-INT

I go back to Emby server and I still can not add the folders back.

Now my next step:

I took a look at fstab and now I am totally lost.

Im afraid at this point of loosing his machine.

Can someone please assist me?

 

Maddy..aka Madlady(gamertag)

Thanks in advance.

 

 

So are the drives on a nas or directly on the machine running emby?

[Q-Droid 989]

You're on the right track looking at and doing some of the right things.

Post your fstab entries for the external drives.

Also run: namei -lv "/media/rootadmin/SATAHD2000H-INT/Movies - Live Action"

You can trim the list from the command above if it's too long. A sample should be enough.

Also run:  ps -eo ruser,rgroup,euser,egroup,f,comm | grep -i emby

 

[Madlady 8]

6 hours ago, guunter said:

So are the drives on a nas or directly on the machine running emby?

The drives are directly in the computer.

[Madlady 8]

3 hours ago, Q-Droid said:

You're on the right track looking at and doing some of the right things.

Post your fstab entries for the external drives.

Also run: namei -lv "/media/rootadmin/SATAHD2000H-INT/Movies - Live Action"

You can trim the list from the command above if it's too long. A sample should be enough.

Also run:  ps -eo ruser,rgroup,euser,egroup,f,comm | grep -i emby

 

Thank you, I usually am pretty up on things, just not this one, this time, lol. Thank you for the response. Please remember I am a beginner in understanding, although I am pc and programming advanced.

When you say post your fstab entries, I dont know how to do that, but will try it first. I'll do some research and then post what I find, hopefully its the right stuff. I will run, those commands to see what I get and post outcomes here as well. Thank you for the assistance, greatly.

[Madlady 8]

Here is my fstab entries.

(I ran sudo vi  /etc/fstab)

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda5 during installation
UUID=b7533eb9-cd48-4131-b144-600a257641ee /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda2 during installation
UUID=2261-6FCF  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
~             

I ran the next command and this is what I got also. (namei -lv "/media/rootadmin/SATAHD2000H-INT/Movies - Live Action")

rootadmin@DNS:~$ namei -lv "/media/rootadmin/SATAHD2000H-INT/Movies - Live Action"
f: /media/rootadmin/SATAHD2000H-INT/Movies - Live Action
drwxr-xr-x root root /
drwxr-xr-x root root media
drwxr-x--- root root rootadmin
                     SATAHD2000H-INT - No such file or directory

and the next command: (ps -eo ruser,rgroup,euser,egroup,f,comm | grep -i emby)

rootadmin@DNS:~$ ps -eo ruser,rgroup,euser,egroup,f,comm | grep -i emby
emby     emby     emby     emby     4 EmbyServer

Because I dont know what that will do, I will try and add the drive again, I also have seven more drives to go, if I can get this one, then I can duplicate what I just did, or is that necessary? Im finding this Ubuntu very interesting.

 

 

[guunter 49]

10 minutes ago, Madlady said:

Here is my fstab entries.

(I ran sudo vi  /etc/fstab)

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda5 during installation
UUID=b7533eb9-cd48-4131-b144-600a257641ee /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda2 during installation
UUID=2261-6FCF  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
~             

I ran the next command and this is what I got also. (namei -lv "/media/rootadmin/SATAHD2000H-INT/Movies - Live Action")

rootadmin@DNS:~$ namei -lv "/media/rootadmin/SATAHD2000H-INT/Movies - Live Action"
f: /media/rootadmin/SATAHD2000H-INT/Movies - Live Action
drwxr-xr-x root root /
drwxr-xr-x root root media
drwxr-x--- root root rootadmin
                     SATAHD2000H-INT - No such file or directory

and the next command: (ps -eo ruser,rgroup,euser,egroup,f,comm | grep -i emby)

rootadmin@DNS:~$ ps -eo ruser,rgroup,euser,egroup,f,comm | grep -i emby
emby     emby     emby     emby     4 EmbyServer

Because I dont know what that will do, I will try and add the drive again, I also have seven more drives to go, if I can get this one, then I can duplicate what I just did, or is that necessary? Im finding this Ubuntu very interesting.

 

 

So you can do another command to make emby the owner of the files and it should have permissions to see it that way. If you're adding new content to the server it makes it tricky without knowing how your other apps are setup but if you just want to watch the content now just run this command on the folders you want emby to have ownership of.

sudo chown -R emby /media/rootadmin/SATAHD2000H-INT/foldername

You can confirm the changes with

ls -l /media/rootadmin/SATAHD2000H-INT 

 

[Q-Droid 989]

There are many unknowns here and should be careful when making changes. If possible create a backup of the important stuff as soon as you can access it. 

With 8 drives it's important to figure out if they were individual, pooled, raid, etc. 

Figure out the filesystem. 

If you were able to mount one that's good but doesn't give us all of the answers. 

When you have more info then mount them properly from the fstab so the drives/volumes/filesystem are "permanent" and with the right access. 

Then you should be able to allow reliable access to Emby with the correct ownership and permissions. Might want to consider read only access to prevent accidental deletion until you have a handle on what to keep and what can be erased. 

Finally add the library paths to Emby for access to the media. 

[Madlady 8]

40 minutes ago, guunter said:

So you can do another command to make emby the owner of the files and it should have permissions to see it that way. If you're adding new content to the server it makes it tricky without knowing how your other apps are setup but if you just want to watch the content now just run this command on the folders you want emby to have ownership of.

sudo chown -R emby /media/rootadmin/SATAHD2000H-INT/foldername

You can confirm the changes with

ls -l /media/rootadmin/SATAHD2000H-INT 

 

I saw the first command last night, but not sure how it would work out, Imma give it a try and let you know the outcome.

rootadmin@DNS:~$ sudo chown -R emby /media/rootadmin/SATAHD2000H-INT/Movies - Live Action
[sudo] password for rootadmin:
chown: cannot access '/media/rootadmin/SATAHD2000H-INT/Movies': No such file or directory
chown: cannot access '-': No such file or directory
chown: cannot access 'Live': No such file or directory
chown: cannot access 'Action': No such file or directory

After running the second command to verify.

rootadmin@DNS:~$ ls -l /media/rootadmin/SATAHD2000H-INT
ls: cannot access '/media/rootadmin/SATAHD2000H-INT': No such file or directory

 

[Madlady 8]

3 minutes ago, Q-Droid said:

There are many unknowns here and should be careful when making changes. If possible create a backup of the important stuff as soon as you can access it. 

With 8 drives it's important to figure out if they were individual, pooled, raid, etc. 

Figure out the filesystem. 

If you were able to mount one that's good but doesn't give us all of the answers. 

When you have more info then mount them properly from the fstab so the drives/volumes/filesystem are "permanent" and with the right access. 

Then you should be able to allow reliable access to Emby with the correct ownership and permissions. Might want to consider read only access to prevent accidental deletion until you have a handle on what to keep and what can be erased. 

Finally add the library paths to Emby for access to the media. 

So the drives are individual drives. So as the drives got full, he added more drives to the point the MB is maxed out. No raid, or pooled. I am able to mount all of them, when I went into the disks application, Each states that its mounted. Learning how to mount them from fstab is what I need to do. Mind you, he had it working, its when the storm came and I had install the OS. The version of Ubuntu is a clean install. I remember the user names and passwords that he used, so I kept that same set up. Just getting the right permissions to the drives so that emby can see them and use them. So 'fstab' is my new learning objective. In my research, ive found some videos on describing fstab but there is always something left out to me. I like to know the ins and outs, so that if this happens again, Im not spending hours of trying to do it again.

Thanks for the response, I am very familiar with adding the folders to show the content as well. Just not how the system works.

[Madlady 8]

12 minutes ago, Madlady said:

So the drives are individual drives. So as the drives got full, he added more drives to the point the MB is maxed out. No raid, or pooled. I am able to mount all of them, when I went into the disks application, Each states that its mounted. Learning how to mount them from fstab is what I need to do. Mind you, he had it working, its when the storm came and I had install the OS. The version of Ubuntu is a clean install. I remember the user names and passwords that he used, so I kept that same set up. Just getting the right permissions to the drives so that emby can see them and use them. So 'fstab' is my new learning objective. In my research, ive found some videos on describing fstab but there is always something left out to me. I like to know the ins and outs, so that if this happens again, Im not spending hours of trying to do it again.

Thanks for the response, I am very familiar with adding the folders to show the content as well. Just not how the system works.

[Madlady 8]

So I opened DISKS, the application in Ubuntu. And it shows all of the drives. Each drive with media on it has been mounted here is an image of the drive Im starting with. Im still not able to add the folders, I bet it is something simple or will be or seem simple after I finally get it. Smh.

 

 

Edited October 17, 2024 by Madlady
adding more content

[Q-Droid 989]

When you mount them from the GUI application (disks) it will likely do so as the user launching the app and restricts access to that user, preventing others. Which is why doing so from fstab is preferable. Can also mount from the command line as root to achieve the same. Pick the least important drive to try things then move to the ones with things you want to preserve. 

I'm not at my server at the moment so can't offer much detail for the commands. 

[guunter 49]

25 minutes ago, Madlady said:

So I opened DISKS, the application in Ubuntu. And it shows all of the drives. Each drive with media on it has been mounted here is an image of the drive Im starting with. Im still not able to add the folders, I bet it is something simple or will be or seem simple after I finally get it. Smh.

 

 

From that screenshot it looks like the media is mounted on /media/rootadmin/SATAHD2000H-INT8 . The info you posted in the top post you had /media/rootadmin/SATAHD2000H-INT.

Since it seems like you have a JBOD does each disk have a different mount point? If that is the case you should do mount points in /etc/fstab

So you'd first have to create the folders to point the mount to. So something like /mnt/media/drive1 and /mnt/media/drive2 etc...  You need to make a folder for each drive.

Grab the UUIDs from the disks like in your screenshot.

Then you need to edit your fstab.

sudo nano /etc/fstab

ex. Take note the ext4 part should be changed to what ever file system the drive is using. I just took that info from your screenshot.

UUIDNumber /mnt/media/drive1 ext4 deffaults 0 0

Then do a

sudo systemctl daemon-reload

sudo mount -a

 

Edited October 17, 2024 by guunter

[Madlady 8]

7 minutes ago, guunter said:

From that screenshot it looks like the media is mounted on /media/rootadmin/SATAHD2000H-INT8 . The info you posted in the top post you had /media/rootadmin/SATAHD2000H-INT.

Since it seems like you have a JBOD does each disk have a different mount point? If that is the case you should do mount points in /etc/fstab

So you'd first have to create the folders to point the mount to. So something like /mnt/media/drive1 and /mnt/media/drive2 etc...  You need to make a folder for each drive.

Grab the UUIDs from the disks like in your screenshot.

Then you need to edit your fstab.

sudo nano /etc/fstab

ex. Take note the ext4 part should be changed to what ever file system the drive is using. I just took that info from your screenshot.

UUIDNumber /mnt/media/drive1 ext4 deffaults 0 0

Then do a

sudo systemctl daemon-reload

sudo mount -a

 

The drive ending is INT8 is one of the drives that needs to be mounted, I just showed that one. But my computer I had to do restart, and it showed that only one drive was mounted. I will read over and watch a video and try and edit the fstab and get back to you on it.

 

[Madlady 8]

20 minutes ago, Q-Droid said:

When you mount them from the GUI application (disks) it will likely do so as the user launching the app and restricts access to that user, preventing others. Which is why doing so from fstab is preferable. Can also mount from the command line as root to achieve the same. Pick the least important drive to try things then move to the ones with things you want to preserve. 

I'm not at my server at the moment so can't offer much detail for the commands. 

Thank you I will try this and let you know how it turns out. I will still need to watch the fstab video. One thing I am nervous about is deleting the OS. I appreciate all the information that youre giving. I am trying to save our media files, years of media.

[Q-Droid 989]

The OS is the least valuable data on that box and the easiest to recreate or recover. The drives holding your media and memories are the ones to be cautious with. As I posted before take this in steps and don't move to the next step until you're good with the current one.

 

[Madlady 8]

I knew that it was going to take me a minute to understand what FSTAB is about. I was afraid of erasing his drives with all our media on it. That was my hesitation.

Both of you provided me with the necessary steps to take and they both worked.

I wanted to understand the hierarchy for the users and groups. I checked them both in terminal. getent passwd and getent groups.

I had to first create emby which i did already, then I created a group for emby to be in and gave it rw  permissions and all.

So I used the commands above to give ownership to the drives.

Then I looked at the directory structure, I went happy making directory's all over the place and they really were not needed, so I practiced with removing directories I created, that took a few minutes, because I did not add the sudo in front of remove directories. I got permission denied, figured that out then, I watch a 25 min video on fstab, for like 4 hours to truly understand what I was doing and where things were at, and what not to move, and found a lot of advice on make sure to read carefully what you are typing.

The i found out how to find the blkid's and got the uuid.

The added the one drive to the fstab table and now its mounted permanently.

Here is the proof of adding the uuid.

UUID=d3d58fa0-c57b-45c4-a163-a93b988b28f5 /media/driveA ext4 defaults 0 0

Now I have 7 drives left to go.

Thank you for your patience, Emby Server is very easy to understand for me, to add all the drives, media and music into the server and run on our smart tvs, with the emby app around the house.

I'm a some-what happy widow, thanks again. Our precious memories have been saved. Thanks to you both.

Q-Droid and Guunter

 

[Madlady 8]

What would cause a drive not to be found?

 

I was trying to add the drive to emby via the folders and got the error message

The directory '/media/driveG/TV - Finished Series' could not be found.

I have a total of 6 drives, I have added them all following the steps below. 4 of the drives are working, 2 drives Im having issues with.

This is what I have done.

I checked the DISKS application to make sure the drive was there.

 I have added the drive in the fstab table.

 UUID=94ebd06b-c3aa-4dab-b569-a78589412aa9 /media/driveG ext4 defaults 0 0

UUID=d55df485-6adf-44b8-9f79-8349bc6f48aa /media/driveZ ext4 defaults 0 0
 

I ensured the UUID was correct by examining it, on the blkid screen.

 /dev/sdi: LABEL="SATA2000S-INT2" UUID="94ebd06b-c3aa-4dab-b569-a78589412aa9" BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop11: TYPE="squashfs"

/dev/sde: LABEL="SATAHD2000W-INT6" UUID="d55df485-6adf-44b8-9f79-8349bc6f48aa" BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop9: TYPE="squashfs"
I gave the drive permission by doing the chown and chmod.

rootadmin@DNS:~$ sudo chown emby:admins /media/driveG
rootadmin@DNS:~$ sudo chmod +rw /media/driveG

rootadmin@DNS:~$ sudo chown emby:admins /media/driveZ
rootadmin@DNS:~$ sudo chmod +rw /media/driveZ

I ran fsck on the drive 

rootadmin@DNS:~$ sudo fsck -n /dev/sdi
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
SATA2000S-INT2: clean, 4344/88727552 files, 342783925/354892056 blocks

rootadmin@DNS:~$ sudo umount /dev/sde
umount: /media/driveZ: target is busy.
rootadmin@DNS:~$ sudo fsck -y /dev/sde
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/sde is mounted.
e2fsck: Cannot continue, aborting.
 

I used smartctl on the drive to make sure it was operating well.

Overall Assessment - DISK is OK - SDI

Overall Assessment - Disk is OK, one attribute failed in the past - SDE

Ran the mount command to see what was mounted.

The Drive /dev/sdi is mounted.

The Drive /dev/sde is mounted. The Drive will not umont. See where I rand fsck on sde.

I am stumped.

Also when I go to add the Movies folder to emby, in the movies folder there are over 300 movies in the folder, but when I run the emby app, it does not show the movies, I've added them correctly.

/media/driveC/Movies - Live Action to the Movies Folder created in emby. 

 

Can someone help me again? Please

Edited October 23, 2024 by Madlady
needed to clarify more

[Q-Droid 989]

Can you attach an emby server log?

Now that you have the drives mounted we can go back to earlier posts in this thread.

You need to make sure the emby runtime user has access to the path. Meaning able to access each directory along the path to the final destination. Not necessarily w(rite) access, r(ead) is enough, but with directories x(ecute) is also needed to access/enter.

Run: namei -lv "/media/driveC/Movies - Live Action"

You can trim the list from the command above if it's too long. A sample should be enough. Do the same for the other drives and directories you want Emby to use.

The chown and chmod commands you've been running only affect the file or directory given in the path. They're not global or recursive unless you specify that option. This is the part where people go crazy and recursively give all privs or sweep ownership for more than they should.

My recommendation:
- Pick the directories or base path you want Emby to not only access but also be able to modify.
- Change permissions for the directories leading up the base directory.
- Change ownership recursively starting from the base directory.

Example, for "/media/driveC/Movies - Live Action"
- chmod o+rx /media /media/driveC
- chown -R emby:admins "/media/driveC/Movies - Live Action"

Again, start with a less important drive or media collection and scan the library after you make the changes.

 

[Madlady 8]

1 hour ago, Q-Droid said:

Can you attach an emby server log?

Now that you have the drives mounted we can go back to earlier posts in this thread.

You need to make sure the emby runtime user has access to the path. Meaning able to access each directory along the path to the final destination. Not necessarily w(rite) access, r(ead) is enough, but with directories x(ecute) is also needed to access/enter.

Run: namei -lv "/media/driveC/Movies - Live Action"

You can trim the list from the command above if it's too long. A sample should be enough. Do the same for the other drives and directories you want Emby to use.

The chown and chmod commands you've been running only affect the file or directory given in the path. They're not global or recursive unless you specify that option. This is the part where people go crazy and recursively give all privs or sweep ownership for more than they should.

My recommendation:
- Pick the directories or base path you want Emby to not only access but also be able to modify.
- Change permissions for the directories leading up the base directory.
- Change ownership recursively starting from the base directory.

Example, for "/media/driveC/Movies - Live Action"
- chmod o+rx /media /media/driveC
- chown -R emby:admins "/media/driveC/Movies - Live Action"

Again, start with a less important drive or media collection and scan the library after you make the changes.

 

Ok will start with that and try and get you my emby server logs as well.

Thank you.

[Q-Droid 989]

Regarding the drives with fsck/umount problems it's most likely because an active process or user is accessing that drive. If you can't find it then you might have to reboot and if you've added the paths to Emby then shut it down as well to see if that clears the problem and lets you unmount and fsck.

 

[Luke 42077]

@Madladyhas this helped?

[Madlady 8]

 

• Yes, these have helped greatly. I have to redo this all over again because my Ubuntu updated to the latest version, In windows I know how to turn off updates, In Ubuntu, I'm still searching. But will find it. I am currently reading over what was placed here to duplicate it in the newest update from Ubuntu, which wiped everything out. I still have my drive, which is all that matters. But this was very helpful and I can keep our memories and movies. It's such a great community.

 

 

Thank you all,

Maddy

[Madlady 8]

So one thing I'm grateful for among many is that I was not sure how installing emby on the upgraded Ubuntu worked, so I opened a terminal and started the update|upgrade and then went to do an install of emby server. The terminal stated it was already installed. So I was like hmm...let me check the status of the emby server by typing sudo systemctl status my-server. I came back...nothing found, error. So my next guess was to check and see if it was started, because when I went to the browser, I pressed my premade EMBY button, and it took me to create a new account. I was like OMG, I have to do all that work again. So quickly a thought came to me, and it was check to see if it is started, I ran the command sudo systemctl  start emby-server. I went to the browser did a refresh and all the work that I did from Ubuntu 20.4.5, showed up, I am now going to check my fstab to see if that carried over and I wont have to do that again either. I am grateful. Ive learn a lot, I feel like an expert. I could not have done this without the help of this community...I was tripping really hard thinking I was going to loose all of his hard work. I think he would be proud of me.

 

Thanks again everyone!

You all rock!

Maddy