Root out of space

English Install/Boot/Login
1

I have 19.3 GB ext4 root partition with only 400 MB left, which is not enough to update packages anymore.

This laptop is about five years old and I never had this problem until upgrade to 13.1. I ran out of space immediately after upgrade, a few months ago, and cleaned up everything I could - old kernels, even some rarely used packages. That gave me some 2-3 GB of free space but now it’s full again. Is this usual?

I don’t see any big log files or anything, and this is the top of my du - ah | sort -nr list run on /usr , :

1020K    ./src/linux-3.11.10-25/arch/alpha/kernel
1020K    ./share/wallpapers/Fog_on_the_West_Lake/contents/images/3840x2400.jpg
1020K    ./share/texmf/fonts/afm/public/fonts-tlwg
1020K    ./share/texmf/doc/texlive/texlive-pl/texlive-pl.pdf
1020K    ./share/texmf/doc/context/third/context-notes-zh-cn
1020K    ./share/icons/gnome/scalable/status
1020K    ./share/fonts/uni/newunifont.pcf.gz
1020K    ./share/doc/packages/tracker/ChangeLog
1020K    ./lib64/libreoffice/share/gallery/symbols
1020K    ./lib64/firefox/browser/extensions/langpack-tr@firefox.mozilla.org/browser/chrome
1020K    ./lib64/firefox/browser/extensions/langpack-son@firefox.mozilla.org/browser/chrome
1020K    ./lib64/firefox/browser/extensions/langpack-sl@firefox.mozilla.org/browser/chrome/sl
1020K    ./lib64/firefox/browser/extensions/langpack-sk@firefox.mozilla.org/browser/chrome
...

I can change my disk partitioning and resize and move root, or I have unused space at the end of the disk, maybe it’s possible to move some folders there, like help or docs. Or is there something wrong with my system that makes root grow?

2

Could be many things. Do you use a large database like mysql (the data defaults to root)? What do you have installed? I only use about 8 gig but I don’t install a lot of extraneous stuff. Check /tmp and the log files.

A recent thread said that some multimedia data base was using up huge amounts of space in root.

You can add a partition and mount it to hold any large data user. But first you have to know what is eating the space.

3

Nope, I’m not using mysql here, logs directory is 500 MB, most of the space is taken by /usr and there’s nothing particularly big there, too. Perl’s CPAN takes more than I expected but messing with it is tricky, I need those modules working.

It takes a fair bit of time to calculate /usr size, I’ll post the results once it’s over. Should be about 15 GB in my estimate.

Edit, it’s actually 11.3 GB.

4

gogalthorp donned his tin foil hat and penned:

>
> Could be many things. Do you use a large database like mysql (the data
> defaults to root)? What do you have installed? I only use about 8 gig
> but I don’t install a lot of extraneous stuff. Check /tmp and the log
> files.
>
> A recent thread said that some multimedia data base was using up huge
> amounts of space in root.
>
> You can add a partition and mount it to hold any large data user. But
> first you have to know what is eating the space.
>
>

As gogalthorp says, if you can find which dir in / root is taking up the most
space and you have enough slack on the drive then you can just copy all
across then do a test mount to check all is well, a good test depending on
which dir you copy for instance say you have a lot in /usr ( see note at
bottom of post ) then make a partition in the spare space that is over that
amount in the file system of choice ( ext3, ext4 etc…) copy all of /usr
across and in the root of the new /usr create a file does not matter what the
contents are but name it something unique like new-usr-dir.txt

do not do anything else and if it was me I would then reboot ( that is my
OCD showing ) :slight_smile:

Now when the machine has rebooted fresh have a quick look in the existing
/user and make sure that file does not exist, if it does not then use the
mount command to mount the “New” /use whatever it is:

mount -t type device destination_dir

where -t would be the file-system as above ext3 or ext4 or whatever you
picked.

device is the partition on disc sda4 or sda5 whatever…

destination would be “/usr” ( without quotes )

if all goes well then have a look once again in /usr and if you can see the
unique file that you created there and every thing seems fine after a bit of
use then you can add that line into the /etc/fstab.

( actually I would not yet I would then do another reboot and make sure that
the system reverts back to the old /usr, OCD is a great time waster ) :slight_smile:

If everything is OK then I would add that line in the fstab.

Then reboot and have a look in /usr if your file is there then hey presto you
have safely made a new /usr, personally I would use the machine for a couple
of days just to make sure and when you are satisfied you can then go on the
next step of deleting the old /usr to free up the space.

But that comes in lesson 2 of “Making Space by a Waste of Space” £20 at a
book store near you now :slight_smile:

The easiest way is to use a live distro and just delete the contents of the
Old /usr, but do make sure that everything is working fine first, trust me I
have been there myself :slight_smile:

HTH

I think I have covered everything but if anyone can see errors in my
diatribe the please shout before Stan fuffs his machine.

Note: this will work for dir like /usr /opt /root best, /var can also be
moved using this method, I would leave /tmp for the moment as I think you
would not do the test mount part it might throw a wobbly ( technical term )
:slight_smile:

/proc is not worth it as that a pseudo dir that does not exist.

Sorry for such a long post but it is one of those things where it is easy to
do but takes a bit of juggling to get the right sequence and if it all goes
pear shaped it can be a pain to fix if you do not know how.

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

5

Baskitcaise donned his tin foil hat and penned:

> gogalthorp donned his tin foil hat and penned:
>
>>
>> Could be many things. Do you use a large database like mysql (the data
>> defaults to root)? What do you have installed? I only use about 8 gig
>> but I don’t install a lot of extraneous stuff. Check /tmp and the log
>> files.
>>
>> A recent thread said that some multimedia data base was using up huge
>> amounts of space in root.
>>
>> You can add a partition and mount it to hold any large data user. But
>> first you have to know what is eating the space.
>>
>>
>

<snip load of waffle by me>

Just seen you have 11Gigs in /usr, if your spare space is not big enough for
all that then you can do the same trick with individual dir under /usr just
make sure your fstab entry is at the bottom and the “destination” is
correct.

A good choice might be the /usr/share dir so it would probably look
something like:

/dev/sda5 /usr/share ext3 defaults 1 1

Adjust to fit where from to where.

Correction to my previous post***

I forgot to include the above example syntax of the fstab entry in there
SORRY… Knew it all went to well from here until I reread it after sending
DOH! my OCD let me down.

HTH

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

6

On 2015-05-30 15:26, Baskitcaise wrote:

> Note: this will work for dir like /usr /opt /root best, /var can also be
> moved using this method, I would leave /tmp for the moment as I think you
> would not do the test mount part it might throw a wobbly ( technical term )
> :slight_smile:

Warning: therre are certain directories that should be in the main
partition, can not be moved. “/root” is one such, because you need it on
emergency boots to be able to log in as root.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

7

On 2015-05-30 14:16, Stan Ice wrote:
>
> I have 19.3 GB ext4 root partition with only 400 MB left, which is not
> enough to update packages anymore.
>
> This laptop is about five years old and I never had this problem until
> upgrade to 13.1. I ran out of space immediately after upgrade, a few

Was that a real upgrade, or did you install fresh on the same partition?

Also: is “/” a btrfs partition?

> I can change my disk partitioning and resize and move root, or I have
> unused space at the end of the disk, maybe it’s possible to move some
> folders there, like help or docs. Or is there something wrong with my
> system that makes root grow?

Find out what are the big directories. That’s the first thing to do.

If you can add a new partition anywhere, you can move things there, like
/usr/share, or even /usr. If you can not create new partitions, then use
symlinks or bind mounts to move those directories to another partition
with free space.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

8

Carlos E. R. donned his tin foil hat and penned:

> On 2015-05-30 15:26, Baskitcaise wrote:
>
>> Note: this will work for dir like /usr /opt /root best, /var can also be
>> moved using this method, I would leave /tmp for the moment as I think you
>> would not do the test mount part it might throw a wobbly ( technical term
>> )
>> :slight_smile:
>
> Warning: therre are certain directories that should be in the main
> partition, can not be moved. “/root” is one such, because you need it on
> emergency boots to be able to log in as root.
>

Oops! Thanks Carlos,

I had to answer the bl**dy phone half way through my post and that is my
excuse :slight_smile:

I knew I must have got something wrong.

Cheers

Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

9

All the upgrades on this laptop were online, via zypper. There’s no btrfs, only ext4.

20 GB for root is legacy of the very first install five years ago, there was no space problem until upgrade to 13.1.

Before creating more space or moving /usr I want to be sure there’s no underlying problem somewhere else. It was only a few months ago when I freed up 2-3 GB and I haven’t installed anything of note since. Is this a normal rate of creep as packages and their dependencies slowly grow and take up more space?

For comparison, a couple of years ago I sandwiched Ubuntu in between original Windows and openSUSE, its root is 12 GB of which only 8 GB is used, and it has all my essential software in case openSUSE gets broken (it was in the days when I first tried messing with video drivers for dual card and bumblebee). It all works now and Ubuntu sits unused.

I can format that partition and mover /usr there but my /usr is already at 11 GB and will hardly fit in 12 GB space. The advantage is that it’s next to openSUSE on the disk.

I can move /usr at the end of the disk where there’s 50 GB of unused space, but will it make the system significantly slower as /usr will be on the other side of /home from root and swap?

I can delete Ubuntu partition and expand root there but it’s impossible on a live system, nor when running Windows, right? Plus, if moving root fails I can end up with a completely broken and unbootable linux.

I also suspect that my optical drive is busted, or maybe all my blank CDs are too old, either way I can’t burn and boot into something like GParted.

So, in case fixing root growing out of space is impossible, the solution I want to try is this:

  1. Create a new ext4 partition at the free end of the disk
  2. Copy Ubuntu root there and make sure it’s bootable and works in case openSUSE gets borked.
  3. While running this new Ubuntu, delete the original Ubuntu partition and move and resize openSUSE root using this reclaimed space.
  4. Boot back into openSUSE.

Step 2 would need rebuilding grub2 and possibly editing new Ubuntu’s fstab.
Step 3 would also require moving swap, I hope it’s possible to not mount/unmount it while either in openSUSE or in Ubuntu.

Sounds plausible?

10

My 13.1/KDE4 is on a 20GB partition, ext4, including /home 2GB, and 7GB /usr; excluding /boot; and with 6GB free space. From /var/log/zypp/history, it was upgraded from 12.2 > 12.3 > 13.1, and upgrades were online via zypper dup. It hasn’t run out of space or come close, but my data and /boot are on separate partitions.

My /usr is smaller than yours, above the default install I’ve added VirtualBox (vdi’s stored elsewhere), mostly additional multimedia apps, Jack sound server, Rosegarden, and various others - SeaMonkey, Thunderbird, etc. If you need anything else for comparison, just ask. :slight_smile:

11

Stan Ice donned his tin foil hat and penned:

>
> All the upgrades on this laptop were online, via zypper. There’s no
> btrfs, only ext4.
>
> 20 GB for root is legacy of the very first install five years ago, there
> was no space problem until upgrade to 13.1.
>
> Before creating more space or moving /usr I want to be sure there’s no
> underlying problem somewhere else. It was only a few months ago when I
> freed up 2-3 GB and I haven’t installed anything of note since. Is this
> a normal rate of creep as packages and their dependencies slowly grow
> and take up more space?

By moving /usr you will at least be able to check where this creep is coming
from without running out of space before you can.

>
> For comparison, a couple of years ago I sandwiched Ubuntu in between
> original Windows and openSUSE, its root is 12 GB of which only 8 GB is
> used, and it has all my essential software in case openSUSE gets broken
> (it was in the days when I first tried messing with video drivers for
> dual card and bumblebee). It all works now and Ubuntu sits unused.
>
> I can format that partition and mover /usr there but my /usr is already
> at 11 GB and will hardly fit in 12 GB space. The advantage is that it’s
> next to openSUSE on the disk.

I personally would not go down that route, if it is /usr that is growing
then you will have the same problem crop up pretty soon and have to start
messing about again.

>
> I can move /usr at the end of the disk where there’s 50 GB of unused
> space, but will it make the system significantly slower as /usr will be
> on the other side of /home from root and swap?

You will not notice the m/s longer it might take.

>
> I can delete Ubuntu partition and expand root there but it’s impossible
> on a live system, nor when running Windows, right? Plus, if moving root
> fails I can end up with a completely broken and unbootable linux.

No, I would not go down that route, if you make a mistake you can bork your
machine, at least with my solution once set up you use the machine for a
week or so before deleting the original /usr therefore if anything happens
all you do is comment out or remove the entry in fstab and voilà you are
back to where you are now as long as you do not change many programs in /usr
during the test phase.

>
> I also suspect that my optical drive is busted, or maybe all my blank
> CDs are too old, either way I can’t burn and boot into something like
> GParted.
>
>
> So, in case fixing root growing out of space is impossible, the solution
> I want to try is this:
>
>
>
> - Create a new ext4 partition at the free end of the disk
> - Copy Ubuntu root there and make sure it’s bootable and works in
> case openSUSE gets borked.
> - While running this new Ubuntu, delete the original Ubuntu partition
> and move and resize openSUSE root using this reclaimed space.
> - Boot back into openSUSE.
>
>
> Step 2 would need rebuilding grub2 and possibly editing new Ubuntu’s
> fstab.
> Step 3 would also require moving swap, I hope it’s possible to not
> mount/unmount it while either in openSUSE or in Ubuntu.
>
> Sounds plausible?
>
>

Weeeelllll… Yes but a lot of work for nothing, as I said above my solution
is totally reversible by editing just one file line in fstab and is less
fraught of dangers.

But YMMV

Cheers

Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

12

Another idea is to simple remove old programs you don’t use.20 Gig with ext4 should be plenty enough normal Desktop usage unless you do have some large data storage setup or have a tmp/cache/log problem. One of the reasons I always do a clean install is to clean out all the junk I installed but never use.

.

13

On 2015-05-31 12:26, Stan Ice wrote:

> Before creating more space or moving /usr I want to be sure there’s no
> underlying problem somewhere else. It was only a few months ago when I
> freed up 2-3 GB and I haven’t installed anything of note since. Is this
> a normal rate of creep as packages and their dependencies slowly grow
> and take up more space?

No, not typically.

Do you have the kernel sources installed? Do you build the kernel? They
are huge, and they grow with updates (more versions installed).

You have to find where space is gone.


du -hscx --exclude=/proc --exclude=/sys --exclude=/dev --exclude=/mnt
--exclude=/media --exclude=/run   /* 2>/dev/null

(one line)

> I can format that partition and mover /usr there but my /usr is already
> at 11 GB and will hardly fit in 12 GB space. The advantage is that it’s
> next to openSUSE on the disk.

Don’t.

You might perhaps move instead /usr/share, if it has a reasonable size.

> I can move /usr at the end of the disk where there’s 50 GB of unused
> space, but will it make the system significantly slower as /usr will be
> on the other side of /home from root and swap?

Not significantly, no.
I would use it, all of it, or part of it. Both methods have advantages
and disadvantages.

> I also suspect that my optical drive is busted, or maybe all my blank
> CDs are too old, either way I can’t burn and boot into something like
> GParted.

Before you go ahead, make sure you can boot some external rescue media.
My choice is the XFCE rescue image from openSUSE, on a USB stick.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

14

Somehow I mistakenly assumed I’m still on 13.1. No, I upgraded to 13.2 a few months ago and it was this upgrade that created a creep on this machine.

Another idea is to simple remove old programs you don’t use.

I’ve done that the first time I run out of space shortly after the upgrade.

Do you have the kernel sources installed? Do you build the kernel?

No, and I removed old kernels at that time, too.

Baskitcaise, your solution does make a lot of sense, it’s fairly easy to implement, it would be easier to isolate the source of the creep, and it’s easily reversible.

The problem I’ve just encountered, though, is that when I try to create a new partition on the unused space at the end of the disk I get this error:

There are already 4 primary partitions on this device. This is the maximum number its partition table type can handle. 
You cannot create, paste or restore a primary partition on it before you delete an existing one.

It’s from KDE partition manager rather than YAST module (where the option to add a new partition is not even shown).

Is it possible to copy /usr to /home and mount it from there? I have 47 GB free in home and I suppose I can resize and extend it to include unpartitioned space. I think 20GB should be enough for my current 11GB /usr for now.

15

Stan Ice donned his tin foil hat and penned:

>
> It’s from KDE partition manager rather than YAST module (where the
> option to add a new partition is not even shown).
>
> Is it possible to copy /usr to /home and mount it from there? I have 47
> GB free in home and I suppose I can resize and extend it to include
> unpartitioned space. I think 20GB should be enough for my current 11GB
> /usr for now.
>
>

HI Stan,

Have you got much data in your /home partition?

I am wondering if it would be possible to back your stuff up, nuke that
partition, repartition the slack as and extended drive then you can create
as many partitions in there as you want ( /usr and /home )?

As to your other question of having /usr on your /home partition…

Ummm… errr!!! I will have to look into that something tells me “no” I
don`t know why but maybe I am wrong it is a while since I have messed about
with partitioning systems, I have a feeling that depending on how/when the
system mounts the /home partition could cause probs if it calls something in
/usr before /home has been mounted then ???

Not sure maybe someone who is a bit more knowledgeable on the system load
sequence can help?

I have a set rule that I normally stick to that works for me because I know
what software I will be using and I have always done clean installs.

Can you post your fstab though just so I can get a clear view and then will
do some research and see what will be the best way forward?

Cheers

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

16

I’m afraid not.

/home and all my other Linux partitions, sda5 through to sda8, are on an extended drive already - sda3 in my table. Before that there’s windows, and at the end of the drive there’s what looks like one more windows recovery partition, sda4.

I could, theoretically, shrink that sda3 without nuking /home and create another extended partition between it and sda4 at the end but it doesn’t look like an option in partition manager, but maybe I’m missing something, I never understood how these primary, extended and logical partitions relate to each other exactly.

I suppose I could nuke sda4 and leave windows without recovery, but it’s the only working windows in the house and all iDevices depend on iTunes, can’t have anything bad happen to it. Windows came preinstalled and without a DVD so if it’s lost it’s lost. I burned Windows recovery disks once but I’m not sure if they are still in good condition, this plastic storage doesn’t last very long.

Can you post your fstab though just so I can get a clear view and then will
do some research and see what will be the best way forward?

I’ll get to that notebook in a few hours and post fstab then.

I remember I tried moving /usr to /home when I first encountered the creep and it sort of worked, but in the end I went with cleaning up installed programs instead.

17

Stan Ice donned his tin foil hat and penned:

> I remember I tried moving /usr to /home when I first encountered the
> creep and it sort of worked, but in the end I went with cleaning up
> installed programs instead.
>
>

I have a plan, a very cunning plan!

But I will wait till I see your fstab first :slight_smile:

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

18

On 2015-06-02 10:48, Baskitcaise wrote:

> As to your other question of having /usr on your /home partition…
>
> Ummm… errr!!! I will have to look into that something tells me “no” I
> don`t know why but maybe I am wrong it is a while since I have messed about
> with partitioning systems, I have a feeling that depending on how/when the
> system mounts the /home partition could cause probs if it calls something in
> /usr before /home has been mounted then ???
>
> Not sure maybe someone who is a bit more knowledgeable on the system load
> sequence can help?

I don’t see an issue, but… I’m not sure. I would do it with a bind
mount, not a symlink. The issue with /usr not on root is that the initrd
boot archive needs to have a copy of everything needed for booting and
starting, before /usr is mounted. This happens automatically, but I
don’t know what triggers it when you run “mkinitrd”. Maybe the existence
of /usr in fstab, but that’s just guessing in my part.

Of course, you can try: just copy the files to home, rename the old usr,
make te bind mount in fstab, and reboot… No, first boot a rescue,
chroot it all and mkinitrd. If it fails, revert the usr rename.

What is absolutely needed is having always a rescue system available,
and as I said, I prefer the rescue image from the opensuse download
site. Why? Because when the system doesn’t boot and goes to emergency
mode, it may not mount usr (or home/_usr), and as you only have the
insufficient tools in initrd, you are stuck.

I know because I have /usr on a different partition.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

19

On 2015-06-02 06:26, Stan Ice wrote:

> The problem I’ve just encountered, though, is that when I try to create
> a new partition on the unused space at the end of the disk I get this
> error:
>
>
> Code:
> --------------------
> There are already 4 primary partitions on this device. This is the maximum number its partition table type can handle.
> You cannot create, paste or restore a primary partition on it before you delete an existing one.
>
> --------------------

Well, that is so, there can only be four primaries. One of them can be an “extended” partition, which contains as many logical partitions as you wish.

That extra partition you want has to be inside the contiguous space defined for the extended partition.

Post here the output of:


su -
fdisk -l
lsblk --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT

so that we can advise better.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

20 
stan@linux-y70s:~> su -
Password: 
linux-y70s:~ # fdisk -l


Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xaae439ed


Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048   3074047   3072000   1.5G 12 Compaq diagnostics
/dev/sda2         3074048 453954337 450880290   215G  7 HPFS/NTFS/exFAT
/dev/sda3  *    453955582 833443607 379488026   181G  f W95 Ext'd (LBA)
/dev/sda4       951261184 976773119  25511936  12.2G 17 Hidden HPFS/NTFS
/dev/sda5       479961088 498513014  18551927   8.9G 82 Linux swap / Solaris
/dev/sda6       498513078 540474794  41961717    20G 83 Linux
/dev/sda7       540474858 833443607 292968750 139.7G 83 Linux
/dev/sda8       453955584 479961087  26005504  12.4G 83 Linux


Partition table entries are not in disk order.
linux-y70s:~ # lsblk --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
NAME   KNAME  RA RM RO   SIZE TYPE FSTYPE LABEL     PARTLABEL MOUNTPOINT UUID                                 PARTUUID                             WWN MODEL     ALIGNMENT
sda    sda   128  0  0 465.8G disk                                                                                                                     TOSHIBA M         0
├─sda1 sda1  128  0  0   1.5G part ntfs   System                         5CD87D9DD87D75DC                     aae439ed-01                                                0
├─sda2 sda2  128  0  0   215G part ntfs   S3A9103D001
                                                              /windows/C 9AB0A395B0A37683                     aae439ed-02                                                0
├─sda3 sda3  128  0  0     1K part                                                                            aae439ed-03                                                0
├─sda4 sda4  128  0  0  12.2G part ntfs   HDDRECOVERY
                                                              /windows/D F6B6E867B6E829B7                     aae439ed-04                                                0
├─sda5 sda5  128  0  0   8.9G part swap                       [SWAP]     46473ca8-52b1-479f-b4b4-acd309824f17 aae439ed-05                                                0
├─sda6 sda6  128  0  0    20G part ext4                       /          87bb2d2e-6ed9-43ab-ade8-24ec5892fa03 aae439ed-06                                                0
├─sda7 sda7  128  0  0 139.7G part ext4                       /home      94e4633d-539c-41df-8c9b-32a1c2bdbc47 aae439ed-07                                                0
└─sda8 sda8  128  0  0  12.4G part ext4                                  41d06bdc-08b1-4072-a0f8-5c7e2d271a85 aae439ed-08                                                0
sr0    sr0   128  1  0  1024M rom                                                                                                                      DVDRAM GA         0
linux-y70s:~ #

and fstab

/dev/disk/by-id/ata-TOSHIBA_MK5065GSX_30OES2JXS-part5 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-TOSHIBA_MK5065GSX_30OES2JXS-part6 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-TOSHIBA_MK5065GSX_30OES2JXS-part7 /home                ext4       defaults              1 2
/dev/disk/by-id/ata-TOSHIBA_MK5065GSX_30OES2JXS-part2 /windows/C           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
/dev/disk/by-id/ata-TOSHIBA_MK5065GSX_30OES2JXS-part4 /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0